8.1 Schedule of Values (SOV) Preparation & Review

8.1 Schedule of Values (SOV) Preparation & Review

The financial administration of a construction contract rests entirely upon an accurate, objective, and defensible cost baseline. For the ARE 5.0 Construction & Evaluation (CE) division, candidates must master the preparation, structural formatting, and rigorous architectural review of the Schedule of Values (SOV). Governed primarily by AIA Document A201-2017 (General Conditions of the Contract for Construction), Section 9.2, the Schedule of Values serves as the fundamental yardstick against which all subsequent monthly progress billings are measured.

If an architect fails to critically audit the initial SOV, the project is exposed to severe financial vulnerabilities, including contractor overpayment, cash-flow unbalancing, and catastrophic losses if a contractor defaults early in construction.

---

Contractual Foundation: AIA Document A201-2017 Section 9.2

Under AIA Document A201-2017 Section 9.2, the obligations regarding the SOV are explicitly defined:

"Where the Contract is based on a stipulated sum or Guaranteed Maximum Price, the Contractor shall submit a schedule of values to the Architect before the first Application for Payment, allocating the entire Contract Sum to the various portions of the Work. The schedule of values shall be prepared in the form, and supported by the data to substantiate its accuracy, required by the Architect. This schedule, unless objected to by the Architect, shall be used as a basis for reviewing the Contractor's Applications for Payment."

Several vital legal and administrative principles emerge directly from this contractual language:

1. Mandatory Condition Precedent: The contractor cannot submit a valid first Application for Payment until the SOV has been submitted and reviewed. The architect should not certify progress payments against an unsubmitted or disputed SOV.
2. Allocation of the Entire Contract Sum: In a stipulated sum contract (AIA Document A101-2017) or Guaranteed Maximum Price (GMP) contract (AIA Document A102-2017 or A133-2019), the sum of all line items in the SOV must equal exactly 100% of the Contract Sum. Line items cannot sum to less than or exceed the executed contract value.
3. Architect's Authority to Mandate Form and Substantiating Data: The architect possesses contractual authority to dictate the format (e.g., AIA Document G703) and demand supporting documentation (subcontractor agreements, vendor purchase orders, material takeoffs, and labor estimates) to verify the legitimacy of each number.
4. Standard of 'Unless Objected To' vs. Formal Approval: Contractually, the architect does not 'approve' the SOV in a manner that warrants contractor profit margins or assumes responsibility for contractor bidding adequacy. Instead, the architect reviews the schedule to ensure it is balanced and realistic. If the architect finds flaws, the architect must formally object in writing, requiring corrections before payment processing.

---

Structural Formatting: CSI MasterFormat and Line-Item Granularity

A common administrative failure in construction management is accepting an SOV that is too broad or aggregated. To function effectively as a tool for evaluating monthly progress, the architect may require an SOV organized using the Construction Specifications Institute (CSI) MasterFormat 50-division classification system, matching the organizational structure of the project manual.

Why Broad Division Lump Sums Must Be Rejected

If an SOV merely lists broad numbers—such as 'Division 09 - Finishes: $850,000' or 'Division 26 - Electrical: $1,200,000'—the architect has no objective mechanism during monthly site observations to verify whether the contractor has completed 10%, 25%, or 40% of the electrical work.

To provide verifiable benchmarks, the architect must require that major trade divisions be broken down into discrete work packages and distinct physical areas:

• Separation of Labor and Materials: Line items should disaggregate procurement costs from field installation labor. For expensive equipment packages (such as chillers, switchgear, elevators, and custom curtain walls), separating fabrication and delivery from physical installation ensures that the contractor does not bill for installation labor when materials are merely sitting in crates.
• Disaggregation by Subcontractor and Major Work Package: Each line item should correlate directly with individual trade subcontracts, supplier purchase orders, or distinct building phases (e.g., Building A vs. Building B, or Substructure vs. Superstructure).
• Floor-by-Floor or Phased Breakdown: On multi-story or multi-building projects, major repetitive scopes (such as interior metal stud framing, drywall, rough-in mechanical, and acoustic ceilings) should be broken down by floor level or construction phase to allow straightforward field visual audits.

---

Detecting Unbalancing and Front-Loading

The most critical fiduciary responsibility of the architect during SOV review is detecting and eliminating front-loading (also known as unbalancing the schedule of values).

Mechanics and Motives of Front-Loading

Front-loading occurs when a contractor artificially inflates the monetary value of work performed early in the construction schedule—such as mobilization, site clearing, mass earthwork, utility trenching, and foundation concrete—while proportionately deflating the monetary value of work executed in the late stages of the project, such as drywall, interior painting, architectural millwork, flooring, mechanical balancing, and commissioning.

Contractors are incentivized to front-load for two primary reasons:

1. Generating Early Working Capital: Contractors often operate with tight cash reserves. By overbilling early scopes, the contractor uses the owner's capital to fund company overhead, purchase equipment, or subsidize other struggling projects.
2. Mitigating Financing Costs: Securing early cash flow reduces the contractor's reliance on commercial lines of credit, saving interest expenses at the owner's expense.

The Owner's Risk: Contractor Abandonment and Default

Front-loading creates a severe financial hazard for the building owner. When the contractor bills and receives $1,500,000 for work that objectively cost only $800,000 to construct, the contractor has received an advance payment from the owner.

If the contractor subsequently encounters financial distress, becomes insolvent, or defaults at 40% project completion, the remaining funds left in the Contract Sum are insufficient to hire a replacement contractor to finish the work. The remaining trades (finishes, MEP trim-out, commissioning) were under-allocated on the SOV.

A replacement contractor bidding on the unfinished project will demand true market rates to complete the under-valued late packages. The owner faces an immediate budget deficit, and disputes with the contractor's performance bond surety will inevitably escalate regarding whether the owner and architect negligently overpaid the contractor.

Common Red Flags of Front-Loading

• Inflated Mobilization: Mobilization listed at 5% to 10% of the total contract value without extensive documentation of temporary facilities, security, crane staging, or utility setups. There is no universal AIA percentage cap; evaluate substantiated project requirements.
• Excessive Earthwork and Foundation Values: Mass excavation, deep piers, or foundation concrete priced at 150% to 200% of typical regional unit rates.
• Disproportionate Rough-In vs. Trim-Out Allocations: Mechanical, electrical, and plumbing trades carrying 80% to 90% of their subcontract value in rough-in piping/conduit, leaving only 10% to 20% for fixtures, equipment connections, testing, and balancing.
• Deflated Final Finishes and Closeout Items: Interior painting, resilient flooring, punch list completion, and closeout submittals listed at nominal or below-market sums.

---

Allocating Contractor Fees, Insurance, Bonds, and General Conditions

Another frequent area of dispute on the SOV involves the allocation of the contractor's General Conditions, insurance premiums, surety bonds, and overhead and profit.

Performance and Payment Bonds

Premiums for AIA Document A312 Performance and Payment Bonds are paid by the contractor to the surety broker upfront upon contract execution. Therefore, it is standard and legitimate for the contractor to list bond costs as a discrete line item on the SOV and bill 100% of this line item in the first Application for Payment. However, the architect must require that the contractor provide a copy of the surety's paid invoice or receipt as substantiating data before certifying the payment.

Builder's Risk and General Liability Insurance

Similar to bonds, contractor insurance policies are typically bound prior to mobilization. If listed as a separate line item, insurance premiums can be billed upon proof of coverage and paid premium invoices.

Contractor Fee (Overhead and Profit)

Contractor overhead and profit (fee) can be handled in two contractually acceptable ways:

1. Prorated Across All Trade Items: The fee is distributed proportionally into the unit pricing of every individual line item across the entire SOV.
2. Discrete Line Item Billed Proportionally: The fee is listed as a separate line item at the bottom of the SOV. When listed separately, the contractor is not permitted to bill the fee upfront. Instead, the fee must be billed strictly in direct proportion to the overall percentage of trade work completed during each monthly billing cycle.

General Conditions (Jobsite Overhead)

General Conditions encompass temporary jobsite utilities, field office trailers, project management salaries, safety equipment, sanitary facilities, and daily cleanup. Because general conditions represent ongoing operational expenses incurred continuously throughout construction, their billing follows the agreed cost allocation and applicable payment terms rather than an automatic universal equal-month rule.

For example, on a 12-month construction project with $240,000 allocated to General Conditions, assume the contract allocates this recurring cost evenly at $20,000 per month (1/12th of the total). If the contractor bills 50% of general conditions in the first two months, the architect must formally object to front-loading.

Balanced vs. Front-Loaded Schedule of Values Analysis

The table below contrasts a balanced, compliant SOV line-item structure against an unbalanced, front-loaded submission for a hypothetical commercial project (selected packages only, not a complete SOV totaling the contract):

Source and application

A201-2017 official sample. Checked October 16, 2026. Apply the cited form edition and the actual project amendments, adopted codes and supplied scenario assumptions. Numerical examples are teaching inputs unless expressly attributed to a requirement.