Start free
September 10, 202611 min read

Avoid 56-Day Delays: Contractors’ Schedule of Values for G703/G702

Contractor reviewing construction payment documents

A schedule of values (SOV) is the line-item breakdown of a contract sum that turns one lump-sum price into the billable units that support every progress payment. It’s what populates the AIA G703 continuation sheet, which then rolls up into the G702 pay application. If you’re building one from scratch or reviewing one a subcontractor submitted, the steps below cover exactly what belongs on it and how to keep it audit-safe.

TL;DR:

  • A properly structured SOV must match the signed contract sum exactly, including all change orders, and be backed by supporting documentation for stored materials.
  • Using standardized formats like AIA G703 or ConsensusDocs 293 helps ensure clarity and compliance with owner, architect, and government review requirements.
  • Creating an SOV involves selecting a consistent line-item structure aligned with project scope, accurately translating estimates, and avoiding early-phase inflation to prevent front-loading.
  • Regular reconciliation and synchronization with internal cost codes, along with meticulous logging of change orders, keep the SOV audit-safe and reduce billing delays.
  • Automating SOV workflows with AI-native ERP platforms minimizes transcription errors, speeds up updates, and facilitates rapid, error-free billing cycle submissions.
Designflow-build
Automate Your SOV Billing Workflows
DesignFlow Build combines project management, accounting, and field operations to reduce manual work across construction billing workflows.
Explore DesignFlow Build

Table of Contents

What Is a Schedule of Values, and When Is One Required?

An SOV is not your internal job-cost budget. Your budget tracks what a scope actually costs you to build; the SOV tells the owner and architect how you’re allocating the contract price across phases of work so they can certify payment. Confusing the two is one of the fastest ways to create billing friction, since the SOV is an owner-facing document, not an internal cost tool.

The general contractor typically prepares the SOV, then submits it for review by the architect, owner, or construction lender before the first draw. On many private jobs, this happens informally, guided by whatever payment form the contract references. On federal work, it’s not optional: the GSAM requires contractors to assign a value to each major activity, including both direct and indirect costs, with enough detail for the government to evaluate payment requests.

You’ll typically encounter one of a few standard formats:

Granularity should scale with project size. A small tenant buildout might need 15 lines. A multi-million-dollar commercial job usually needs more structure to stay defensible under review.

How to Create a Schedule of Values: A Step-by-Step Workflow

Building an SOV that survives architect and lender scrutiny comes down to sequence. Skip a step, and you’ll be revising it after the first rejected draw.

  1. Confirm the contract format and retainage terms first. Check whether the owner’s contract specifies AIA, ConsensusDocs, or a custom form, and lock in the retainage percentage before you build a single row. Retainage rules affect how you structure totals later, so getting this wrong means redoing the math.
  2. Pick your line-item structure. Most SOVs follow CSI divisions, trade breakdowns, or project milestones. CSI divisions work well for owners and architects who want to cross-reference specs. Trade-based grouping is often faster for subcontractor coordination. Pick one and stay consistent; mixing structures mid-project confuses everyone reviewing the draws.
  3. Translate your estimate into SOV lines. Group your detailed estimate costs into the SOV’s coarser categories, then allocate overhead and profit across the lines rather than isolating them into one suspicious “markup” row. Add every line, and the total must equal the contract sum exactly. Even a rounding error of a few dollars can trigger a resubmission request.
  4. Submit and respond to questions. Send the draft to the architect or owner’s representative, then expect line-item pushback, especially on early-phase costs. Answer with backup documentation rather than adjusting numbers just to move the conversation along.

Pro Tip: Build your SOV in the same tool you use for scheduling and cost coding whenever possible. Reconciling three spreadsheets, an estimate, a schedule, and a billing form, is where most transcription errors happen.

What Belongs on Each SOV Line, Mapped to G703 and G702

Every SOV line needs enough information for someone outside your company to understand what’s being billed and verify it. At minimum, each row should include:

These columns aren’t arbitrary. On AIA contracts, the SOV loads directly onto the G703 continuation sheet, which carries scheduled value, percent complete, stored materials, retainage, and balance to finish for every single line. The G703 subtotals then feed the G702 summary, which is the document the architect actually certifies and the owner pays against.

That net figure flows up into the G702’s total earned less retainage line. Get one row wrong, and the G702 summary is wrong too, which is exactly what triggers a rejected draw.

How SOVs Drive Monthly Progress Billing and Draw Approval

Once your SOV is approved, it becomes the template you update every billing cycle, not a document you file away. Each month, you report percentage complete per line, add any new stored materials with supporting invoices, and recalculate retainage.

The architect or owner’s representative reviews the updated G702 and certifies it before payment releases. That certification is the reconciliation point where inflated percentages or unsupported stored-material claims get caught, and where trust either builds or erodes over the life of a contract.

The financial stakes of getting this wrong are real. Because a poorly built SOV is effectively the billing engine for every draw that follows, errors cascade: a mismatched total on one line can hold up the entire application, and subcontractors caught in that delay wait an average of 56 days for payment once billing errors force a resubmission.

Before you submit, run through this checklist:

Best Practices That Keep an SOV Defensible

The single biggest threat to a clean SOV is front-loading: inflating early line items like mobilization or site prep so you get paid faster than the work justifies. Architects watch for this specifically, so the best defense is granularity that maps realistically to actual sequencing. As a rule of thumb, large commercial projects typically use 30 to 50 SOV lines, enough detail to be inspectable without turning monthly billing into a data-entry marathon.

  1. Size your line count to the contract. A $500,000 renovation doesn’t need 60 lines; a $30 million build usually does.
  2. Justify early-phase pricing. If mobilization or general conditions carry a large share of value, be ready to explain the labor and material commitments behind it.
  3. Add change orders as new numbered lines, like CO-1, CO-2, rather than folding them into existing scopes. This preserves an audit trail and keeps percent-complete tracking accurate for both the original scope and the change.
  4. Sync your SOV with internal cost codes every billing cycle so your accounting team and your PM are reading from the same numbers, not two versions that drift apart over time.

Pro Tip: Keep a change log alongside your SOV showing the date, amount, and owner approval for every CO line you add. If a lender or auditor questions a jump in contract value, you want that answer in seconds, not after digging through email threads.

Mapping an Estimate to an SOV When Change Orders Hit

Converting a detailed estimate into billing-ready SOV lines, and keeping it accurate once change orders start landing, follows a tight five-step loop.

  1. Group estimate line items into the coarser SOV categories you chose during setup, whether that’s CSI divisions or trade packages.
  2. Allocate overhead and profit proportionally across lines instead of stacking it into one row.
  3. Reconcile the total against the signed contract sum. If it doesn’t match exactly, find the discrepancy before submitting.
  4. Validate percentages with subcontractors each period so their billing matches what you’re reporting upstream.
  5. Finalize and lock the baseline before the first pay application, then treat every future change as an addition, not an edit.

When a change order gets approved, append it as its own numbered line, CO-1, CO-2, and so on, rather than editing the original scope’s value. This keeps your audit trail intact and simplifies percent-complete tracking on both the base contract and the CO separately. The most common failure point here is letting your general ledger and your SOV drift out of sync. If a CO gets logged in accounting but never appended to the SOV, your next draw will be short, and someone will have to explain why.

A Sample Schedule of Values Mapped to a G703 Line

Seeing one row carried through the full workflow makes the mapping concrete. Here’s a simplified example for a single trade package:

To use a template like this, drop each row into your AIA-style continuation sheet or your billing platform’s SOV module, then confirm the sum of every scheduled value column equals your total contract sum before the first submission. Keep supplier invoices and delivery tickets attached to any stored-materials line, and log CO documentation separately so it’s traceable when the retainage totals shift.

How AI-Native ERP Platforms Speed Up SOV Workflows

Manually re-keying an estimate into an SOV, then into a G703, then into a G702, is where most transcription errors creep in. DesignFlow Build’s AI-native ERP maps estimate line items into SOV structure automatically, populates G703/G702 forms, appends change order lines with numbering intact, and recalculates retainage as percentages update. It’s one automation path among several, but a useful benchmark for what “good” looks like.

How AI-Native ERP Platforms Speed Up SOV Workflows — overview diagram

A Checklist I Run Before Every First Pay Application

Before any pay application goes out, I check that line totals tie exactly to the signed contract sum, every change order is appended with its own number, and stored-material backup is attached and dated. Then I confirm the subs know what’s being billed on their behalf. One habit worth building into your calendar: a short monthly reconciliation meeting between accounting and the PM, just to catch drift before the architect does.

— Keith

DesignFlow Build: Automating SOV and AIA Billing Workflows

Building and updating an SOV by hand across three or four disconnected tools, an estimate spreadsheet, a scheduling app, and a separate accounting system, is exactly where totals stop matching and draws get delayed. DesignFlow Build maps your estimate directly into SOV structure, auto-populates G703 and G702 forms, appends change orders as clean numbered lines, and recalculates retainage as work progresses, all inside one platform instead of across five.

Designflow-build

Contractors report that using such platforms can lead to reductions in manual data entry and rapid implementation timelines, with high adoption rates among teams who switch over. If your billing team is still reconciling SOVs across spreadsheets and email threads, take a look at the AI construction software built to automate that workflow, or start with the construction software glossary to map your own terms to AIA fields before you migrate.

Sources

For canonical formats, review the AIA G703 continuation sheet, the ConsensusDocs 293 SOV form, and GSAM clause 552.236-15 for federal procurement requirements. For hiring context around SOV responsibilities, see this contractor hiring checklist.