Getting schedule of values best practices right is the difference between a project that runs on budget and one that bleeds cash through overbilling. A 2025 Construction Financial Management Association survey found that 38% of GCs identified poorly structured schedules of values as the top cause of pay application disputes.

This guide gives you practical strategies for building, reviewing, and enforcing a schedule of values that protects your project finances from day one.

Why Your Schedule of Values Needs a Better Structure

Most GCs accept the subcontractor's first draft of the schedule of values without meaningful pushback. That is a mistake.

A well-structured SOV breaks the contract into line items that match your cost codes, your payment milestones, and your ability to verify completed work in the field. When line items are too broad, subcontractors can claim percentages that do not reflect actual progress.

Front-Loading Is the Biggest Threat

Front-loading happens when a subcontractor assigns disproportionate value to early-stage work. An electrical sub might load 40% of the contract value into rough-in when the actual cost of rough-in materials and labor represents only 25%.

The result is that you overpay early in the project. If that sub defaults or gets terminated, you have paid more than the value of work in place.

Require subs to provide material cost breakdowns and labor hour estimates for each line item. Compare those numbers against your estimating database or RSMeans data. Flag any line item where the assigned value exceeds your estimate by more than 15%.

Match Line Items to Verifiable Milestones

Every line item on the schedule of values should correspond to work you can physically inspect or document. Avoid vague categories like "general conditions" without sub-line-items.

Break general conditions into monthly amounts. Break mobilization into specific deliverables such as trailer setup, temporary utilities, and safety equipment installation. Each sub-item should be something your field team can confirm with a photo or a site walk.

Schedule of Values Review Checklist

Use this comparison framework when reviewing subcontractor SOV submissions.

Review Item	What to Check	Red Flag
Line item count	Minimum 15-20 for contracts over $100K	Fewer than 10 items suggests hidden costs
Front-loading ratio	Early phase items should not exceed 30% of total	Over 35% in first three phases
Mobilization line	Should not exceed 5% of contract	Over 8% signals padding
Material vs. labor split	Should reflect actual cost ratios	80%+ in one category
Retainage alignment	All items subject to same retainage rate	Excluded line items
Cost code mapping	Each item maps to your cost code structure	Unmapped items
Change order protocol	SOV includes process for adding line items	No change order provision

Set Clear Submission Requirements Up Front

Include your SOV requirements in the subcontract before execution. Specify the minimum number of line items, the format, the cost code structure, and the deadline for submission.

Require the SOV within 10 days of contract execution and before the first pay application. If a sub submits a pay app without an approved SOV, reject it. Consistency here prevents arguments later.

Use Percentage Complete with Stored Materials Separately

Combining percentage of work complete with stored materials in a single column creates confusion. Separate them.

Your SOV template should have distinct columns for work in place, stored materials on site, and stored materials off site. This separation makes it easier to verify each component and prevents subs from inflating progress by including uninstalled materials.

Review the SOV Monthly Against Pay Applications

The SOV is not a one-time document. Review it against every pay application.

Compare the percentage complete claimed on the pay app against the previous month. An item jumping from 20% to 80% in a single billing period deserves field verification. Track cumulative overbilling patterns across months. A sub who consistently claims 5-10% more than verified work is a candidate for a billing audit.

Digital Tools Beat Paper Processes

Manual SOV tracking using spreadsheets leads to version control problems and calculation errors. A 2024 Dodge Data report found that GCs using digital pay application tools reduced SOV-related disputes by 52% compared to spreadsheet-based processes.

Digital platforms link the SOV to the pay application automatically. When a sub updates their percentage complete, the system recalculates amounts, applies retainage, and flags anomalies. This removes human error from the billing cycle.

Train Your Project Managers on SOV Review

Many project managers approve pay applications without meaningfully reviewing the underlying SOV. Invest two hours in training your PMs on what to look for.

Cover front-loading detection, stored materials verification, and retainage calculation. A PM who understands the SOV catches overbilling before it becomes a dispute. A PM who rubber-stamps pay apps creates financial exposure you only discover at closeout.

FAQs

How many line items should a schedule of values include? For contracts over $100,000, expect a minimum of 15-20 line items. Larger contracts may need 50 or more. The goal is enough granularity to verify progress without creating administrative overhead. Each line item should represent work you can physically confirm in the field.

What percentage of the contract should mobilization represent? Mobilization should typically be 3-5% of the total contract value. Anything over 8% is a red flag for front-loading. Require the sub to break mobilization into specific deliverables such as equipment delivery, temporary facilities, and safety setup.

How often should GCs review the schedule of values? Review the SOV with every monthly pay application at minimum. Also review it after any change order that adds or modifies scope. The SOV is a living document that should reflect the current contract value at all times.

Can a GC reject a subcontractor's schedule of values? Yes. The GC has the right to reject an SOV that does not meet contract requirements. Include specific SOV format requirements in your subcontract. Common rejection reasons include insufficient line items, front-loaded values, and missing cost code alignment.

What happens if the SOV total does not match the contract amount? The SOV total must match the contract amount exactly, including all approved change orders. If the totals do not match, reject the SOV and require resubmission. Mismatched totals indicate calculation errors or unauthorized scope additions.

Should retainage be shown on the schedule of values? Yes. The SOV should include a retainage column showing the amount withheld on each line item. This ensures both parties agree on the retainage calculation method and amount. Some contracts apply different retainage rates to different line items, which makes this column essential.

Strengthen Your Pay Application Reviews

SubcontractorAudit automates SOV tracking and flags overbilling patterns across every pay application cycle. See how pay app auditing works and take the guesswork out of subcontractor billing.