What Is a Schedule of Values (SOV)? A Subcontractor's Guide

The schedule of values is the document that takes a single lump-sum contract price and breaks it into the line items that will be billed against over the life of a project. On a $2M subcontract, the SOV might show 40 lines — mobilization, demolition, site work, foundation, slab, framing, sheathing, roofing, exterior finishes, MEP rough-in, insulation, interior finishes, punch list, and so on — each with a scheduled value that adds up to the contract total.

Every pay application submitted during the project references these lines. The AIA G703 Continuation Sheet is essentially a schedule of values with added columns tracking work completed to date, work completed this period, and stored materials. If you know the SOV structure, you know what every pay app will look like.

Why the SOV Matters

The SOV matters because it is the billing framework for the entire project. A well-structured SOV makes progress measurement objective and makes pay apps fast to review and approve. A poorly-structured SOV turns every pay app into a negotiation, and every closeout into an argument.

The Structure of a Schedule of Values

Most SOVs follow CSI MasterFormat divisions — the construction industry's standard way of organizing scope by trade and system. A sub's SOV typically uses a subset of divisions relevant to their scope, with individual line items beneath each division for specific tasks or assemblies.

How Line Items Get Valued

The scheduled value on each line is the amount the sub will bill for completing that scope item. Values are usually derived from the sub's own estimate — the internal breakdown that went into preparing the bid. A sub with a clean, detailed estimate has a natural SOV; a sub with a rough plug-number estimate has to synthesize one.

The values should reflect the actual cost and reasonable margin for each line, including direct labor, direct material, and an allocable share of overhead and profit. Mobilization and project management lines typically carry overhead load; installation lines carry direct cost plus margin.

Front-Loading the SOV: Why It Gets Rejected

Front-loading is the practice of assigning disproportionately high values to early-project lines (mobilization, demolition, early site work) and correspondingly lower values to late-project lines (finishes, punch list). The motivation is cash flow — getting more money early means less working capital at risk later.

Sophisticated GCs and owners reject front-loaded SOVs on submission because front-loading shifts risk to them: if the sub defaults mid-project, the owner has paid out more than the remaining scope is worth, and completing with another sub becomes expensive. Good-faith SOV negotiation involves the GC's project manager reviewing the breakdown, flagging lines that appear front-loaded, and requesting rebalancing toward a more linear work-to-payment curve.

Unit Price vs. Lump Sum Lines

Most SOV lines are lump sum — a scope item is valued at a fixed dollar amount regardless of the eventual quantity. Some lines are structured as unit prices, particularly for scopes with variable quantities (excavation cubic yardage, linear feet of wiring, square feet of specific finishes). Unit price lines list the unit, the estimated quantity, and the unit rate; the extended value is quantity times rate, and each pay app bills actual completed units at the rate.

Unit price lines are fairer to both sides when quantities are genuinely uncertain, but they add complication at pay app review — the GC has to verify the quantity claimed each period, not just the percent complete.

The SOV and the G703

The SOV lives inside the AIA G703 Continuation Sheet when pay apps use AIA forms. Column A (item number) and Column B (description) are the SOV structure. Column C (scheduled value) is the dollar amount for each line. The remaining columns track the pay app history: what was completed in prior periods, what was completed this period, what stored materials exist, cumulative completed and stored, and retainage.

Over the life of the project, the G703 grows as a living ledger of the SOV plus pay app history. At closeout, the cumulative completed values across all lines should equal the original contract amount plus approved change orders, exactly — no more, no less.

Change Orders and the SOV

Change orders modify the total contract amount, and the SOV has to reflect them. The correct pattern is to add new lines to the SOV for each change order scope — not to modify existing line values. This preserves the audit trail: every original SOV line carries its original value through the life of the project, and every change order has its own traceable line from the period it was approved.

Subs sometimes fold change order work into base contract lines to simplify the paperwork. This creates a reconciliation problem at closeout when the base contract lines exceed 100% complete and the change order lines are at zero despite the work being done. Disciplined change order handling in the SOV prevents the problem.

SOVs in Unit Price Contracts

For contracts that are primarily unit price rather than lump sum — common on heavy civil, grading, and infrastructure work — the SOV becomes a schedule of unit prices. Each line lists the scope, unit of measure, estimated quantity, and unit rate. Pay apps bill actual measured quantities at the rate. Final reconciliation compares total actual quantities across all lines to the estimated total, and the final contract value is the sum of (actual quantity × rate) for each line.

Common SOV Mistakes

Bottom Line

The schedule of values is the foundational financial document of any construction subcontract. A thoughtfully built SOV makes every subsequent step — pay app submission, progress measurement, change order tracking, and closeout reconciliation — cleaner and faster. A careless SOV turns the whole project into a month-by-month billing argument. The time spent getting the SOV right at project start is the single highest-leverage investment in smooth billing for the life of the project.