Line item management software controls how GCs structure, track, and verify the schedule of values across every subcontract. The questions below come up repeatedly when GCs evaluate these tools or try to improve their existing line item processes.

What Detail Level Should the SOV Have?

The right granularity depends on contract value, trade complexity, and your ability to verify completion in the field.

Too few line items and you cannot verify progress. A $900K mechanical sub with 5 line items means each item averages $180,000. A 10% error on one line item is an $18,000 overpayment that you cannot detect without breaking the line item down further.

Too many line items and your review drowns in detail. An electrical sub with 120 line items across a $600K contract averages $5,000 per line item. Reviewing 120 completion percentages every billing cycle is impractical and adds minimal accuracy over a well-structured 35-item SOV.

Recommended ranges by contract value:

Contract Value	Line Items	Average Item Value	Review Time Per Cycle
Under $100K	8-15	$7K-$13K	30-45 minutes
$100K-$500K	15-30	$7K-$33K	45-90 minutes
$500K-$2M	25-45	$11K-$80K	90-150 minutes
$2M-$10M	40-70	$29K-$250K	2-4 hours
Over $10M	60-100	$100K+	4-6 hours

The test for any line item is: can your superintendent walk the jobsite and independently estimate the percentage complete for this item? If the answer is no because the scope is too broad, break it down. If the answer is obviously yes because the scope is trivially small, consolidate it.

How Should Change Order Line Items Be Handled?

Change orders should appear as new, distinct line items at the bottom of the SOV. They should never be absorbed into existing line items.

Why separate line items matter: When a $25,000 change order is folded into an existing $200,000 line item, the line item becomes $225,000. The percentage complete on the original scope and the change order work get blended. You lose the ability to track whether the change order work was actually completed, and you lose the ability to verify the change order cost separately during an audit.

Line item software should handle change orders by:

Accepting new line items with a CO reference number that links to the approved change order document.
Automatically updating the contract sum on the summary (G702 equivalent) to reflect approved COs.
Preserving billing history on existing line items when new CO items are added.
Flagging if an existing line item's value changes in the same period a related CO is approved (potential double-count).

Deductive change orders require particular attention. A $15,000 credit should appear as a negative line item, not as a reduction to an existing item's contract value. This preserves the audit trail and prevents the sub from hiding the deduction in a percentage adjustment on the original item.

What Is the Right Number of Line Items?

There is no universal right number. There is a right structure. Line items should follow the scope breakdown in the subcontract, with enough granularity to verify completion and detect overbilling.

Start with the spec sections. The contract specifications divide the work into sections (Division 1-49 in MasterFormat). Each spec section that the sub is responsible for should map to at least one line item. A mechanical sub covering Division 23 (HVAC) might have line items for ductwork fabrication, ductwork installation, equipment procurement, equipment installation, controls, testing and balancing, and insulation.

Add granularity where financial risk is high. If one spec section represents more than 25% of the contract value, break it into sub-items. A $1.5M curtain wall sub should not have a single $900K line item for panel fabrication and installation. Split it into fabrication, delivery, first floor installation, upper floor installation, and sealant/waterproofing.

Consolidate where financial risk is low. General conditions, cleanup, and minor accessory items below $5,000 each can be consolidated into grouped line items. Tracking a $2,000 item at the same level of detail as a $200,000 item wastes review time without improving financial control.

How Do You Verify Completion Percentages?

Completion percentage verification is the bridge between the line item software and physical reality. The software tracks what the sub claims. Verification confirms what actually happened.

Field-based verification: The superintendent or project engineer walks the work area 3-5 days before the billing deadline and records independent completion estimates for each active line item. These field estimates are entered into the line item software and compared against the sub's claimed percentages. Discrepancies exceeding 10% trigger a review conversation with the sub.

Milestone-based verification: For items with clear milestones (equipment delivered, rough-in complete, system tested), the percentage corresponds to milestone achievement rather than a subjective estimate. Equipment procurement is 0% until the PO is issued, 30% when fabrication starts, 70% when delivery occurs, and 100% when installation is complete. Milestone-based items are easier to verify and harder to manipulate.

Quantity-based verification: For unit price items (linear feet of pipe, square feet of drywall, cubic yards of concrete), completion percentage is calculated from installed quantities versus total contract quantities. This is the most objective verification method. If the contract includes 5,000 LF of copper pipe and 3,200 LF are installed, the line item is 64% complete. No judgment required.

Software should support all three methods and allow the PM to select the appropriate method for each line item. A single SOV often includes judgment-based items (general conditions), milestone items (equipment), and quantity items (materials), each requiring a different verification approach.

Should the SOV Match the Bid?

Not necessarily. The bid and the SOV serve different purposes.

The bid is a competitive pricing document structured to win the project. Bid line items are often organized by the sub's cost categories: labor, materials, equipment, overhead, profit. This structure helps the sub price the work competitively but does not support progress billing.

The SOV is a billing document structured to track progress. SOV line items should follow the physical work sequence and enable field verification. This structure may differ significantly from the bid.

Example: A drywall sub's bid might break down as: materials ($180K), labor ($220K), equipment ($15K), overhead ($25K), profit ($60K). Total: $500K. This tells you the sub's cost structure but does not tell you whether Level 3 framing is 60% or 80% complete.

The same sub's SOV should break down by location and activity: Level 1 framing ($45K), Level 1 board ($38K), Level 2 framing ($52K), Level 2 board ($44K), Level 3 framing ($48K), Level 3 board ($41K), finishing all levels ($120K), fire-rated assemblies ($62K), miscellaneous/cleanup ($50K). This structure maps to physical locations you can verify.

The connection between bid and SOV: The SOV total must equal the contract value, which equals the accepted bid amount (adjusted for any negotiated changes). But the internal line item structure should prioritize progress tracking over cost category reporting.

Line item software should allow the GC to define the SOV structure independently of the bid, while maintaining the total contract value as a reconciliation point. Some platforms include a bid-to-SOV mapping feature that traces each SOV line item back to the original bid items for cost analysis.

How Does Retainage Work at the Line Item Level?

Retainage is held at the line item level, not just the contract level. Each G703 line item has a retainage amount calculated from the completed and stored value for that item.

Uniform retainage: The simplest approach. Every line item retains the same percentage (5% or 10%). The software calculates retainage automatically. Total retainage equals total completed and stored times the retainage rate.

Variable retainage: Some contracts reduce retainage after a completion threshold (typically 50%). When a line item crosses 50% complete, the retainage rate on that item drops from 10% to 5%. Different line items cross the threshold at different times, creating a mixed-rate SOV that the software must track individually.

Zero retainage on specific items: Equipment purchases, stored materials, and certain early-phase items may have zero retainage per contract negotiation. The software must support item-level retainage overrides while maintaining the correct totals.

Frequently Asked Questions

Can I change the SOV structure mid-project? Yes, but with caution. Restructuring the SOV mid-project requires rebasing all historical billing data. This creates an audit trail disruption. If restructuring is necessary (due to major scope changes or an unworkable original structure), document the change formally, get the sub's agreement, and verify that all historical totals reconcile after the restructure.

What if the sub refuses to use my SOV structure? The SOV is a contract administration document subject to GC approval. If your subcontract gives you approval authority over the SOV (it should), you can require the sub to conform to your structure. Most subs comply once they understand the structure. The ones who resist often have something to hide in a lump-sum breakdown.

Should mobilization be a separate line item? Yes. Mobilization should always be a separate line item capped at 3-5% of contract value. Embedding mobilization in other line items inflates early billing across multiple items and makes front-loading detection harder.

How do I handle a sub who bills 100% on a line item but the work is not complete? Adjust the percentage down to your field-verified estimate and return the pay app with a written explanation. Do not process a 100% line item that is not 100% complete. A sub who bills 100% on incomplete work is establishing a pattern that will continue until you stop it.

Can line item software integrate with my accounting system? Most modern platforms export data in formats compatible with Sage 300, Viewpoint Vista, CMiC, and QuickBooks. Look for API integration rather than CSV export. API connections update billing data in real time without manual file transfers.

What reports should line item software generate? At minimum: SOV status by sub, billing curve analysis by sub, retainage summary by sub and by project, change order impact on SOV, and overbilling risk report. The overbilling risk report, which flags line items where claimed percentage exceeds field-verified percentage, is the highest-value report for GC financial control.

Get answers faster with automated line item tracking. SubcontractorAudit verifies SOV math, flags overbilling, and tracks every line item across billing periods. Explore pay app audit.