Schedule of Values in Construction: What It Is and Why It Controls Your Cash Flow

A schedule of values (SOV) is the line-item breakdown of a construction contract that assigns a specific dollar amount to every scope of work on the project. It’s the document that drives progress billing, controls draw accuracy, and determines how fast money moves from lender to owner to general contractor to subcontractor. 

When the SOV is structured correctly and kept current with change orders, the GC’s pay application matches the G703 Continuation Sheet, the draw clears without lender questions, and subs get paid on schedule. When it’s not, billing errors cascade through the entire payment chain. Built connects the SOV to lien waiver automation and draw assembly, cutting draw submission time by 75% and reducing billing errors that delay payments across more than 569,000 active projects.

What Is a Schedule of Values in Construction?

A schedule of values is a detailed financial document that breaks the total construction contract price into individual line items, each representing a specific scope of work with a dollar amount assigned to it. The sum of every line item equals the agreed-upon contract price.

The SOV exists to make progress billing work. Without it, there’s no structured way for a GC to show how much work has been completed, how much money is owed this period, and how much remains. Owners use it to verify that payment requests match actual progress. Lenders reference it when reviewing draw requests. Architects use it during field inspections to confirm that billed percentages reflect what’s actually in place.

GCs typically create the SOV after the contract is signed but before the first pay application. Subcontractors provide input for their scopes, and the owner or architect reviews and approves the document before billing begins. On projects using a construction manager at risk (CMAR), the CMAR may coordinate the SOV as part of early-stage cost planning.

The two most common formats are the AIA G703 Continuation Sheet (used alongside the G702 Application and Certificate for Payment) and the ConsensusDocs 293. Both give every party a shared reference for what work costs, what’s been completed, and what’s left. The AIA’s guidance on SOVs lays out why most contracts require one before the first draw.

The schedule of values is the single document that determines whether your draw clears, your subs get paid, and your project stays lien-free.

What Is Included in a Schedule of Values?

A standard SOV contains columns that track every dimension of billing across the life of a project. Each row is a line item representing a scope of work, and each column captures a different aspect of progress and payment.

The typical SOV includes the following:

Most GCs organize line items by CSI MasterFormat division (Division 03 for Concrete, Division 09 for Finishes, Division 23 for HVAC, and so on). This structure keeps the SOV consistent with spec sections, which makes it easier for architects and owners to cross-reference during billing review.

How change orders affect the schedule of values

Approved change orders (COs) should be added as separate line items in the SOV, not folded into existing lines. When a CO gets absorbed into an existing line item, the original scheduled value no longer reflects the original contract, which means the general ledger (GL), the draw request, and the remaining budget all desync.

On a $25M mixed-use development with 14 subs across 10 trades and a 30-day billing cycle, one miskeyed line item on the SOV means the G702 amount doesn’t match the G703 continuation sheet. The lender flags the discrepancy. The GC resubmits. The draw that should have cleared in three days takes two weeks. Fourteen subs wait for payment. Three conditional lien waivers expire and need to be re-executed.

The discipline is straightforward. Every approved CO becomes its own line item with its own scheduled value, and the SOV total updates to reflect the revised contract amount.

How to Create a Schedule of Values

Building an SOV that holds up through billing, change orders, and lender review requires discipline from the start. The following steps detail the process:

1. Start with the contract: Pull the total contract price, and confirm the scope breakdown. Every dollar in the contract needs a home in the SOV.
2. Break the scope into line items: Use either CSI MasterFormat divisions or a trade-based structure. Each line item should represent a distinct, measurable scope of work.
3. Assign scheduled values: Allocate the contract price across line items. The sum must equal the total contract amount exactly. Round-number allocations that don’t reflect actual cost breakdowns invite front-loading scrutiny from owners and lenders.
4. Set retainage by line item: Apply the contractually agreed retainage percentage. Some contracts allow different retainage rates for different scopes or phases. Document any variations.
5. Align with subcontractor scopes: Each sub’s contract should map cleanly to one or more SOV line items. When a sub’s scope splits across multiple line items, confirm the sub understands how to bill against each one.
6. Submit for owner/architect review: The owner or architect must approve the SOV before the first pay application. Flag any line items the reviewer is likely to question, particularly mobilization and general conditions.
7. Establish the change order protocol: Define how COs will appear in the SOV. The best practice is that each CO gets its own numbered line item appended to the bottom of the schedule.

Organizing by CSI division vs. trade

CSI MasterFormat divisions (Divisions 01 through 49) give the SOV a standardized taxonomy that architects and engineers recognize. Trade-based organization groups line items by subcontractor (e.g., “ABC Plumbing” rather than “Division 22”). Both work. Internal consistency matters most.

For GC controllers managing billing across eight active projects, the CSI approach tends to scale better because it creates a repeatable structure across every project regardless of which subs are on the job. Trade-based SOVs can be faster to build but harder to compare across a portfolio.

Setting retainage by line item

Retainage rules vary by state. Some states cap retainage at 5% on public projects. Others allow up to 10%. A few require retainage release at substantial completion regardless of punch list status. Federal projects follow the Miller Act and its retainage provisions.

The SOV should reflect the contractually agreed retainage rate, and the GC needs to confirm that rate complies with the applicable state statute. Getting this wrong creates a legal exposure. It’s a good idea to consult counsel for state-specific retainage compliance before finalizing the SOV on any project where the retainage terms aren’t established in the prime contract.

How the SOV Connects to AIA G702, G703, and the Draw Cycle

The SOV is the starting point for every billing cycle on a construction project. Understanding how it feeds into the G703, the G702, and the draw request is the difference between draws that clear in three days and draws that take two weeks.

Here’s the chain:

The SOV establishes the line items and their scheduled values. Each billing period, the GC updates those line items with work completed this period, materials stored, and the new percentage complete. That update populates the AIA G703 Continuation Sheet, which is the progress billing detail by line item.

The G703 feeds the AIA G702 Application and Certificate for Payment, which is the certified summary. The G702 carries the total amount due this period, cumulative retainage, and the net payment requested. The owner or architect signs the G702 to certify the work.

The signed G702 and G703 go into the draw package, along with lien waivers, compliance documents, inspection reports, and any other items the lender requires. The lender reviews the package. If everything matches, the draw gets funded. If the G702 amount doesn’t match the G703 totals, or if line items don’t reconcile to the approved SOV, the lender kicks it back.

For billing managers assembling draw packages each month, the cascade involves an inaccurate SOV producing the wrong G703 totals, which produces the wrong G702 amount, which triggers lender questions, which triggers a draw resubmission, which adds 7 to 10 days to the funding timeline. Downstream, the sub doesn’t get paid. The conditional lien waiver the sub already signed may expire before the resubmitted draw clears. Now the GC needs a new waiver. Lien risk escalates.

The connection between the SOV and the draw cycle is financial. Every error in the SOV flows directly into the payment chain. A GC who treats the SOV as a one-time setup document instead of a living billing tool will spend the rest of the project fixing draw packages.

(Learn more about accounting for construction draws and how to manage a construction draw schedule across multiple projects.)

Common Schedule of Values Mistakes and How to Avoid Them

SOV errors cost real money and real time. The following mistakes show up on nearly every project that still manages the SOV manually.

Front-loading and how to spot it

Front-loading is when a contractor assigns disproportionately high values to early-phase line items (mobilization, general conditions, site prep) to pull more cash at the start of the project. The financial risk is real. If early phases are over-billed, the remaining scheduled values won’t cover the cost of the remaining work.

Owners and lenders watch for mobilization costs that exceed 3% to 5% of the contract, overhead allocations that don’t match historical benchmarks, and early-trade values that seem high relative to the scope. A GC who front-loads aggressively may clear the first two draws faster, but they’ll face scrutiny on every draw after that and risk a lender requiring a revised SOV mid-project.

Version drift across projects

On a five-project portfolio, the SOV for each project lives somewhere different. One is on the project manager’s desktop. Another is in a shared drive with three versions. A third exists only in an email thread from six weeks ago. The billing manager pulls the wrong version, keys in the wrong scheduled value, and the draw goes out with numbers that don’t match what the lender has on file.

The counter-argument is predictable: “We’ve always done SOVs in Excel and it works fine.” Excel isn’t the problem. Version drift is. Manual draw packages carry a 3% to 5% error rate. On a $25M project, that’s up to $1M in billing errors across the life of the job. Those errors don’t disappear. They surface as lender questions, resubmissions, and delayed payments.

The other counter-argument is “Our accounting software handles this.” Sage, QuickBooks, and Yardi track costs after the fact. They record what happened. They don’t enforce SOV-to-draw alignment in real time. The billing error has already shipped before the accounting system sees it.

What Subcontractors Need to Know About the Schedule of Values

Subs don’t create the SOV, but they live with the consequences of how it’s built. Every sub on a project bills against the SOV line items assigned to their scope. Their pay application amounts must align with the scheduled values in the prime contract.

When the GC’s SOV is inaccurate or outdated, the sub’s billing gets caught in the middle. The wrong scheduled value means the wrong billing amount on the pay app. The owner or lender rejects it. The payment that should have arrived in 30 days takes 45 to 60. The lien waiver exchange stalls because the sub can’t sign an unconditional waiver for an amount they haven’t received.

For subs, the SOV error chain involves an incorrect billing amount on the pay app leading to a rejected pay app, which leads to a payment delay, which means the lien waiver can’t be collected, which means lien risk escalates for everyone on the project.

The counter-argument from GCs considering new tools is familiar: “Subs won’t adopt new software.” In practice, the opposite happens. When subs can sign waivers in under four minutes on their phone with no account required, adoption takes care of itself. Across Built’s network, 95% of subs report the process as “very easy to use.”

Rod Heisler Construction put it directly: “Built has helped our business by keeping our subs in line with everything that we require.” When compliance is built into the payment process instead of bolted on after, subs don’t resist it. They prefer it, because it means they get paid faster.

How Built Connects the SOV to Faster Draws and Payments

The SOV is the foundation of the billing chain. Built connects that foundation to every step that follows, from invoice ingestion through waiver collection, draw assembly, and payment.

When an invoice arrives, Built’s AI reads it, codes it to the right line item, and flags discrepancies before anyone touches it. Invoice-to-payment time drops from 53 days to 26. The draw package that used to take the finance team three days to assemble now takes one. For GCs on the other side of that draw, the payment arrives faster, which means subs get paid faster.

Lien waivers generate automatically when a payable is created, pre-populated with the correct amount, project, and party using a 50-state statutory template library. Compliance is enforced before payment releases, not after. Subs sign on their phone. Conditionals and unconditionals come back within 24 hours instead of two weeks.

The visibility extends down the chain. With xTier, owners and GCs see waiver status all the way to every sub and supplier, which means one missed lower-tier waiver doesn’t blow up a project closeout.

Waltz Construction saw the difference immediately: “Before implementing Built, we were spending one to two hours tracking down compliance documentation.” John Kraemer & Sons reported the impact in even simpler terms: “We are literally saving days every month.”

Project accountants save 20 to 25 hours per week. Sub adoption exceeds 85%. Subs get paid 50% faster.

Built is the front door to your ERP. Approved payables push directly into Sage, QuickBooks, Vista, or CMiC. There’s no double entry, and for GCs already on Procore, Built integrates natively. Procore handles field ops. Built handles construction accounts payable, waivers, and payments. Built + Procore.

Talk to our team to see how Built connects the schedule of values to faster draws and payments.

Schedule of Values FAQs

What is a schedule of values in construction?

A schedule of values is a document that breaks down the total contract amount into individual line items, each assigned a specific dollar value representing a scope of work. The sum of all line items must equal the agreed-upon contract price. GCs and subcontractors use the SOV to submit progress billing, and owners and lenders use it to verify that payments align with completed work.

Who prepares the schedule of values?

The general contractor typically prepares the SOV after the contract is signed but before the first pay application. Subcontractors provide input for their specific scopes, and the owner or architect reviews and approves the SOV before billing begins. On projects using a construction manager at risk (CMAR), the CMAR may coordinate the SOV as part of early-stage cost planning.

What is included in a schedule of values?

A standard SOV includes item numbers, descriptions of work, scheduled values per line item, work completed to date, work completed this period, materials stored on site, total completed and stored, percentage of completion, balance to finish, and retainage withheld. Change orders are added as separate line items as they’re approved.

How does the schedule of values connect to the AIA G702 and G703?

The SOV is the source data that populates the AIA G703 Continuation Sheet, which tracks progress billing by line item. The G703 then feeds the AIA G702 Application and Certificate for Payment, which is the formal payment request submitted to the owner. Errors in the SOV cascade directly into both documents, triggering lender questions and draw resubmissions.

What is front-loading on a schedule of values?

Front-loading is when a contractor assigns disproportionately high values to early-phase line items to generate more cash flow at the start of the project. Owners and lenders watch for inflated mobilization costs, overhead allocations, or early-trade values that don’t match the actual cost of the work. Front-loading creates financial risk later in the project when remaining values don’t cover the remaining work.

What happens when the schedule of values has errors?

SOV errors cascade through the billing chain. An inaccurate line item leads to the wrong billing amount on the G702, which triggers lender questions, a draw resubmission, and a payment delay of 7 to 10 days or more. Downstream, the sub doesn’t get paid, the lien waiver can’t be collected, and lien risk escalates. Manual SOV management carries a 3% to 5% error rate on typical commercial projects.

Do subcontractors use the schedule of values?

Subcontractors bill against the SOV line items assigned to their scope. Their pay application amounts must align with the scheduled values in the prime contract SOV. When the GC’s SOV is inaccurate or outdated, the sub’s billing gets rejected, their payment is delayed, and the lien waiver exchange stalls. Subs who use platforms like Built can submit invoices and sign waivers in under four minutes without a separate login.