A pumping station estimate can look complete while leaving the most awkward work between packages. The concrete is measured, the pumps have a quotation and the pipework has a rate. Then someone asks who has allowed for the connection to the live network.
That question is a useful place to start. Water projects are systems. An estimate needs to describe the assets, but it also needs to explain how they will be installed, connected and brought into service.
The example in our estimating spreadsheet is deliberately manageable: a pumping station upgrade and a 500 m rising main. It includes a wet well, reinforcement, formwork, trench excavation, PE pipework, valves, a pump set, controls and a commissioning allowance. The quantities and rates are fictional teaching inputs. They are not a tender, a design or a market benchmark.
- Wet well and civil works
- Pumps and mechanical installation
- Rising main and valves
- Power and controls
- Testing and handover
A simplified functional breakdown for our fictional spreadsheet project. It is not a construction sequence or standard classification.
Establish the boundary before choosing a code
Imagine walking the proposed route from the wet well to the discharge point. At each change of material, ownership or work method, ask what needs to happen. Who excavates? Who supports the trench? Who keeps the work dry? Where can spoil be stored? What happens at a road crossing?
Do not assume that a supplier’s description answers these questions. “Pump set supplied” may cover equipment only. “Pipework installed” might exclude excavation, testing or a specialist jointing crew. Keep the original quotation and make any additions visible.
The structure should follow that understanding. Work packages are useful when checking delivery responsibilities. A resource view helps examine labour, material and plant. A measurement classification supports the bill. These are different views of the same work, so changing the view should not change the total.
Measure quantities on a stated basis
The training example includes 500 m of rising main. That length does not tell us the trench volume on its own. Width, depth, local enlargements and the measurement convention all matter. Likewise, the amount excavated is not automatically the amount exported: some material may be retained and reused.
A practical quantity record keeps net work, procurement allowances and disposal quantities separate. Record the reason for any difference. If imported bedding displaces material that would otherwise be reused, follow the effect through the earthworks balance rather than adjusting the final disposal number by instinct.
The spreadsheet starts in a CESMM view because the example is civil engineering work. Its top-level groups are review aids. Some mechanical, electrical and commissioning items are deliberately left unclassified until the project’s measurement requirements are established. Choosing NRM2 changes the view; it does not turn a water project into a fully compliant building bill.
| Interface | What to establish | Where to record it |
|---|---|---|
| Pipework and civil works | Who prices bedding, backfill and reinstatement? | Measured item and scope note |
| Pump and electrical package | Who supplies cables, starters and controls? | Enquiry and quote comparison |
| New asset and live network | Who plans isolation, testing and connection? | Method, programme and estimate basis |
An interface can be missing even when both neighbouring packages have been priced.
Read the gaps as carefully as the prices
Dewatering, temporary works, utility diversions and live connections can matter more than a small change in the pipe supply rate. Their absence from a teaching model should prompt a scope question, not an assumption that they cost nothing.
Our example excludes land, design fees, preliminaries, overhead, profit, contingency and tax. It also excludes several project-dependent activities identified in the project-basis panel. A commercial estimate needs those decisions resolved and recorded. Add the required work as identifiable items with an owner and a price basis.
There is a similar distinction within commissioning. A single allowance makes a small example easier to use, but a real project may need separate provision for pressure testing, cleaning, process checks, electrical testing, telemetry integration, operator training and handover records. The applicable specification determines what is needed.
Review the system before reviewing the sum
A useful first review asks whether the priced scope can deliver an operational asset under the stated conditions. A second review tests quantities and resource assumptions. Only then does reconciling every row give you confidence that the total means what the team thinks it means.
Try changing the pipe length in the spreadsheet. The pipe supply and jointing cost will move, but excavation and reinstatement do not update automatically because they are separate measured items. A change in one quantity should trigger a review of related quantities, not an unexplained adjustment hidden in another cell.
The lesson is broader than water infrastructure. A cost structure can organise an estimate very well. It cannot decide the scope for you.