Building a Schedule of Values That Survives the First Pay Application

The schedule of values (SOV) is the backbone of progress billing on any lump-sum or GMP contract. It breaks the total contract amount into individual billing line items — each with a dollar allocation, each tracked for percent-complete on every pay application. It's what the AIA G703 form is designed to capture, and it's the single document every month's billing will reference.

Building a good SOV at the start of a project is one of the higher-leverage administrative activities a contractor does. A clean SOV supports clean billing cycles for the life of the project. A sloppy SOV creates arguments about percent-complete every month and invites front-loading disputes that eat both sides' time.

Granularity: How Detailed to Go

The biggest tradeoff in SOV design is granularity. Too coarse — say 10 lines on a $10M project — and every percent-complete assessment becomes a debate because each line covers too much work. Too fine — 400 lines on the same project — and the administrative load of tracking each line monthly is disproportionate to the benefit.

A reasonable baseline is one line per significant scope element per trade, with specialty work broken out further where it has distinct phases. A general contractor's SOV for a $10M commercial building might have 40-80 lines. A structural steel sub's SOV might have 15-25 lines. A mechanical sub's SOV might have 30-50.

Cost Loading

Each SOV line needs a dollar value. The sum of lines must equal the contract value (or GMP). The allocation should reflect the actual cost of each scope, plus fair allocation of overhead and profit across the lines.

Cost loading is where architects and owner's reps push back most. They're looking for lines that are inflated relative to the cost of the work — mobilization at 10% of contract when actual mobilization cost is closer to 3%, site work at double the sub's quoted price, etc. Overinflated early-phase lines get called out because they enable front-loading.

The Front-Loading Problem

Front-loading is the practice of shifting dollar allocations toward early-phase lines so the contractor collects more cash earlier than the work is actually being performed. A contractor who loads mobilization at 10% when it's really 3% pulls $700K of cash forward on a $10M project. When the project completes, the total billing still equals contract value — but along the way, the contractor was paid ahead of earned work.

Owners fight front-loading because it increases their risk — if the contractor walks mid-project, the owner has paid for work that hasn't been done and has to recover from the contractor or the surety. The negotiated SOV is the vehicle for controlling this.

General Conditions as Separate Lines

General conditions (GC costs) — supervision, field office, temporary utilities, site security, consumables — are typically broken into their own SOV lines. Some contractors lump them into a single line; others break them by category. Monthly billing against GC lines is usually earned in proportion to time elapsed, not physical progress, because GCs accrue daily regardless of specific work done.

Breaking GC lines out separately lets the monthly earned calculation handle them differently. A well-structured SOV might bill GCs as 1/12 of the line per month on a 12-month project, rather than trying to attribute them to percent-complete on specific trade lines.

Stored Materials Handling

Some SOVs carve out stored materials as their own line items. When the contract allows billing for materials stored on site (or at a bonded off-site location), the SOV can identify specific major material items that will be billed on delivery rather than on installation — structural steel, long-lead equipment, specialty finishes. This creates a distinct billing path for those items independent of their installation progress.

Without separate stored-materials lines, stored-materials billing has to be accommodated within each trade line, often creating awkward pay-app calculations where the installed portion is at one percent-complete and the delivered-but-not-installed portion is at another.

Change Orders and the SOV

As change orders get executed, the contract value changes. The SOV should update to reflect the new contract total. Common practice: each approved change order becomes a new line on the SOV, with its own dollar value and percent-complete tracking. Some contractors roll change orders into the affected trade lines instead, though this makes reconciliation harder at closeout.

The change-order-as-separate-line approach produces a cleaner audit trail — every approved change order can be traced to its specific SOV line, its billings, and its closeout. For projects with many change orders, this structure is worth the slight SOV expansion.

The Line Description Discipline

Vague line descriptions are a common source of monthly pay-app friction. A line that reads "Interior Finishes — $1,200,000" on a pay app can mean anything. When the contractor reports 35% complete and the architect thinks it's 20%, neither side has a specific reference point. The contractor says the tile is in; the architect says the paint isn't. Without line-level specificity, the dispute has nowhere to go.

Better line descriptions are specific: "Interior Finishes — Paint (floors 1-3)" $180K; "Interior Finishes — Tile" $220K; "Interior Finishes — Casework" $450K; etc. Each is a discrete scope whose progress can be assessed directly. The total still equals the category total, but the monthly discussion is concrete rather than abstract.

Subcontractor Alignment

The GC's SOV should reconcile to the subcontractors' own billing structures. If the mechanical sub invoices the GC in lines that don't match the GC's SOV lines for mechanical scope, every month's pay-app cycle requires reconciling two different breakdowns. This is tedious and error-prone.

The cleanest approach: the GC's SOV for each trade scope maps 1:1 or N:1 to the sub's subcontract breakdown. When the sub bills, their lines roll up into the GC's SOV lines without transformation. Some GCs require this explicitly in their subcontracts — the sub's monthly billing must align with the GC's SOV categories.

Closeout Reconciliation

At project completion, every SOV line should reconcile — billed amount equals allocated amount, percent complete equals 100%. Lines that haven't been fully billed are places where money is still on the table. Lines that have been over-billed (possible if change orders were misallocated) need to be corrected on the final pay application.

A clean SOV makes closeout reconciliation a simple arithmetic check. A messy SOV makes closeout a line-by-line investigation of what was billed when, why some lines don't reconcile, and how change orders affected the totals. The difference is the thirty minutes of closeout reconciliation versus the three days of it.

Bottom Line

The schedule of values is the document that governs every monthly pay application on a lump-sum or GMP contract. A good SOV is granular enough to allow specific percent-complete assessments, cost-loaded defensibly to avoid front-loading disputes, aligned with subcontractor billings, and maintained cleanly as change orders execute. The investment at contract execution pays dividends every month of billing for the rest of the project.