Schedule of values & the payment application, explained
On a lump-sum construction contract, you don't get paid at the end — you bill for progress every month. And the document that makes that happen has a reputation for being fussy: a schedule of values, an application for payment, retainage on two kinds of value, previous certificates, a balance to finish. Miss a line or transpose a number and the whole thing won't foot, the architect kicks it back, and your payment slips a cycle. It's not actually complicated. It's just unforgiving, and it rewards understanding why each line is there.
This is a plain-English walk through how progress billing works — what a schedule of values is and why it has to tie to the contract sum, how the payment application computes what you're owed this period, how retainage and stored materials fit in, and why an approved change order is the only kind that touches your contract.
The schedule of values: your contract, sliced into billable pieces
A schedule of values (SOV) is your contract sum broken into line items, each with a dollar value, so that progress can be measured and billed piece by piece. Instead of one $500,000 number that's impossible to bill against partially, you have thirty or forty lines — mobilization, foundations, framing, roofing, mechanical, and so on — each carrying its share of the total.
The rule that makes an SOV valid is simple and absolute: the sum of the line values equals the contract sum. Not approximately — exactly. The SOV isn't a separate estimate; it's the contract, re-sliced. Owners and lenders lean on this because it's how they'll judge every future bill: if line values didn't add up to the contract, "percent complete" would mean nothing.
How the payment application actually foots
Each billing period you submit an application for payment — the summary sheet, in the widely used AIA G702/G703-style format, that owners, architects, and lenders already recognize. (The industry-standard forms are published by the AIA; a well-built spreadsheet simply follows that format and is not an AIA® document.) The application walks down a fixed set of lines, and every one is arithmetic:
- Original contract sum — where you started.
- Net change by change orders — the total of approved change orders (more on that below).
- Contract sum to date — the two lines above, added. This is what the job is now worth.
- Total completed & stored to date — from the SOV: work done from prior periods, plus work done this period, plus materials stored on site but not yet installed.
- Retainage — the percentage held back on that completed-and-stored amount (below).
- Total earned less retainage — line 4 minus line 5. What you've genuinely earned so far.
- Less previous certificates — everything already billed and paid in earlier applications.
- Current payment due — line 6 minus line 7. The check you're asking for this period.
- Balance to finish, plus retainage — what's still left in the contract. A running check that everything ties out.
The reason it foots every time — when it's built right — is that the SOV feeds the application. You enter this period's progress once, on the schedule of values; the application reads the totals. When people bill by retyping numbers into the summary by hand, that's where transpositions creep in and applications bounce. Tie the summary to the schedule and the math can't disagree with itself.
Retainage: the money you've earned but can't collect yet
Retainage (or retention) is a percentage — commonly 5% or 10%, set by your contract — that the owner withholds from each payment until the job is substantially complete. Bill $50,000 of work at 10% retainage and you collect $45,000 now; the $5,000 is held as the owner's assurance you'll finish and close out properly.
Two things trip contractors up:
- Retainage applies to stored materials too, in most contracts — the held-back percentage comes off completed work and material you've stored on site but not installed.
- Retainage accumulates. By late in a job the held-back amount can be a serious sum — often your entire profit and then some — sitting in the owner's account. Knowing exactly what's being held, and following your contract's rules for reducing or releasing it, is real money. A good application shows retainage held to date as its own figure, not buried.
Stored materials and change orders: the two special cases
Stored materials let you bill for major items delivered to the site (or sometimes stored off-site under bond) before they're installed — so you're not floating the cost of a $40,000 switchgear for two months waiting to set it. It's a distinct column on the SOV, usually with its own documentation requirements. It counts toward completed-and-stored, and retainage applies.
Change orders are where applications most often go wrong, and the rule is strict: only an approved change order moves the contract sum. A pending change — priced, submitted, not yet signed — is not contract money and must not appear in "net change by change orders." Put it in and your application overstates the contract, the architect catches it, and the whole thing bounces. Approved COs get added to the SOV as their own lines so they can be billed like everything else. (For the extra work that hasn't been formalized into a CO yet — the T&M tickets and field directives — that's a tracking problem of its own, worth keeping separate until it's approved.)
The Construction Payment Application + Schedule of Values
An original Excel workbook in the standard AIA-style format: an application for payment, a self-totaling schedule of values, retainage on completed work and stored materials, and a change-order log where only approved COs move the contract sum. Enter this period's work once; the application computes completed-and-stored to date, retainage, current payment due, and balance to finish — and the SOV always ties to the contract sum, so it foots every time. Pure formulas, no macros. An original template that follows the format — not an AIA® document.
Billing and costing are two different books
One last distinction worth holding onto: the payment application tells you what you can bill — it's the revenue side, the story you tell the owner. It says nothing about whether the job is actually making money. You can be perfectly current on your billings and quietly losing your margin, because billed-to-date and cost-to-date are two different books. The application manages your cash in; job costing manages your margin. A healthy contractor runs both, and never confuses one for the other — and prices the work well in the first place (which is where the bidding numbers come in).
Get the schedule of values right, let it feed the application, keep pending change orders out of the contract sum, and watch your retainage like it's the money it is. Do that and progress billing stops being the monthly headache that delays your check and becomes what it's supposed to be: a clean, recognized document that gets you paid on time.
This is general information about construction progress billing, not accounting, tax, or legal advice, and not a substitute for your contract. "AIA" and "G702/G703" refer to documents published by The American Institute of Architects; Quire Paper is not affiliated with, endorsed by, or sponsored by the AIA, and our template is an original work that follows the common format — it is not an AIA® document. Retainage rules, stored-material terms, and lien and payment rights vary by contract and jurisdiction — follow your contract and consult a qualified professional.