Utility takeoff guide

How to do sanitary and storm sewer depth-bracket takeoffs faster

Tracing pipe is the easy part. The slow part of a subdivision takeoff is splitting runs into depth bands, keeping the assumptions straight, and rolling it all into a bid summary you can still explain a month later. Here is a repeatable way to do it by hand in Bluebeam, Revu, PlanSwift, or a spreadsheet.

Small utility contractors lose hours on the same problem every bid. The takeoff is not hard to trace, but once you start sorting sanitary, storm, and water runs by depth, the sheet turns into a pile of numbers nobody can defend at the bid table. This guide is estimating organization only, not engineering or design advice. It is the same method the TrenchCalc workbook builds in.

1. Mark every run with utility, segment, and depth band before you price it

The mistake is pricing straight off the plan and sorting later. Before any quantity leaves the sheet, give each run a consistent label that carries four things: utility type (sanitary, storm, or water), segment or station range, depth band, and any note. A fixed color and label convention in Bluebeam or Revu means a run is already sorted the moment you mark it, instead of being re-read three times.

2. Split runs into written depth brackets, not one average depth

A 400 foot run that starts at 6 feet and ends at 14 feet is not one line item. Priced as a single average depth, it hides the deep footage that drives the real cost (trench box size, spoil, dewatering, crew speed). Break each run at the bracket boundaries you actually price to, for example 0 to 6, 6 to 10, 10 to 16, and over 16, and carry the linear feet in each band separately. This is the single change that most improves both speed and accuracy.

3. Log structures and crossings separately from pipe length

Manholes, inlets, cleanouts, services, and utility crossings are their own quantities and their own cost. Mixing them into mainline footage is how counts get missed and how two estimators get two different numbers off the same plan. Keep a short structure log: type, size, depth, station, and a note. It also gives you a fast second-pass check, because a missing structure is far easier to spot in a list than buried in a pipe total.

4. Write the crew and excavation assumptions next to each bracket

The number you cannot defend after bid day is the one with no assumption written down. Next to each depth bracket, note what you assumed for production: soil, dewatering, shoring or trench protection, rock, surface restoration, and any crossing exceptions. When the question comes ("why is the deep sanitary so high"), the answer is right there on the sheet instead of in your memory from three weeks ago.

5. Build the bid summary once so the next subdivision reuses it

If you retype the bid summary by hand every job, you reintroduce errors every job. Link the summary to the takeoff tabs so depth-band totals roll up automatically, keep sanitary, storm, and water on separate tabs with the same headers, and run one final pass for missing brackets, duplicates, and odd depths. Done once, the same worksheet carries straight to the next subdivision bid with only the quantities changing.

Common questions

What depth brackets should I use?

Use the brackets your own pricing and crew actually change at. Many contractors work in roughly 0 to 6, 6 to 10, 10 to 16, and deeper bands, but the right split is wherever your production rate, trench protection, or dewatering changes. The point is that the boundaries are written down and consistent across the bid.

Do I need special software?

No. This works in whatever you already use to trace, Bluebeam or Revu for markups and PlanSwift or a spreadsheet for quantities. The fix is the method and a consistent worksheet, not another tool to rip in.

How do I keep two estimators consistent?

Share one annotation convention and one worksheet layout. When color, labels, structure log, and bracket boundaries are the same on every job, two people produce comparable takeoffs and a reviewer can follow either one.

Skip the setup and use the workbook

The free depth-bracket QA check shows where a takeoff still needs cleanup before the number goes out. The one-time TrenchCalc workbook gives you the whole method ready to use.

  • Bluebeam annotation convention and depth-bracket worksheet
  • Structure and service log for traceable quantities
  • QA checklist and a bid-summary rollup that links from the takeoff tabs
  • One-time workbook and SOP pack, no subscription