How to Build a Schedule of Values You Can Actually Bill Against

It's the 25th of the month and the progress claim is due. The schedule of values came straight out of the estimate the week the contract was signed, and one line on it reads "Structural concrete: $1,800,000." The concrete is maybe 40 percent done. The owner's consultant walks the site and calls it 30. Neither of you can prove your number, because the line is too big and too vague to measure, and the difference is $180,000 of this month's cash flow being settled in a parking lot conversation.

Most contractors treat the schedule of values as contract paperwork. Fill it in, get it approved, file it. But it's the instrument you bill against every month for the life of the job. Every progress claim, every review meeting, every argument about percent complete happens on the structure you locked in during week one. A bad SOV doesn't fail loudly. It just quietly turns every billing cycle into a negotiation you're not equipped to win.

An estimate breakdown is not a billing breakdown

The estimate is organized around how you priced the work: takeoff quantities, crew rates, supplier quotes, subcontractor packages. The schedule of values needs to be organized around how you'll measure the work, month after month, in a way a reviewer can verify without taking your word for it.

Those are different structures. An estimate line like "Site works" might be perfectly fine for pricing and useless for billing, because "Site works" on a real project is clearing, excavation, backfill, and grading happening in different areas across five months. What percent complete is "Site works" in month two? Whatever you and the consultant can agree on, which is to say: an opinion.

The practical consequence is that whoever bills the job should build (or at least review) the SOV before it goes to the owner, not inherit it from the estimator after the fact. The estimator's job was to get the price right. The project manager's job is to get paid for two years. The document should serve the second job.

The three ways an SOV fails at billing time

Lines too big to measure. Any line where percent complete is a judgment call rather than a measurement is a line you will eventually argue about. The bigger the line, the more expensive the argument. A single $2M line disputed by ten percentage points is $200,000 of cash flow riding on whose gut feel wins. Ten $200K lines, each tied to something countable, almost never produce that argument, because most of them are either clearly done or clearly not.

Lines that don't match how the field measures. If your crews track piles driven, cubic metres poured, and lineal metres of pipe in the ground, but your SOV is broken out by contract phase or by estimate discipline, then every month somebody translates field quantities into SOV percentages by hand. That translation is where claims get soft, and soft claims get cut.

No relationship with your cost codes. When a reviewer pushes back on a line, your best evidence is your own cost report: here are the hours, here's the material delivered, here's the sub's invoice for that scope. That only works if the SOV line maps cleanly onto one or more cost codes. If the SOV and the cost structure were built by different people at different times, you can't support your claim with your own data, and you're back to opinions.

What a billable structure looks like

Break lines until they're measurable. The test for each line: could a reasonable person verify percent complete from a site walk or a quantity sheet? Quantities are best (poured, driven, installed, backfilled). Where the work doesn't lend itself to counting, use milestones that are binary: formed, inspected, energized, commissioned. A line that's "either done or not" can't be argued down.

Keep judgment lines small. Some scope is genuinely hard to measure. Fine. Keep those lines small enough that a percent-complete argument over them isn't worth anyone's time.

Give time-based costs their own lines. Site supervision, trailers, and general conditions burn by the month, not by physical progress. Put them on their own line and bill them on elapsed duration. Burying them inside physical scope lines means you either under-recover them early or get accused of front-loading later.

Be straight about mobilization. Mobilization is real money and belongs on its own line, sized to actual mobilization cost. Reviewers know what front-loading looks like, and an inflated mob line buys you one good month and then a reviewer who scrutinizes everything else you submit for the rest of the job. Whatever early cash it gains you, it costs more in credibility, and you'll finance the back end of the job at a discount you created.

Mirror your cost codes. Ideally the SOV and the cost code structure are two views of the same breakdown, built together at handoff. Then the monthly claim and the monthly cost report reinforce each other instead of contradicting each other, and the same quantity sheet feeds both.

The monthly routine

A good structure still needs a routine behind it.

Draft the claim from field quantities a few days before cutoff, not from memory at the deadline. Walk the pencil copy with the owner's representative before you submit formally, so disagreements surface in a conversation instead of in a certified payment cut. Keep the backup (quantity sheets, delivery tickets, photos) assembled as you go, because backup gathered after a challenge always looks like backup manufactured for one.

And when a change order is approved, give it its own SOV line that month. Folding approved changes into existing base-contract lines is how change work disappears from billing, and it wrecks the measurability you set up in week one.

The BC wrinkle: the clock is about to matter

BC's prompt payment legislation has Royal Assent and is coming into force by regulation. When it does, payment timelines and dispute windows get statutory teeth, and a percent-complete argument that used to drag on for a billing cycle or two will have to be raised, documented, and resolved on the clock. A schedule of values built on measurable lines is the cheapest dispute-prevention tool available: most of what people fight about simply stops being arguable.

The tradeoff, honestly

More lines means more admin. A 200-line SOV on a $3M job is its own failure mode; you'll spend claim day updating rows instead of managing work. The target isn't maximum detail, it's no line you can't defend. On most mid-size civil jobs that lands somewhere between 25 and 60 lines, but the number matters less than the test: measurable, mapped to your costs, and matched to how the field already counts.

One more thing: the owner's consultant reviews and approves the SOV, and they can reject your structure. Have that negotiation at contract award, when you have leverage and goodwill, not in month four when you're trying to restructure lines mid-stream.

At Manara we spend a lot of time on exactly this seam, where field measurement, cost tracking, and billing either line up or quietly fight each other. If your progress claims take too long to build or come back cut more often than they should, a short discovery call is an easy way to find out whether the problem is the process or just the paperwork it runs on.