Are You Making These Schedule of Values Mistakes?
Last Updated: October 25, 2026
Quick Summary
The five common schedule of values mistakes subcontractors make are lumping costs instead of breaking down line items, front-loading values that don't match the work, ignoring change orders until billing time, skipping stored materials and retainage detail, and letting the schedule of values and progress billing drift apart. Each mistake stalls pay applications and invites GC scrutiny.
- Break work into line items a GC can verify on a site walk, not one lump sum.
- Front-loading puts your entire billing history under scrutiny for the rest of the job.
- Add every approved change order as a new SOV line the day it is signed.
- Bill to two decimal places and use the same rounding rule everywhere.
- Run the eight-item SOV checklist before every submission to avoid rejections.
Table of Contents
- Why Schedule of Values Mistakes Stall Your Pay Applications
- Mistake 1: Lumping Costs Instead of Breaking Down Line Items
- Mistake 2: Front-Loading Values That Don't Match the Work
- Mistake 3: Ignoring Change Orders Until Billing Time
- Mistake 4: Skipping Stored Materials and Retainage Detail
- Mistake 5: Letting Your Schedule of Values and Progress Billing Drift Apart
- What a Clean Construction Schedule of Values Example Looks Like
- Building a Schedule of Values Template That Survives Review
- Frequently Asked Questions
Why Schedule of Values Mistakes Stall Your Pay Applications
A schedule of values is the line-by-line breakdown of your contract that every pay application is built on. Get it wrong, and your billing stalls before it starts.
Here's the thing most guides miss. Your SOV isn't a one-time form you submit at project start. It's a living billing document. Every change order, every stored material delivery, every retainage adjustment flows through it.
Below, we'll walk through the five most common schedule of values mistakes subcontractors make, why each one costs you money, and how to fix it before your next pay app goes out. We'll also show you what a clean construction schedule of values example actually looks like.
The good news: none of these mistakes requires a finance degree to fix. Most come down to structure and discipline.
Mistake 1: Lumping Costs Instead of Breaking Down Line Items
The biggest mistake is treating your SOV like a summary instead of a schedule. A single line that says "Electrical - $180,000" gives the GC nothing to measure progress against. It also gives them a reason to hold your payment.
Break your work into line items that match how the job actually progresses:
- Rough-in by floor or zone
- Fixtures and devices
- Panel and gear installation
- Testing and commissioning
- Temporary power
Each line should map to a phase of work a GC can physically verify on a site walk. When a line item is too broad, the reviewer can't confirm the percentage you're claiming, so they approve less than you billed.
If your line items are already lumped together, you can add, edit and balance the lines you bill against without rebuilding the whole document from scratch.
Mistake 2: Front-Loading Values That Don't Match the Work
Front-loading means assigning more value to early line items than the work is actually worth. It's tempting. It improves cash flow at project start. It also gets flagged fast.
A GC's project manager walks the site. They see the rough-in is 40% done, but your SOV shows 70% of that line billed.
The fix is honest distribution. Weight each line to reflect real labor, material, and equipment value across the schedule. Your early months will look leaner.
What most contractors miss: front-loading doesn't just risk rejection on one application. It puts your entire billing history under scrutiny for the rest of the job.
Mistake 3: Ignoring Change Orders Until Billing Time
Change orders are where billing accuracy falls apart. A signed CO sits in a folder, the work gets done, and nobody updates the SOV until the month it needs to be billed.
Treat every approved change order as a new line item the day it's signed. Add it to the SOV with a clear description and a sequential number that matches your CO log.
You can add approved change orders and bill them directly against your SOV so nothing gets missed between approval and application.
Watch out: unbilled change orders are one of the fastest ways to lose money on a job.
Mistake 4: Skipping Stored Materials and Retainage Detail
Stored materials and retainage are the two most overlooked lines on any SOV. Contractors leave them off because they're complicated, then wonder why their cash flow feels tight mid-project.
Stored materials are materials you've paid for and had delivered to the site but haven't installed yet. If you're billing for materials delivered but not installed, stored materials tracking keeps the paperwork clean and the amounts defensible.
Retainage works the other way. It's the percentage the GC holds back until substantial completion. Understanding how retainage is calculated and how to bill it back keeps your SOV detail accurate month after month.
Get these two right and your pay apps stop getting partial approvals.
Mistake 5: Letting Your Schedule of Values and Progress Billing Drift Apart
Your schedule of values and progress billing must stay locked together. When they drift, the pay app tells a story that doesn't match the SOV, and the reviewer notices.
Here are the three most common drift mechanisms, and how to stop each one:
1. The spreadsheet split. You maintain the SOV in one Excel file and the pay app in another. A line item gets adjusted on the pay app but not the SOV. A percentage gets rounded differently in two places. After three months, the two documents disagree on basic totals. The fix: use a single source of truth. Your SOV should drive the pay app, not the other way around. Every percentage you bill should pull from the same line item the GC approved. If you're still running two files, you're guaranteeing drift.
2. The change order lag. A change order gets billed on the pay app but never added to the SOV.
3. The rounding creep. A line item is 33.333% complete, but you bill 33% on the pay app and 34% on the SOV. Small differences compound.
What most contractors miss: drift isn't just a billing problem, it's a documentation problem.
The practical fix is a review step before submission. Before you send the pay app, open the SOV and the application side by side.
If you're using construction billing software for subcontractors, this synchronization happens automatically, the pay app pulls from the SOV, so drift can't happen. If you're still manual, build the review step into your monthly close.
What a Clean Construction Schedule of Values Example Looks Like
A clean SOV has one line per billable scope, sequential numbering, and a running total that reconciles to your contract value. Here's a simplified example for a $180,000 electrical subcontract:
| Line | Description | Scheduled Value | Billed to Date | % Complete |
|---|---|---|---|---|
| 1 | Temporary power | $8,000 | $8,000 | 100% |
| 2 | Rough-in - Level 1 | $42,000 | $31,500 | 75% |
| 3 | Rough-in - Level 2 | $38,000 | $19,000 | 50% |
| 4 | Panel and gear | $35,000 | $0 | 0% |
| 5 | Fixtures and devices | $40,000 | $0 | 0% |
| 6 | Testing and commissioning | $12,000 | $0 | 0% |
| 7 | Change order CO-001 | $5,000 | $2,500 | 50% |
| Total | $180,000 | $61,000 | 34% |
Notice what makes this clean. Every line is specific enough to verify on a site walk. The change order has its own numbered line. The percentages match the physical progress. And the total reconciles to the contract.
For a line-by-line walkthrough of how this SOV maps onto the application itself, see our guide on how to fill out a G702 and G703 pay application.
Building a Schedule of Values Template That Survives Review
A schedule of values template that survives review is built around three things: consistent line-item structure, a change order log tied to the SOV, and a retainage and stored materials section that never gets skipped. But the template alone isn't enough, you also need to understand how the GC reviews and approves it, because that's where most rejections happen.
Here's the review workflow most GCs follow, and what it means for your template:
Step 1: Initial submission. You submit the SOV with your first pay application. The GC's project manager checks that the line items match the subcontract scope and that the total reconciles to the contract value. If a line item is too broad (e.g., "Electrical - $180,000"), they'll reject it and ask for a breakdown. Your template should force specificity: one line per billable scope, with a description that a site walk can verify.
Step 2: Line-item review. The PM walks the site and compares your billed percentages to physical progress. If a line is front-loaded, they'll flag it.
Step 3: Change order reconciliation. The GC checks that every approved change order has a corresponding line on the SOV.
Step 4: Retainage and stored materials. The GC verifies that retainage is calculated correctly and that stored materials are documented with delivery receipts.
Step 5: Approval and payment. Once the SOV is approved, the GC uses it to process the pay app.
Here's the practical checklist we'd use to audit any SOV before submission:
- Every line item is specific enough to verify on a site walk
- Line numbering is sequential and matches your billing history
- Every approved change order has its own line and a matching CO number
- Stored materials are itemized with delivery documentation attached
- Retainage is calculated and shown on the current application
- Billed-to-date percentages match physical progress
- The SOV total reconciles to the contract value plus approved COs
- The pay app pulls directly from the SOV, not a separate spreadsheet
Run this checklist before every submission.
This is also where construction billing software for subcontractors earns its place. PayAppHub reads your subcontract and carries forward prior work, stored materials, and retainage automatically, so the SOV and the pay app stay in sync without manual retyping. It combines the pay application, lien waiver, and photos into a single PDF, then drafts the billing email in your own email app so you can send it to the GC.
If you're still running the SOV in Excel, the switch is less painful than it looks. You can start with a free trial before committing.
Frequently Asked Questions
How detailed should a subcontractor's schedule of values be?
Detailed enough that each line ties to a measurable piece of work the GC can verify on site. Break major trades into phases, separate materials from labor where the contract allows, and keep line items consistent month to month. Too few lines invites front-loading suspicion; too many makes progress tracking a chore. A good rule is one line per work activity you would actually schedule and bill separately.
How do change orders affect a schedule of values?
Every approved change order should add its own line to the schedule of values, with the approved value and a reference to the change order number. If you wait until billing time to fold changes in, your progress billing will not match the contract sum and the GC will reject or hold the pay app. Update the schedule of values as soon as the change order is signed, not at month end.
How does the schedule of values affect progress payments?
The schedule of values is the backbone of progress billing. Each month you bill a percentage of completion against each line, and the GC approves or adjusts those percentages before releasing payment. Errors in the schedule of values, such as unbalanced lines or missing change orders, lead to disputed percentages, slower approvals, and delayed cash flow. An accurate schedule of values is the fastest route to a clean pay app.
Can construction billing software for subcontractors fix a bad schedule of values?
Software will not fix bad line-item structure, but it removes the mechanical errors that cause most rejections. Tools like PayAppHub read your subcontract, carry forward prior work and retainage, and keep the schedule of values, lien waiver, and pay application in one PDF. That means fewer retyping mistakes, consistent sequential numbering, and a billing package the GC can approve.
Billing mistakes cost you time and cash flow, and most of them start with the SOV. PayAppHub automates AIA-style pay applications, reads your subcontracts, and carries forward stored materials and retainage so your paperwork stays accurate and ready for the GC. Get started with PayAppHub and turn a multi-hour billing day into a few minutes of review.
