The schedule of values is where your estimate meets the GC's payment application process — and where a lot of waterproofing subs unknowingly agree to finance the job. A good SOV isn't clever; it's honest, granular, and traceable back to the estimate the job was won on.
Break lines out the way the work happens
One line that says "Waterproofing — $166,603" is an invitation to argue about percent complete every month. Break the SOV out by scope and, on phased jobs, by area:
- Mobilization (per mobilization, if the job phases)
- Below-grade membrane — walls, by pour or elevation
- Deck coating — by building or level
- Sheet metal & counterflashing
- Sealants & expansion joints
- Closeout documents & warranty
Granular lines make progress obvious: when the podium base coat is down, that line is billable, no debate.
Mobilization: honest, not hidden
Front-loading an SOV until it snaps is an old game GCs know well. But mobilization is a real cost you genuinely incur early — crew, equipment, submittals, mockups. Carry it as its own line at its real value, and carry each mobilization on phased work. You'll bill it without a fight because it's defensible.
Keep a closeout line — small, but real
GCs like a retention hook; you like getting the last check. A modest closeout/warranty line gives the GC confidence the paperwork will show up and gives you a clean final bill when it does.
Tie every line to the estimate
The failure mode isn't the SOV format — it's the SOV drifting from the estimate. If the estimate said the deck coating scope was $54,200 and the SOV says $48,000 because someone "rounded," you just donated $6,200 of early billing position. Build the SOV from the estimate's scopes, and when change orders land, add lines rather than absorbing them.
Change orders get their own lines. Always.
Absorbing CO work into base lines destroys both your billing position and your record. A CO line with its own value is the paper trail that survives an audit — and the argument you don't have to have.
The workflow version
In Division 7 Estimating, SOVs are generated from the estimate's scopes — same names, same values, same structure — so the billing story and the bid story are the same story. See how that works in a demo.