How to Build a Schedule of Values That Bills Clean

Start from the contract sum and make it add up

The schedule of values divides the total contract amount into line items, each carrying a scheduled value, so that the sum of all lines equals the contract sum exactly. This is the document that drives the G703 continuation sheet behind your G702 pay application.

Every dollar of the contract must land on a line. If your lines do not foot to the total, the architect will reject the application before reading anything else. Tie the values back to your estimate so the SOV reflects how the money is really distributed across the work, not a guess made the night before the first draw.

Choose the right granularity

Granularity is a tradeoff. Too coarse and you cannot bill for work that is genuinely done because it is buried inside a giant line that is only half complete. Too fine and you create a tracking burden and hand the architect dozens of small lines to question.

The sweet spot lets you bill each meaningful chunk of work as it earns, without splitting hairs. A practical rule: break out a line whenever a portion of the work will reach completion on a clearly different timeline than the rest.

• •Break out by phase, area, or building system so you can bill completed work without waiting on the rest
• •Separate labor-heavy scopes from material-heavy scopes when they progress on different schedules
• •Avoid lines so small they create a tracking nightmare and invite line-by-line disputes
• •Keep a single, oversized catch-all line off the SOV, because you can never bill it cleanly

Reasonable front-loading versus what gets rejected

Front-loading means weighting early line items so you collect cash sooner to cover real up-front costs. Legitimate front-loading reflects costs you actually incur early; aggressive front-loading hides profit in early lines and gets caught.

Mobilization, bonds, insurance, and general conditions are defensible early lines because that money really does go out the door at the start. What architects reject is value shifted onto early lines with no cost behind it, leaving the back end of the job underfunded. The test is simple: can you justify the early value with real early cost? If not, the architect will redistribute it for you and you will have spent credibility for nothing.

• •Defensible: mobilization, bonds and insurance, submittals and engineering, general conditions
• •Risky: padding finishes or sitework early when the cost lands much later
• •Self-defeating: stripping value off late lines so closeout work is underfunded and retainage hurts more

Mobilization and stored materials lines

Two lines deserve special attention because they govern early cash. A mobilization line captures the real cost of setting up the job, and a stored materials provision lets you bill for material purchased and stored but not yet installed.

Stored materials billing usually requires the contract to allow it, plus proof the material is paid for, properly stored, insured, and dedicated to the project. Set up the SOV to accommodate stored materials from the start rather than scrambling to add a line mid-job when a long-lead order shows up on site and you need to bill for it.

Tie the SOV to your cost codes

The SOV is a billing document, but it should map cleanly to your job-cost codes so revenue and cost speak the same language. When your SOV lines align with your cost codes, you can compare what you have billed against what you have spent on the same structure and see your earned margin line by line instead of guessing at the job level.

In Field PM, aligning your schedule of values with your budget cost codes means each pay application is built from the same line structure your job-cost report uses, so progress billing and budget-versus-actual reconcile automatically. For the mechanics of turning a finished SOV into a certified pay application, see how G702 and G703 work together.