Every dollar that flows through a construction project passes through a schedule of values first. Yet most general contractors treat this document as a formality -- something to file away and forget.

That mistake costs real money. GCs who fail to scrutinize subcontractor SOVs before the first pay application face an average overpayment exposure of $40,000 to $120,000 on a $5 million sub contract.

This guide covers everything a general contractor needs to know about building, reviewing, and managing subcontractor schedules of values from project kickoff through final payment.

What Is a Schedule of Values?

A schedule of values (SOV) is a detailed breakdown of a contract amount into individual line items. Each line item represents a specific portion of the work with an assigned dollar value.

Think of it as the financial skeleton of the project. Every pay application, every progress billing, every retainage calculation -- they all reference the SOV. The AIA G703 Continuation Sheet, the most common pay application format in construction, is essentially an extension of the SOV with columns for completed work and stored materials.

The SOV translates a lump sum contract into measurable, billable pieces.

Why the SOV Is the Foundation of Every Pay Application

When a subcontractor submits a monthly pay application, they are reporting progress against their SOV. If the SOV has 60 line items, the sub fills in a completion percentage for each one. The math cascades from there:

Line item value multiplied by completion percentage equals work completed to date
Previous payments subtracted from completed work equals current payment due
Retainage withheld per contract terms reduces the actual check amount

A poorly structured SOV makes every one of these calculations suspect. Lump sum line items hide actual progress. Vague descriptions make field verification impossible. Front-loaded values create cash flow risk from day one.

How GCs Should Require Structured SOVs From Subs

The best time to set SOV expectations is before the subcontract is signed. Include SOV formatting requirements in your subcontract terms.

Specify minimum requirements:

Line items must align with CSI MasterFormat divisions applicable to the scope
No single line item should exceed 5% of the total contract value without approval
Labor and material must be split on line items exceeding $50,000
Mobilization cannot exceed 3% of contract value
Bonds and insurance must be separate line items, not embedded in unit costs

Set a submission timeline. Require the SOV within 10 business days of contract execution, before the first pay application period begins. Review and approve (or reject) within 5 business days of receipt.

Mandate supporting documentation. For contracts over $500,000, require the sub to provide backup for how they arrived at each line item value. This could be a simplified bid breakdown or vendor quotes.

Recommended Line Item Granularity

The right number of line items depends on contract size and scope complexity.

Contract Value	Recommended Line Items	Avg. Line Item Value
Under $100,000	10-20	$5,000-$10,000
$100,000 - $500,000	20-40	$5,000-$25,000
$500,000 - $1,000,000	40-60	$10,000-$25,000
$1,000,000 - $5,000,000	50-100	$20,000-$50,000
Over $5,000,000	80-150	$35,000-$65,000

These are guidelines, not rules. An electrical sub on a $2 million contract might need 80 line items to cover panels, branch wiring, low voltage, fire alarm, and fixtures across multiple floors. A concrete sub at the same value might only need 40.

The goal is for each line item to represent work that can be visually verified in the field within a single pay period.

Front-Loading Prevention Through Proper SOV Setup

Front-loading happens when a subcontractor inflates the value of early-phase line items and deflates later ones. The sub collects more money early in the project than the work warrants.

A mechanical sub might assign 15% of the contract to "rough-in piping" when it actually represents 8% of the total effort. By the time the GC notices, three pay applications have already been approved.

How to catch front-loading at the SOV stage:

Compare line item values against historical cost data from similar projects
Cross-reference the sub's SOV against their original bid breakdown
Flag any line item where the SOV value exceeds the bid value by more than 10%
Check that mobilization, general conditions, and early-phase items don't collectively exceed 15% of the contract
Verify that the cumulative value curve follows a reasonable S-curve pattern

Projects that catch front-loading at the SOV stage save an average of 3-5% in overpayment exposure across the life of the sub contract.

Labor and Material Splits

Splitting line items into labor and material components adds transparency and improves change order management later.

When labor/material splits matter most:

Prevailing wage projects where labor rates are auditable
Tax jurisdictions where materials are taxed differently than labor
Projects with owner-furnished equipment or materials
Contracts with different retainage rates for labor and materials

A typical split for mechanical work might be 55% labor / 45% material. Electrical often runs 50/50. Drywall and painting lean heavier on labor at 65/35.

When the SOV includes these splits, change orders become easier to negotiate because you have a baseline cost structure to compare against.

How the SOV Ties to the G703 Continuation Sheet

The AIA G703 Continuation Sheet is the industry standard format for tracking work completed against the SOV. Each row of the G703 corresponds to a line item from the SOV.

The G703 adds these columns to each SOV line item:

Column A: Item number
Column B: Description of work (from the SOV)
Column C: Scheduled value (from the SOV)
Column D: Work completed from previous applications
Column E: Work completed this period
Column F: Materials presently stored
Column G: Total completed and stored to date (D + E + F)
Column H: Percentage complete (G / C)
Column I: Balance to finish (C - G)
Column J: Retainage

When the SOV is well-structured, the G703 becomes a reliable progress tracking tool. When it is not, the G703 becomes a vehicle for billing errors and disputes.

Common SOV Formats

Different project types and owners use different SOV structures.

AIA-based SOV. The most common in commercial construction. Follows CSI divisions and integrates directly with G702/G703 pay application forms.

Owner-specific templates. Government agencies, universities, and large private owners often have their own SOV templates. Federal projects follow FAR requirements that dictate specific cost categories.

CSI MasterFormat-aligned. Organizes line items by the 50-division MasterFormat structure. Division 26 Electrical, Division 23 HVAC, and so on. This creates consistency across trades and simplifies cost reporting.

Phase-based SOV. Breaks the contract into project phases (foundations, structure, envelope, interiors) rather than trade divisions. Common on design-build projects where scope crosses traditional trade boundaries.

Hybrid formats. Many GCs use a combination -- CSI divisions as the primary structure with phase sub-categories beneath each division. This provides both trade-level and schedule-level visibility.

Building Your SOV Review Process

A repeatable SOV review process prevents the most common billing problems before they start.

Step 1: Receipt and completeness check. Verify the SOV covers 100% of the contract value. Confirm all required line items are present (mobilization, bonds, insurance, general conditions).

Step 2: Granularity review. Check that no single line item exceeds your maximum threshold. Verify that line items are specific enough for field verification.

Step 3: Front-loading analysis. Compare early-phase line item values against historical benchmarks. Flag any items that appear inflated.

Step 4: Cross-reference to bid. If you have the sub's bid breakdown, compare it against the SOV. Significant variances indicate potential front-loading or scope gaps.

Step 5: Labor/material split review. On projects requiring splits, verify the ratios are reasonable for the trade.

Step 6: Approval or revision request. Approve the SOV in writing or send specific revision requests with a deadline for resubmission.

FAQs

What happens if a subcontractor refuses to provide a detailed SOV? Address it contractually. Your subcontract should require SOV submission as a condition precedent to the first pay application. If the sub resists after contract execution, withhold the first payment until a compliant SOV is received. Most subs cooperate when payment is on the line.

Can the SOV be changed after it is approved? Yes, through change orders. When a change order is executed, new line items should be added to the SOV (or existing ones modified) to reflect the changed scope and value. Never let a sub bill changed work against existing line items without a formal SOV revision.

How detailed should stored materials be tracked on the SOV? Materials stored on-site or at an approved off-site location should be tracked against the specific line items they support. Require the sub to identify which SOV line items the stored materials apply to, with quantities and unit costs.

What is the difference between a schedule of values and a cost breakdown? They serve different purposes. A cost breakdown is a budgeting tool that shows how a contractor estimated the job. A schedule of values is a billing tool that determines how progress payments are calculated. The SOV should be informed by the cost breakdown but will not always match it exactly.

How does retainage work with the SOV? Retainage is calculated on each line item's completed work. At 10% retainage, a line item showing $100,000 of completed work has $10,000 withheld. Some contracts reduce retainage at 50% completion. The SOV must be structured so that retainage calculations are clear and auditable at the line item level.

Should the SOV match the project schedule? Not line-for-line, but there should be a logical relationship. Each SOV line item should correspond to activities in the project schedule so that earned value analysis is possible. This connection helps GCs verify that billing aligns with actual progress.

Stop reviewing pay applications blind. SubcontractorAudit's pay app audit tool catches front-loading, flags SOV anomalies, and gives you line-item-level visibility across every sub on every project. See how it works.