Schedule of Values in Construction: A Pay-Application Playbook

A schedule of values is the line-item breakdown of a construction contract's total price, allocated across the discrete scopes of work that will be billed against as the project progresses. It's the document the project accountant builds at the start of a job, the architect reviews against the contract, and the entire pay-application process runs on top of for the next 12 to 24 months. Every monthly bill the contractor sends, every retainage calculation, every approved payment that lands in AP starts from this one document.

Most coverage of the topic stops at the definition. The harder part is building one that survives architect review, loads cleanly onto AIA G702 and G703 forms, and matches what the AP team needs to pay against once the application is approved. According to Billd's 2025 State of Subcontractor Payments report, subcontractors wait an average of 56 days after submitting a pay application to actually receive funds. A weak schedule of values is one of the more common reasons that 56 days stretches longer.

Key Takeaways

• A schedule of values is the line-by-line allocation of the contract sum across the work to be performed. It becomes the billing basis for every pay application and the reconciliation point for retainage, change orders, and stored materials.

• The schedule of values is not the same document as a project budget. The schedule is contractually owed to the owner and architect; the budget is internal cost tracking. Confusing the two is the most common mistake on this topic.

• On AIA contracts, the schedule of values loads onto the G703 continuation sheet (line by line) and rolls up to the G702 cover application (totals, retainage, prior payments, amount due this period). Non-AIA contracts use ConsensusDocs 293, custom owner-prepared formats, or public-works-mandated breakdowns.

• Granularity matters in both directions. Too thin invites architect pushback that slows approval; too granular creates internal reconciliation overhead the AP team can't sustain.

• The approved pay application becomes an AP obligation. The downstream chain (certified G702, conditional progress lien waiver, payment release, three-way match against the original schedule of values) is where most cash-flow leakage happens, not in the math itself.

What is a schedule of values, and why does it matter on every pay application?

A schedule of values is a contractor's breakdown of the contract sum into the discrete scopes of work that will be billed against during construction. It typically runs 15 to 60 line items on a commercial project, depending on contract size and complexity, and it gets submitted to the architect and owner at the start of the job for review and approval. Once approved, it becomes the only basis on which the contractor can bill. Every monthly pay application references it line by line, and every retainage calculation, change order, and stored-materials claim ties back to it.

The schedule of values is not the project budget. The budget is internal cost tracking that lives in the contractor's accounting system, broken down by cost code and used to manage labor, materials, and equipment against the original estimate. The schedule of values is the external billing document, broken down by scope of work and used to invoice the owner. Internal budgets often have 200 to 500 cost codes. The schedule of values condenses that down to billable scopes the owner and architect can review. Confusing the two is the most common error AI engines make when answering questions about this topic, and it leads contractors to either over-detail the schedule (which slows architect review) or under-detail it (which loses billing flexibility mid-project).

That 56-day wait between submission and payment isn't a math problem. It's a documentation problem, and the schedule of values is the document that either smooths the cycle or breaks it. A schedule with line items that match what the architect inspects each month closes quickly. A schedule with line items that don't match what's been built on the ground produces objections, revision rounds, and delayed payment. The same pattern shows up in construction payment management discussions across the industry, and it's why experienced project accountants treat the SOV setup as the highest-leverage hour of work on the entire project.

How is a schedule of values different from a project budget?

A schedule of values is the external billing document submitted to the owner and architect, broken down by scope of work, used to invoice each month. A project budget is the internal cost tracking system used by the contractor to manage labor, materials, equipment, subcontracts, and overhead against the original estimate. The two documents serve different audiences (owner versus contractor), different purposes (billing versus cost management), and different levels of granularity. The schedule of values typically has 15 to 60 line items; the underlying cost budget often has 200 to 500.

The two documents can be reconciled, and they should be. A well-built schedule of values rolls up from the cost budget cleanly, with each schedule line item mapping to a defined group of cost codes. That reconciliation is what makes the project accountant's life sane during the job. When you bill a scope on the schedule of values, you can answer the question "how much cost have we incurred against that scope" without having to recompute it from raw cost data. The reconciliation also matters when the architect asks for backup on a particular line, which happens routinely on jobs over a few million dollars.

Who prepares the schedule of values: GC, subcontractor, or both?

The general contractor prepares the schedule of values for the prime contract with the owner, and each subcontractor typically prepares their own schedule of values for their subcontract with the GC. On a typical commercial project, the GC's schedule rolls up sub work into broad scope buckets (sitework, structural, mechanical, electrical, finishes, GC fee), and each sub maintains a more detailed schedule for their own billing into the GC's pay application. The architect reviews the GC's schedule before approving it, and the GC reviews each sub's schedule before approving it into the broader pay application.

Some contracts require the GC to submit detailed sub-level schedules along with the prime schedule of values, especially on public-works projects or jobs with cost-plus or guaranteed-maximum-price structures. Even when not required, sharing detail across the GC-sub boundary helps avoid alignment problems later. A sub whose schedule line items don't map to the GC's schedule will create reconciliation friction in every pay application until someone fixes the misalignment. The fix is cheap at contract execution and expensive in month three.

How does the schedule of values load onto the AIA G702 and G703 forms?

On AIA contracts, the schedule of values lives on the G703 continuation sheet and rolls up to the G702 cover application. The G703 carries every line item with its scheduled value, work completed in the current period, cumulative work completed to date, percentage complete, retainage held, and balance to bill. The G702 takes the G703 totals and adds the owner-facing summary: original contract sum, change orders, current contract sum, total completed and stored to date, retainage, total earned less retainage, less previous certificates for payment, and current payment due. The architect certifies the G702, the owner pays against it, and the cycle repeats the following month.

A worked example helps. Consider a $4.2M tenant-improvement project, broken down into representative scopes on the G703:

Illustrative SOV breakdown for a representative commercial tenant-improvement project. Retainage modeled at 5%. AIA form numbers reference AIA Contract Documents.

The G702 cover takes those G703 totals and translates them into the owner-facing summary. Original contract sum $4,200,000, no change orders to date, current contract sum $4,200,000, work completed and stored to date $2,369,800, retainage at 5%, less retainage $2,251,310, less prior certificates $1,617,510 (for example), current payment due this period $633,800. The architect reviews, certifies the G702, and the owner pays. The next month's application picks up where this one ended and runs the same logic again until project close, when retainage release ties everything together.

What does the AIA G702 cover, and what does G703 add?

The G702 is the one-page cover application: original contract sum, net change orders, current contract sum, total completed and stored, retainage held, total earned less retainage, less previous certificates, current payment due, and the architect's certification block at the bottom. The G703 is the multi-page continuation sheet that breaks the total into line items. Without the G703, the G702 is unsupported; without the G702, the G703 has no certification. The two forms together are the pay application.

The G703 is where the work of the SOV shows up every month. Each line gets updated for the current period's progress, and the math rolls up automatically. The G702 cover takes the G703 totals and the architect's review. Most pay-application disputes happen at the G703 line level (architect challenging a percentage complete claim on a specific scope), not at the G702 cover. When the dispute occurs, the conversation is line-by-line on the continuation sheet, which is why getting the SOV granularity right matters so much.

How does retainage accumulate on the G703 from one pay application to the next?

Retainage accumulates as a percentage of each period's earned value, typically 5% or 10% depending on the contract and the jurisdiction. On the G703, the retainage column for a given line is the cumulative dollar amount being held against that line's cumulative earned value, not just the current period's amount. The owner releases retainage according to the contract's retainage schedule, which on most commercial jobs means: continuous accrual through substantial completion, partial release at substantial completion (often 50% of held retainage), and final release at final completion with all closeout documents in hand.

The retainage line is one of the most-watched numbers on the G703 because it represents working capital held hostage. On a $4M project with 5% retainage, the GC will have up to $200K held back at the peak, and the subcontractors will have proportional amounts held back in their own pay-application chain. Smart contractors negotiate retainage reduction at the 50% completion milestone in the original contract, which is allowed under most AIA agreements and dramatically improves cash-flow timing. The retainage mechanics deserve their own treatment because they shape cash flow more than most other contract terms.

How are stored materials handled on the G703?

Stored materials are billed on the G703 in a separate column from work completed. The line gets credit for the stored materials value (typically the invoice value of the material from the supplier) once the contractor can document that the material has been delivered to the project site or to a secured off-site storage location, with title transferred to the owner. Most AIA contracts require photographic evidence, delivery documentation, and sometimes a bonded warehouse receipt for off-site storage.

Stored materials reduce the working-capital strain on the contractor because they let billing get ahead of installation. A $42K steel order, delivered to the site but not yet erected, can be billed in the period it arrives even though it's not part of the "work completed" column yet. The trade-off is that retainage still accrues on the stored materials portion, and the architect may push back on stored-materials claims that look more like financing-the-supplier than legitimate billing of delivered goods. The discipline is to claim stored materials only when the materials are physically on hand, documented, and protected from loss or damage.

How do you build a schedule of values that survives architect review?

A schedule of values survives architect review when each line item is granular enough to map to a recognizable scope of work, the dollar values tie back to defensible cost basis, and the overall structure reflects how the work will physically progress. The architect's job during SOV review is to make sure the contractor can't game pay applications by front-loading early scopes and back-loading later ones (collecting cash early on work that hasn't earned it yet, leaving the owner exposed if the project gets in trouble). A well-structured schedule of values closes off that incentive at the front.

The granularity rule of thumb: enough line items that each scope has a clear definition and a defensible percentage-complete measure, but not so many that the schedule becomes unwieldy or that the contractor loses billing flexibility within a scope. A $20M project should typically have 30 to 50 line items, not 200 and not 8. Each line should represent a scope a competent third party could inspect and verify. Lines like "Project Management" or "Coordination" that don't map to inspectable work are red flags for the architect and will typically be challenged.

Protect cash flow on every project

Modernize AP to cut costs, speed approvals, and reduce payment risk — with the real-time visibility construction finance teams need to scale without adding headcount.

Download the whitepaper

How granular should each line item be?

Each line item should be granular enough that the percentage-complete measure for the scope is defensible by someone walking the job site and inspecting the work. Sitework as a single line item is too coarse on most jobs over a few hundred thousand dollars; sitework broken into demolition, excavation, utilities, paving, and landscaping is more defensible. Breaking concrete into 30 sub-lines (footings, slab on grade, walls, columns), by contrast, is more granular than the architect needs and creates more work for the project accountant every month.

A practical test: imagine the architect walking the site at the 50% mark on a particular line and asking "is this scope 50% complete." If the question has a defensible answer ("yes, all four of the rooftop units are set, ductwork is roughed in for floors 1 and 2 of 4"), the granularity is right. If the question can't be answered cleanly because the line covers too much disparate work, the line needs to be split. If splitting it would create five sub-lines that all complete in the same week, the line was already at the right level.

What is front-loading, and why do architects reject it?

Front-loading is the practice of assigning disproportionately high values to scopes performed early in the project (mobilization, sitework, early procurement) and disproportionately low values to scopes performed late (finishes, punch list, closeout). The contractor's incentive to front-load is straightforward: get more cash earlier in the job, which improves working capital and reduces exposure to disputes at the end. The owner's incentive to prevent front-loading is also straightforward: keep the contractor financially motivated to finish, and avoid being left exposed if the contractor walks off mid-project with cash already collected.

Architects review the schedule of values specifically to catch front-loading. The signs are obvious to an experienced architect: mobilization disproportionate to the project size (typically 2 to 5% is reasonable, more than that draws scrutiny), early structural lines that include scope items typically billed later, GC overhead and fee weighted heavily into the first half of the construction schedule. When front-loading is identified, the architect typically asks the contractor to redistribute value across the schedule before approving it. Pushing back on a reasonable architect challenge is usually a losing argument.

How do change orders get added to the schedule of values?

Change orders are added to the schedule of values as new line items, not merged with existing lines. When an owner-approved change order increases the contract sum by $50K to expand the scope of mechanical work, the change becomes a new SOV line: "CO-1: Expanded MEP scope, $50,000" with its own percentage-complete tracking, retainage column, and billing history. This preserves the audit trail (which scope was original, which was added by change) and lets the architect track change-order work separately during pay-application review.

Combining change-order work into existing SOV lines creates messy reconciliation. If the original mechanical scope was $672K and a $50K change order gets folded into the same line, future percentage-complete claims become ambiguous (does the 60% reflect the original scope or the expanded scope?). Keeping each change order as its own line preserves clarity and survives the audit that happens on closeout. The same principle applies to credit changes, where scope is removed and contract value decreases. The credit shows up as its own SOV line with a negative value.

What changes when the contract is not AIA?

When the contract is not AIA, the pay-application mechanics are the same but the form changes. ConsensusDocs 293 is the most common alternative for prime contracts on commercial work; it uses a similar continuation-sheet structure to the G703 with slightly different formatting and column conventions. Many public-works projects use owner-prepared SOV templates, especially federal and state-funded work, which often include additional columns for Davis-Bacon and certified-payroll cross-references. On smaller jobs and design-build projects, the SOV may be a custom format negotiated between the contractor and the owner.

The mechanics that survive across all formats are the same. The schedule allocates the contract sum across scopes of work; pay applications bill against the schedule line by line; the architect (or owner's representative on contracts without a separate architect) reviews and approves each period's billing; retainage accumulates and releases on a contractual schedule; change orders get added as new lines. What changes is the form, the column structure, sometimes the retainage rules, and the specific approval workflow. Project accountants who work across contract types learn to translate among the formats without much difficulty, but it does take attention the first time a new format shows up on the job.

How does ConsensusDocs 293 differ from the AIA G703?

ConsensusDocs 293 is a continuation-sheet format published by the ConsensusDocs coalition (which includes the Associated General Contractors and other industry groups) as an alternative to the AIA G703. The core columns are functionally similar (scheduled value, work completed, percentage, retainage, balance to bill), but the layout differs and some terminology is different. ConsensusDocs tends to be more contractor-friendly in default language; the AIA forms are owner-architect-prepared and lean slightly more conservative.

On a practical basis, the difference matters most at contract execution (which form is referenced in the contract) and at audit (which form's column conventions to follow when reviewing past applications). Once the contract specifies a form, the monthly mechanics are the same. The ConsensusDocs form is used most commonly on contracts where the GC or contractor's association had influence over the contract drafting; AIA forms remain dominant on owner-driven contracts and design-bid-build projects with traditional architectural oversight.

What do public-works projects require beyond the SOV?

Public-works projects (federal, state, and many local government-funded jobs) add requirements that interact with the schedule of values without replacing it. Davis-Bacon and Related Acts require certified payrolls submitted weekly, with payroll data tied back to SOV line items by labor category and prevailing wage rate. Federally funded projects under DBE/MBE/WBE requirements may require subcontractor participation tracked against SOV line items as well. Bond requirements often add billing prerequisites (payment bond verification, performance bond status) before each pay application can be processed.

The implication for the schedule of values is that line items need to be structured to support the reporting requirements that come with public funding. A schedule of values that maps cleanly to labor categories, work classifications, and trade scopes will produce cleaner certified payrolls and faster pay-application approval on public-works projects. A schedule of values structured purely for billing convenience on a private project may require significant rework when applied to a public-works job. Smart contractors who work in both markets keep separate SOV templates for each.

How does the approved pay application land in your AP and payment system?

Once the architect certifies the G702 and the owner approves it, the approved pay application becomes the basis for downstream AP obligations. The GC owes each subcontractor and supplier their proportional share of the approved billing, less retainage held at the sub level, contingent on lien waivers and any contract-specific payment conditions. The AP cycle that follows is where most cash-flow leakage happens on construction jobs: payment to subs gets delayed waiting for owner funds to clear, lien waivers get chased instead of collected at payment release, and reconciliation between the SOV billing and the actual sub payments slips out of sync.

A clean operating model has the following structure. The certified G702 is logged as the AP receivable from the owner and the AP payable to subs (less retainage, less withholdings). When owner funds clear, payment releases go to subs through the contractor's preferred payment rail (ACH for known subs with verified bank accounts, virtual card for material suppliers in rebate programs, check for the holdouts who still demand it). Conditional progress lien waivers are collected as part of payment release, not before. Each payment is reconciled against the SOV line it funded and the lien waiver that accompanied it, which feeds a three-way match against the original SOV and the approved pay application.

How does the pay app reconcile against the SOV for AP?

The pay application reconciles against the SOV at the line-item level. When the approved G702 says "$633,800 due this period," the underlying G703 says "this line earned $X, that line earned $Y," and the sum reconciles to the cover total. AP picks up that line-level detail and matches it to the sub invoices, supplier invoices, and labor costs that funded the work. The reconciliation is the audit trail that survives closeout and the source of any dispute resolution that comes up later. A pay application that doesn't reconcile cleanly to subordinate billing on a line-by-line basis will eventually produce an audit finding.

The reconciliation is also where the three-way match discipline shows up in construction AP. Each sub or supplier invoice should match a purchase order or subcontract reference, match a delivery or progress verification (often via lien waiver or sworn statement), and match the SOV line it was billed against. When all three match, the payment releases cleanly. When one doesn't match, the payment holds until the discrepancy is resolved. Most construction AP systems run this match against the SOV automatically once the structure is set up correctly.

Payments that keep projects moving

Sync with any construction ERP, replace manual approvals with paperless workflows, and earn rebates on fuel, purchases, and T&E — all on one card with built-in fraud controls.

Explore construction solutions

Why does the lien waiver get paired with payment, not approval?

The lien waiver gets paired with payment because the legal protection it provides is contingent on consideration being received. A conditional progress lien waiver says "I waive my lien rights for work performed through this date, conditioned on receipt of payment of $X." Until the payment actually arrives in the sub's account, the conditional waiver doesn't take effect. Pairing the lien waiver with the payment release (not with the pay-application approval) gives the GC the legal protection only at the moment the consideration changes hands. The conditional vs unconditional lien waiver distinction matters here, and most construction AP teams have it baked into their workflow.

The same logic applies to closeout. Final lien waivers (which release all lien rights, not just rights through a particular pay-application date) are typically collected with final payment of retainage. Collecting unconditional waivers in advance of payment is a common rookie mistake that creates legal exposure for the contractor. Collecting conditional waivers at pay-application approval is fine because they take effect only upon payment, but processing them needs to be coordinated with the actual payment release.

How Corpay supports construction AP teams running an ERP

Corpay sits between the construction ERP and the bank, with AP automation that handles the certified pay application as the inbound trigger and a multi-rail payment stack that releases funds to subs, suppliers, and labor pools on the right timing for each counterparty. The ERP integration depth matters here: Corpay connects to Sage 300 CRE, Foundation, Viewpoint Vista, Acumatica Construction Edition, NetSuite, and Microsoft Dynamics 365 among 180+ ERP connections, which means the project accountant doesn't have to rebuild the schedule of values in a separate payment system to release the approved pay application. The SOV stays where it lives (in the construction ERP), and Corpay picks up the approved billing from there.

The downstream payment side handles what each counterparty actually prefers. Subs with established bank accounts and net-30 terms get ACH on the schedule the GC sets. Material suppliers participating in the buyer-side virtual card rebate program get card payment on net-10, which can return rebate-share to the GC at material volume thresholds. Field-spend cards extend working capital for materials and crew expense without burning the GC's revolver. The field-spend card program ties into the same SOV-driven reconciliation as the rest of the AP cycle, which keeps the project ledger aligned with the actual cash movement at the bank. For finance teams running the back office of a construction company, the Corpay AP & Invoice automation platform is the layer that takes the approved pay application and turns it into reconciled payments without rebuilding the project ledger.

Frequently Asked Questions

What is a schedule of values, in plain terms?

A schedule of values is the line-by-line breakdown of a construction contract's total price, allocated across the discrete scopes of work that will be billed against as the project progresses. It's the document that becomes the billing basis for every pay application, the reconciliation point for retainage and change orders, and the audit trail for the entire project at closeout.

What is the difference between the AIA G702 and G703?

The G702 is the one-page cover pay application showing contract sum, change orders, total completed, retainage, prior payments, and current amount due. The G703 is the multi-page continuation sheet that breaks the total into the SOV line items with scheduled value, percent complete, stored materials, and retainage per line. The G703 supports the G702; together they make up the AIA pay application.

Who prepares the schedule of values?

The general contractor prepares the schedule of values for the prime contract with the owner, and each subcontractor typically prepares their own schedule of values for their subcontract with the GC. The architect reviews and approves the GC's schedule before pay applications can be processed against it.

How granular should the SOV be?

Granular enough that each scope of work has a defensible percentage-complete measure inspectable on the job site, but not so granular that the schedule becomes unwieldy or loses billing flexibility. A typical commercial project runs 30 to 50 line items on the prime SOV. Lines that don't map to inspectable physical work are likely to be challenged by the architect.

Is a schedule of values required on every construction project?

A schedule of values is required on virtually every commercial and public-works project of meaningful size, because the contract documents reference it as the billing basis. Smaller residential projects on lump-sum contracts sometimes operate without a formal SOV, billing instead on milestone payments or on a percentage-of-completion estimated by inspection. On any project with monthly progress billing, an SOV (or its functional equivalent) is needed.

Can the schedule of values be revised after it is approved?

The schedule of values can be revised after approval, but the contract typically requires owner and architect agreement to do so. Reallocations of value between line items (without changing the total contract sum) are sometimes allowed within tolerance limits, especially when actual work scope diverges from initial assumptions. Change orders are added as new lines rather than blended into existing ones. Significant restructuring of the SOV mid-project usually signals a problem that the architect will scrutinize.

How does retainage show up on the schedule of values?

Retainage shows up on the G703 as a dedicated column, typically holding a percentage of each period's earned value cumulatively. On a 5% retainage contract, every billing dollar earned has 5 cents held back until contractually scheduled release (typically at substantial completion and final closeout). The retainage line is one of the most-watched numbers on the G703 because it represents working capital held hostage.

What is SOV in construction billing?

SOV in construction billing is shorthand for "schedule of values," the line-item breakdown of the contract sum that serves as the billing basis for every pay application. The SOV allocates the total contract price across the scopes of work that will be billed and reviewed each month, allowing the architect to certify completion percentages and the owner to approve payment on a defensible basis.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation