SOV Alignment Between Prime and Subcontracts: A Real-World Walkthrough

The Setup: A $4.2M Office Tenant Improvement

Imagine a mid-size general contractor, let's call them Meridian Construction, wins a $4.2 million office tenant improvement job for a commercial property owner. The prime contract follows the AIA G702/G703 format. The schedule of values on the G703 continuation sheet breaks the work into 18 line items, organized roughly by CSI MasterFormat division: 03 00 00 Concrete, 06 00 00 Rough Carpentry, 09 21 16 Gypsum Board, 09 91 23 Interior Painting, 26 05 00 Electrical, 23 09 00 HVAC Controls, and so on.

Meridian's project manager, Carla, sets up the prime contract SOV in the billing software and immediately turns to sub procurement. Four major subcontracts go out: framing and drywall, electrical, mechanical, and a single specialty sub for access flooring. Contracts are signed. Then the trouble starts - quietly, before the first pay app is even submitted.

Where the Misalignment Happens

The framing sub, DuraBuild, sends back a signed subcontract along with its own proposed SOV. DuraBuild's SOV has 9 line items. The prime contract's SOV has 4 line items that relate to DuraBuild's scope: Demolition, Metal Framing, Gypsum Board, and Acoustical Ceilings. DuraBuild's 9 lines roll up differently. Their item called "Material Procurement and Mobilization" is $48,000. Nothing in the prime contract SOV matches that description. Their "Framing Labor - Phase 1" and "Framing Labor - Phase 2" split $210,000 across two milestones the architect has never heard of.

The electrical sub, Voltex, does the same thing. Their SOV has a $35,000 line for "Temporary Power and Site Electrical" that is buried inside the prime contract's single 26 05 00 Electrical line item worth $680,000. Voltex plans to bill that $35,000 in Month 1. The prime contract does not front-load.

Neither sub did anything wrong intentionally. They submitted the SOVs they always use. But Carla accepted both without reconciling them to the prime.

Month 2: The Pay App Collision

DuraBuild submits its first pay application: $87,400 earned, based on its own 9-line SOV. Carla needs to translate that into the 4 relevant lines on the prime contract G703 continuation sheet. She cannot. The line items do not map. She spends three hours guessing, ultimately moving $48,000 of DuraBuild's "Material Procurement" into the prime's Demolition line because it was the only partially open bucket. The architect flags it during review. The pay app is rejected and kicked back. Meridian misses the billing cycle. That is $87,400 held for 30 additional days.

Voltex's $35,000 "Temporary Power" line creates a different problem. The prime contract owner approved no front-loading. The architect reviews the G703, sees the electrical line billed at 5% when site work is barely started, and calls Meridian's superintendent to ask what electrical work was actually completed. The answer does not satisfy anyone.

Two subs, two billing problems, and the job is only in its second month.

The Fix: SOV Alignment Before the First Shovel

The right process happens before subcontracts are executed, not after the first pay app lands on your desk. Here is how Meridian should have handled it.

Step 1: Build the Prime SOV First, Lock It

Carla should finalize the prime contract SOV and get it approved by the architect before any subcontract is signed. The approved prime SOV becomes the master. Every subcontract SOV must trace back to it. This is not about convenience - it is about protecting Meridian's billing cycle. If the prime SOV changes after subcontracts are signed, Meridian has to reopen each sub's contract. That is expensive. Locking the prime SOV first eliminates the problem.

Step 2: Attach the Prime SOV Line Items to Each Subcontract

When Meridian sends out the subcontract to DuraBuild, it should include an exhibit that lists exactly which prime contract line items DuraBuild's work feeds. Exhibit A, Scope of Work. Exhibit B, SOV Mapping. The exhibit should say: "Your billing will be organized under the following prime contract line items: Line 4 (Demolition, $62,000), Line 7 (Metal Framing, $185,000), Line 9 (Gypsum Board, $148,000), Line 11 (Acoustical Ceilings, $74,000). Your pay application must allocate earned value to these four lines only."

DuraBuild can still track its own internal cost codes. That is between DuraBuild and its own accounting team. But what DuraBuild submits to Meridian must speak the prime contract's language.

Step 3: Approve Sub SOVs Before Work Begins

When DuraBuild submits its proposed SOV, Carla's job is to verify that every DuraBuild line maps to a prime contract line, that the dollar totals roll up correctly, and that no single sub line front-loads a prime line beyond what the architect will accept. This takes 30 minutes with the right side-by-side view. It saves three hours of damage control per billing cycle.

For Voltex's $35,000 temporary power item, Carla should have flagged it immediately. The options: either fold it into the general 26 05 00 Electrical line and bill it proportionally as electrical work progresses, or get the architect's written approval to bill it as a discrete front-loaded item before submitting Month 1. Both options are legitimate. Neither requires guessing.

Step 4: Create a Sub-to-Prime Billing Crosswalk

For a job with four major subs and 18 prime SOV lines, Meridian should maintain a crosswalk spreadsheet - or better yet, a billing platform that handles the mapping automatically. The crosswalk shows every sub's line items in the left column and the corresponding prime contract SOV line in the right column. When DuraBuild's pay app comes in, Carla checks the amounts against the crosswalk and rolls them into the G703 continuation sheet without interpretation. No guessing. No rejected apps.

On a $4.2M job with four subs, a single missed billing cycle at an average draw of $180,000 per month costs Meridian roughly $1,500 in carrying cost at a 10% line of credit. Miss two cycles on two subs and the number climbs fast. Alignment is not a paperwork formality. It is cash flow management.

A Note on Stored Materials

SOV misalignment gets worse when stored materials are in the picture. If the prime contract SOV includes a stored materials column (as the AIA G703 format does), the sub's SOV must also track stored versus installed separately. A sub that lumps "materials on site" into a single completed-work percentage will create a discrepancy the moment the architect asks for proof of storage or a bill of sale. Build the stored materials tracking requirement into the subcontract exhibit from the start.

The Lesson Meridian Took into the Next Job

After the tenant improvement job, Carla built a standard onboarding package for every new sub: the prime SOV excerpt showing that sub's relevant lines, a blank sub SOV template pre-labeled with those prime line items, and a one-page instruction sheet explaining the billing rules. Sub onboarding time dropped. Billing cycle rejections from the architect dropped. And when Month 6 brought a $95,000 change order that reshuffled two SOV lines, Carla already knew exactly which sub's billing was affected and updated their exhibits the same day the G701 change order was executed.

SOV alignment is a front-loaded investment. Thirty minutes at contract execution prevents hours of repair work across every billing cycle for the life of the job.

Keep It All in One Place

Subcontractor pay apps, joint checks, and backcharges belong in one ledger. EZBilling keeps them tied to the prime contract so your billing always tells a consistent story to the architect, the owner, and your bank.