The Schedule of Values Is Your Cash-Flow Blueprint — Here's How to Build One That Pays You Faster

A schedule of values (SOV) is the line-by-line breakdown of your total contract sum — every portion of the work assigned a dollar value. On most commercial jobs it lives on two AIA forms: G702, the Application and Certificate for Payment, the one-page cover you submit each billing period, and G703, the Continuation Sheet, the itemized backup that does the actual math. G702 summarizes the contract sum, change orders, completed and stored work, retainage, and the payment due; G703 breaks it down line by line. Neither works without the other.

Most subcontractors treat the SOV as a formality — a form the GC's accounting team demands at buyout. That's a costly misread. The SOV is the baseline every single progress payment is measured against for the life of the job. If a line item is too coarse, you can't bill partial progress on it cleanly; if it's structured well, you get paid for exactly what you've completed, when you've completed it. It is, in effect, the blueprint for your cash flow on that project.

The stakes aren't abstract. According to Rabbet's 2024 Construction Payments Report — a construction-fintech survey, so read it as directional rather than census data — slow payments cost the U.S. construction industry an estimated $280 billion in 2024, and 82% of contractors reported payment delays beyond 30 days, up from 49% two years earlier. Your payment terms are largely dictated by the contract, as our look at the industry's 56-day wait explains, but how you structure and submit your SOV is one of the few levers fully in your hands.

Granularity is your friend. A line item that lumps a whole phase into one number forces you to wait until that phase is far along before you can bill meaningfully. Breaking the same scope into several smaller, logically sequenced line items lets you capture progress as it happens — you bill the portion that's genuinely complete instead of rounding a giant lump down to a conservative percentage. The tradeoff is that overly granular SOVs invite line-item scrutiny, so aim for detail that mirrors how the work actually gets built and inspected.

Two line items matter disproportionately for cash. The first is mobilization — a legitimate early line covering setup, temporary facilities, and initial overhead, which recovers real upfront costs honestly. The second is stored materials. G703 has a dedicated column for materials presently stored — delivered to the site or a bonded warehouse but not yet installed — which lets you bill for a big material buy weeks before it goes in place. GCs typically require proof (invoices, a bill of sale, sometimes insurance), but done right it pulls a major cash outlay forward significantly.

Retainage is the structural drag you plan around. It appears as its own G703 column, usually 5–10% withheld from every application and released at or after completion — which is why retainage law and negotiation deserve attention before you sign. Watch for underbilling, too: when your costs run ahead of your billings, you're financing the job out of your own working capital, and the gap hides in your cash balance rather than your profit-and-loss statement. A disciplined SOV keeps billings tracking close to costs.

Front-loading means weighting your early SOV line items — mobilization, general conditions, the first trades on site — above their true cost, so you collect more cash early and offset retainage and upfront outlays. It's common, and modest front-loading isn't automatically improper. But it's a spectrum, and the far end is billing for work you haven't performed. Levelset's analysis of front-loading puts it bluntly: aggressive overbilling is a great way to ruin relationships and can even create legal exposure.

The risk has two sides. Contractually, if you front-load heavily and then default or walk mid-job, the GC and owner have overpaid for incomplete work, and the remaining line items won't cover the cost to finish — exactly the scenario a GC's default and backcharge provisions are written to punish. On public projects the exposure escalates: billing for work not performed can implicate prompt-payment requirements and, in serious cases, false-claims liability.

Owners and architects police it, too. The architect reviews each application's line items against a realistic sense of progress and can reject amounts that outrun observed completion; retainage sits there as a backstop. The honest alternative captures most of the cash-flow benefit without the risk: use a legitimate mobilization line, bill stored materials aggressively but truthfully, and structure enough line-item detail to recognize real progress early. You protect your cash and your relationship at the same time.

Some of the most expensive payment delays aren't the GC's doing — they're baked into a sloppy application. The classic is a mismatch between the G702 summary and the G703 detail: the numbers don't reconcile, so the whole package bounces back and you wait another cycle. Billing a percentage that visibly exceeds actual progress invites the same rejection. Both are unforced errors that cost a full billing period each time — and a billing period, on today's timelines, is weeks.

The paperwork around the application trips people up just as often. A missing or incorrect lien waiver — required with most pay applications — stalls payment until it's corrected, which is why understanding conditional vs. unconditional lien waivers matters. So does billing for stored materials without the backup the contract requires, or billing a change order before it's been formally approved (see change orders and cardinal change). Each gap hands the GC's accounting team a legitimate reason to hold your money.

Timing is the quiet killer. Most GCs have a hard monthly cutoff, and an application submitted a day late doesn't get pro-rated — it waits for the next cycle, pushing your payment out by weeks. Build your internal billing calendar around the GC's cutoff, not your own convenience, and treat the pay application with the same rigor you'd give a bid. The firms that get paid fastest are usually the ones whose applications never give anyone a reason to say no.

Cash-flow pressure is intensifying, not easing. Billd's 2025 National Subcontractor Market Report — again, a lender's survey, so directional — found subcontractors waiting an average of roughly 56 days to get paid while GCs estimated around 30, and about one in three subs dipping into personal or retirement savings to bridge the gap. When the average wait is that long, every self-inflicted delay on top of it compounds a problem that's already straining the business.

That's why the SOV deserves strategic attention, not just administrative box-checking. It's one of the few points in the payment process you control end to end: how you break down the work, how you capture stored materials, how clean your applications are, and how reliably you hit the cutoff. Firms that treat it as a cash-flow instrument — reviewed as carefully as the contract itself — routinely get paid faster than competitors doing identical work under identical terms. It's also part of why so many firms walk away from otherwise-profitable work: the cash mechanics, not the margin, decide what they can take on.

A careful contract review sets the ceiling; a well-built SOV determines how close you get to it. Before you sign, know what the contract says about retainage, stored materials, billing cadence, and pay-if-paid language — the terms that decide how much of your good SOV work actually reaches your bank account. See how RCS flags payment and cash-flow terms on every contract, so your schedule of values is working with the contract instead of against it.