Schedule of values (SOV): how to set one up that gets your pay apps approved

Before your first pay application on a commercial job, the GC will ask for a schedule of values — a line-item breakdown of your contract sum. It feels like a formality. It isn’t. The SOV becomes column B and C of every G703 continuation sheet you submit for the life of the project, and its structure quietly determines how smoothly you get paid. A good SOV makes every monthly application easy to justify; a bad one guarantees arguments. Here’s how to build a good one.

What the SOV actually does

The SOV allocates your total contract sum across lines of work. Each month you bill percent-complete per line, so the SOV is the unit of negotiation with whoever reviews your application: the GC (and often the architect) doesn’t certify “you’re 62% done” in the abstract — they certify that line 4 is 80% and line 7 is 30%. Once approved, the SOV is fixed; changing it later requires the GC’s agreement and creates exactly the kind of reconciliation friction you’re trying to avoid. Get it right up front.

Sizing the lines: not too coarse, not too fine

The most common SOV mistake is one giant line — “Flooring: $480,000.” Now every month becomes a debate about a single percentage with no observable basis, and a reviewer who thinks you’re at 55% instead of 65% is cutting your check by $48,000 with nothing to point at.

The opposite mistake — hundreds of micro-lines — makes monthly updates a chore, invites line-level nitpicking, and multiplies the chance of clerical error. The sweet spot is lines that satisfy one test: can someone standing on the job verify this line’s percent-complete by looking?

• Break out by area or phase: “Carpet — Level 2,” “Carpet — Level 3,” “Resilient — OR Suites.” Areas finish at different times, and an area-based line goes to 100% cleanly when the area is done.
• Break out by scope type: floor prep and moisture mitigation separate from finish flooring; base and transitions separate from field material. Different work, different timing.
• Separate material and labor where it helps. A material line can bill when product is delivered or stored (column F on the G703), while the labor line bills on installation. On prevailing-wage work this split also keeps the labor basis clean.

For a typical flooring subcontract in the mid six figures, that usually lands somewhere between 10 and 40 lines.

Include the lines subs forget

• Mobilization / submittals / project management. Real, early-incurred costs deserve early-billable lines. A reasonable mobilization line lets you bill honestly in month one instead of inflating percent-complete elsewhere.
• Closeout / punch. A modest line for closeout documents, attic stock, and punch work gives the final application something honest to bill — and gives the GC comfort that you’re not 100% before punch is done.
• Freight/delivery or storage, if your contract treats them as compensable and they’re material to your cash flow.

Front-loading: the temptation and the line

“Front-loading” means weighting early-completed lines above their true cost so cash arrives sooner. Reality check: modest weighting of genuinely early costs (mobilization, submittals, material procurement) is normal and defensible. Aggressive front-loading is a different animal — experienced GC accountants spot it, it can get your SOV rejected before the job starts, and if it works you’ve created a job that’s cash-starved at the end, exactly when punch work and retainage already squeeze you. If your costs genuinely arrive early, show that honestly with real lines; don’t bury it in inflated unit values.

Mechanics that keep future pay apps clean

The lines must sum to the contract — exactly

Column C totals your contract sum to the penny, every month. Build the SOV so it does, and never “absorb” rounding by nudging a line later.

Change orders become new lines

When a change order is approved, add it as its own line (or clearly grouped lines) rather than inflating an existing line’s scheduled value. Separate lines keep the original contract auditable, make Line 2 of the G702 (net change by change orders) easy to verify, and matter even more for deductive change orders, which need to appear as explicit negative adjustments rather than silent shrinkage. And don’t bill change-order work before the change order is executed — billing unapproved COs is a top-tier rejection reason.

Think about retainage timing

Retainage is typically held uniformly, but your SOV still affects when it comes back: lines that complete early (mobilization, early areas) accrue retainage that then sits until release. Where your contract allows line-item release at area turnover, area-based lines are what make that possible.

Match how you track costs

If your SOV lines map loosely to your estimate and cost codes, monthly percent-complete becomes a look-up instead of a guess, and you get earned-value visibility (billed vs. cost per line) for free. If the SOV is structured like nothing else in your business, every month requires translation — and translation is where errors breed.

Get it approved before application #1

Submit the SOV for the GC’s review before or with your first application, per your subcontract. An SOV dispute embedded in a pay-app dispute delays money; the same dispute settled up front costs nothing. Many GCs have preferences (their cost codes, their grouping, a cap on mobilization) — better to learn them in week one.

A quick checklist

1. Lines verifiable by observation, roughly 10–40 for a mid-size job
2. Broken out by area/phase and by scope type
3. Material vs. labor split where storage billing or payroll needs it
4. Mobilization and closeout lines included, honestly sized
5. Totals tie to the contract sum exactly
6. Change orders planned as separate lines, billed only when executed
7. Structure mirrors your estimate/cost codes
8. GC approval in hand before the first application

The takeaway

Your SOV is the one billing document you get to design. Every G703 you submit afterward inherits its structure, and every approval conversation happens on its terms. Spend the hour up front: a well-structured SOV means monthly applications that reviewers can verify at a glance — and applications that are easy to verify are applications that get certified the first time.