Schedule of Values Best Practices: Lump-Sum vs Unit-Price Contracts

Why Your Schedule of Values Structure Matters More Than You Think

The Schedule of Values is the foundation of every pay application you submit. Get it right at the start, and billing stays clean through substantial completion. Get it wrong, and you spend the rest of the job arguing with the architect's representative over percentages, fighting for retainage release, and scrambling to reconcile numbers that never quite tie.

The problem is that most contractors build their Schedule of Values the same way regardless of contract type. Lump-sum contracts and unit-price contracts have fundamentally different billing mechanics. They require different structures, different line-item logic, and different documentation habits. Treating them the same is one of the most common and costly mistakes in progress billing.

Lump-Sum Contracts: Breaking Down a Fixed Price Correctly

A lump-sum contract pays you a fixed total for a defined scope. Your Schedule of Values on the AIA G703-style continuation sheet must break that total into line items that collectively sum to the contract amount. Every dollar has to live somewhere on that sheet.

Front-Loading: Where the Line Is

Front-loading means assigning heavier values to early-completing line items so you collect more cash in the first few pay periods. Owners and architects know contractors do this. There is nothing inherently dishonest about it, but there is a line.

Reasonable front-loading: assigning the full installed value of Division 03 concrete work to an early line item because your concrete sub genuinely completes that scope by month two. Unreasonable front-loading: listing "General Conditions" at $400,000 when your actual monthly GC cost is $18,000, simply to inflate early draws. Most owners' representatives will reject a Schedule of Values that assigns more than roughly 10-15% of the contract to general conditions unless your actual costs support it.

A good rule: build your Schedule of Values from your job cost budget. If a line item value can't be traced back to a real cost code or subcontract amount, it will not survive scrutiny during the pay application review.

CSI MasterFormat as Your Framework

For lump-sum commercial work, organize your G703 line items around CSI MasterFormat divisions. Division 01 for general requirements, Division 03 for concrete, Division 05 for metals, Division 09 for finishes, and so on. This aligns with how the design team thinks about the work and makes it easier to tie your billing to the drawings during pay app reviews.

You do not need a separate line for every CSI section. Consolidate within divisions where the scope is minor. A $4,200 Division 10 specialties line does not need to be split into four sub-lines. But Division 22 plumbing rough-in and Division 22 plumbing fixtures should almost always be separate lines because they complete at very different points in the schedule.

Stored Materials on a Lump-Sum Job

Stored materials billing on lump-sum contracts is a separate subject with its own documentation requirements. The short version: stored materials need to be tracked in Column F of the G703-style sheet, not blended into the percent-complete column. Keep your stored materials line items clearly separated from installed work percentages. This keeps your pay app clean and avoids the rejections that come from mixing the two.

Retainage Considerations

Many lump-sum contracts allow retainage to be reduced once a project reaches 50% completion. Your Schedule of Values structure directly affects whether you can claim that reduction. If your line items are too broadly grouped, the architect may argue the project is not demonstrably 50% complete even when the work clearly is. Granular, well-documented line items let you prove completion percentages division by division.

For example, on a $3.2 million contract: if you have a single line item called "Interior Construction" at $1,100,000, proving 50% completion on that line requires judgment. If you split it into "Metal Stud Framing" at $280,000, "Drywall and Taping" at $390,000, and "Acoustical Ceilings" at $430,000, you can document each independently with photos and subcontractor certifications.

Unit-Price Contracts: Entirely Different Rules

A unit-price contract pays you a fixed rate per unit of work installed. The total contract value is not fixed at signing. It adjusts as quantities are measured and verified in the field. This changes everything about how you structure and submit your Schedule of Values.

Your Schedule of Values Is a Quantity Tracker

On a unit-price job, the G703-style continuation sheet functions more like a quantity report than a percentage-complete sheet. Each line item represents a bid item with a unit price and an estimated quantity. Your scheduled value for each line is the unit price multiplied by the estimated quantity. That number is your baseline, not a hard cap.

For example: "4-inch concrete flatwork" at $8.50 per square foot, estimated 22,000 square feet. Scheduled value: $187,000. If field quantities come in at 24,100 square feet, your earned amount on that line exceeds the original scheduled value. The pay app has to reflect that, and the architect needs to approve the quantity adjustment. Build your G703 template to accommodate this from day one.

Separate Line Items for Each Bid Item

Every bid item with a distinct unit price gets its own line on the Schedule of Values. Do not combine bid items even when they fall under the same CSI division. "6-inch water main" and "8-inch water main" have different unit prices, different installation rates, and potentially different inspection requirements. Grouping them creates reconciliation headaches when quantities change at closeout.

This is especially important on civil and site utility work, where Division 31 earthwork, Division 32 paving, and Division 33 utilities each carry multiple bid items with different units: cubic yards, linear feet, each, square yards. A well-structured Schedule of Values lists them all separately.

Quantity Verification and Field Tickets

The biggest billing dispute on unit-price jobs is quantity measurement. Unlike lump-sum work where percent complete is a judgment call, unit-price billing is tied to measured quantities. That means your pay application is only as strong as your field documentation.

Set up a field ticket system before the first pay period closes. Each ticket should record the date, bid item reference, location or station, quantity installed, and the inspector's or owner's representative's signature. Attach those tickets or a certified quantity summary to your pay application. Architects and owners' reps are far more likely to approve payment quickly when the quantities are already verified in writing rather than disputed after submission.

Handling Overruns and Underruns

Unit-price contracts typically include a clause that allows the owner to adjust quantities by 10-25% without a formal change order. Quantities that move beyond that range trigger a change order, which then adds a line to your G703 under the change order section. Track this threshold actively. Many GCs miss the trigger point and end up doing extra work at the original unit price when they were entitled to a renegotiated rate.

When quantities come in below estimate, the scheduled value on that line shrinks. Your G703 needs to show the revised total. Do not leave the original estimated scheduled value in place and show 100% complete on a quantity you did not actually install. That is how billing disputes and lien problems start.

What Both Contract Types Have in Common

Despite their differences, lump-sum and unit-price contracts share a few non-negotiable billing disciplines.

Setting Up the G703 for Each Contract Type

The AIA G702 cover sheet and the G703-style continuation sheet work together as a pay application package regardless of contract type. The G702 carries the summary totals: original contract sum, net change by change orders, contract sum to date, total completed and stored to date, retainage, and amount due this application. The G703 feeds those totals line by line.

For lump-sum jobs, set up your G703 with CSI-organized line items, fixed scheduled values, and percentage columns. For unit-price jobs, add a unit column and a quantity column to your tracking. Some owners' contracts will provide their own Schedule of Values form that modifies the standard G703 layout. Read the contract before you build your template.

One practical tip for both types: number your line items and keep those numbers consistent from pay period to pay period. Architects reviewing pay application number eight do not want to hunt for the line that was item 14 last month but has now been renumbered to 11. Consistency speeds approval.

Final Thoughts

A well-built Schedule of Values protects your cash flow, simplifies retainage negotiations, and makes the closeout process far less painful. The structure you set up before you submit pay application number one determines how smoothly billing runs for the entire job. Match the structure to the contract type, document your quantities, and get the Schedule of Values approved before you bill a dollar.

Managing G702/G703-format pay applications manually gets tedious fast. EZBilling handles progress billing, retainage, and change orders in one place so you can focus on running the job.