The SOV on a private commercial project looks different from the SOV on a state-funded school. Federal projects add another layer of requirements. Prevailing wage projects need line items that align with certified payroll categories. Each project type imposes specific constraints on how the SOV is structured, what data it must contain, and how it connects to the broader pay application package.

GCs who use a single SOV template across all project types run into compliance failures on public and federal work. This guide covers the requirements by project type and the state-specific variations that affect SOV format.

Public Project SOV Mandates

Public projects funded by state or local governments carry SOV requirements that go beyond standard commercial practice. These requirements exist because public funds demand additional accountability, transparency, and audit capacity.

Common public project SOV requirements:

Separate line items for labor and materials. Many public agencies require the SOV to break every scope item into labor and material components. This is not optional guidance. It is a contractual requirement tied to prevailing wage compliance and funding accountability. A lump sum line item for "HVAC installation - $400,000" would not satisfy a public agency that requires "HVAC labor - $220,000" and "HVAC materials - $180,000" as separate entries.

MBE/WBE/DBE tracking integration. Public projects with minority, women-owned, or disadvantaged business enterprise participation requirements need the SOV to identify which line items are performed by certified firms. Some agencies require the SOV to show the DBE sub's contract value and progress separately from the prime sub's work.

Cost code alignment. State agencies often require SOV line items to align with specific cost coding systems. California's Division of the State Architect (DSA) uses a cost code structure that the SOV must follow. New York's Dormitory Authority has its own format. These codes enable the agency to track spending across projects by category.

Public project SOV requirements by state (selected states):

State	Agency	SOV Requirement	Additional Documentation
California	DSA / DGS	Labor/material split, cost codes per agency standard	Certified payroll, DBE utilization report
New York	DASNY / SCA	Wicks Law separate prime SOVs, detailed cost breakdown	Prevailing wage schedule, M/WBE tracking
Texas	TFC	SOV matching state cost categories	HUB participation reports
Florida	DMS	SOV by CSI division with labor/material split	Certified payroll (if state-funded)
Illinois	CDB	Capital Development Board format	Prevailing wage, BEP utilization
Massachusetts	DCAMM	SOV aligned with filed sub-bid categories	Certified payroll, workforce reports
Ohio	OFCC	Separate labor, material, equipment columns	EDGE participation reporting
Georgia	GSFIC	Agency-specific SOV template required	Certified payroll (state projects)

Federal FAR Requirements

Federal projects governed by the Federal Acquisition Regulation (FAR) have SOV requirements that differ from both commercial and state public projects.

FAR 52.232-5 (Payments Under Fixed-Price Construction Contracts): Requires the contractor to submit a schedule of values for progress payments that is broken down by major work categories. The contracting officer must approve the SOV before the first progress payment.

Key FAR SOV requirements:

Line items must correspond to the contract work breakdown structure (WBS)
Each line item must show the estimated percentage of the total contract value
The SOV must include overhead and profit allocated proportionally across line items (not as separate line items, unless the contracting officer approves separate treatment)
Stored materials require separate identification and must meet the ownership and insurance requirements of FAR 52.232-5(d)

Davis-Bacon prevailing wage impact on SOV: Federal projects subject to Davis-Bacon require certified payroll reports. The SOV labor line items must correlate with the labor classifications on the certified payroll. A plumbing labor line item claiming $45,000 in a billing period should correspond to the journeyman and apprentice hours at the applicable prevailing wage rates documented on the certified payroll for that period.

Small Business Subcontracting Plans (FAR 52.219-9): Federal contracts above $750,000 require small business subcontracting plans. The SOV should enable tracking of small business participation by identifying which line items are performed by small business, HUBZone, 8(a), SDVOSB, or WOSB subcontractors.

Prevailing Wage SOV Considerations

Prevailing wage projects, whether federal (Davis-Bacon) or state, add specific constraints to SOV structure. The SOV must support verification that workers are paid correctly for the work billed.

SOV-to-payroll alignment: Each SOV line item that includes labor must correlate with certified payroll data. If the SOV has a "structural steel erection" line item billing $60,000 in labor this period, the certified payroll should show ironworker hours at the applicable prevailing wage rate totaling approximately $60,000 (accounting for fringe benefits and burdens).

Misalignment between SOV labor billing and certified payroll is a compliance red flag that triggers agency audits. GCs should verify this alignment as part of every pay app review on prevailing wage projects.

Apprentice ratio requirements: Many state prevailing wage laws require specific apprentice-to-journeyman ratios. The SOV should be structured so that line items reflect trade classifications that enable apprentice ratio verification. A blended "mechanical installation" line item makes ratio verification difficult. Separate items for "HVAC journeyman labor" and "HVAC apprentice labor" make it straightforward.

Fringe benefit treatment: Prevailing wage fringe benefits can be paid directly to the worker, contributed to approved benefit plans, or a combination. The SOV should clarify how fringe benefits are included in the labor line items. Some agencies require separate fringe benefit line items. Others require fringe to be embedded in the labor rate.

Prevailing Wage Element	SOV Requirement	Verification Method
Base hourly rate	Reflected in labor line item pricing	Compare SOV labor amount to certified payroll base wages
Fringe benefits	Separate line item or embedded in rate	Verify fringe contributions match approved plan or hourly payment
Apprentice hours	Proportional to journeyman hours per ratio	Cross-reference SOV labor billing with apprentice tracking
Overtime	Billed at applicable OT prevailing rate	Verify OT hours on certified payroll against SOV period billing

State-Specific SOV Formats

Several states have published standard SOV formats that must be used on state-funded projects. Using an AIA G703 or a custom format on these projects does not satisfy the contractual requirement.

California: The Division of the State Architect publishes SOV templates for school construction projects. The template includes specific line items for DSA inspection fees, testing, and commissioning that must appear on every K-12 project SOV. General contractors on DSA projects must use this format or risk pay app rejection.

New York: The Wicks Law requires separate prime contracts for HVAC, electrical, plumbing, and general construction on public projects over $500,000. Each prime contractor submits their own SOV directly to the owner, not through a single GC. This fundamentally changes the SOV structure because there is no consolidated GC SOV on Wicks Law projects.

Texas: The Texas Facilities Commission publishes project accounting guides that include SOV format requirements for state-funded projects. The format requires cost code alignment with the state's project accounting system.

Massachusetts: DCAMM projects follow the filed sub-bid law, which requires certain trades to be bid as filed sub-bids. The SOV must identify filed sub-bid scopes separately from general contractor self-performed or non-filed sub work.

Florida: The Department of Management Services has guidelines for SOV preparation on state building projects. While not a mandatory template, the guidelines specify minimum line item categories and require retainage tracking at the line item level.

Adapting Your SOV Template for Project Type

GCs working across project types need a modular SOV template system. The base structure stays consistent. Project-type modules add required fields and line items.

Base SOV template (all project types):

Item number, description, scheduled value
Work completed (prior, current period)
Materials stored
Total completed and stored, percentage complete
Balance to finish, retainage

Public project module adds:

Labor/material split columns
Cost code field per agency requirements
DBE/MBE participation identifier
Certified payroll reference field

Federal project module adds:

WBS alignment codes
Small business subcontracting identifiers
FAR-compliant overhead/profit allocation
Davis-Bacon wage classification reference

Prevailing wage module adds:

Labor classification columns (journeyman, apprentice, foreman)
Fringe benefit tracking (paid or contributed)
Apprentice ratio calculation
Overtime tracking

Build these as layers on your base template, not as separate templates. A project that is both state-funded and prevailing wage activates two modules on the same base structure. This approach maintains consistency while meeting project-specific requirements.

Frequently Asked Questions

Do public project SOV requirements apply to subcontractors or only the GC? Both. The GC must submit a consolidated SOV that meets agency requirements, and each subcontractor's individual SOV must provide the data needed for the GC's consolidated submission. If the agency requires labor/material splits, every sub's SOV must include labor/material splits.

Can I use AIA G703 format on a public project that does not specify it? Yes, if the G703 captures all required data fields. Many public agencies accept G703 format supplemented with agency-required data (cost codes, DBE tracking, etc.). Verify with the agency before the first submission.

What happens if my SOV does not comply with the state format on a public project? The agency rejects the pay application and returns it for correction. This delays payment by one billing cycle (typically 30 days). Repeated non-compliance can trigger a formal notice and may affect the GC's prequalification status for future projects.

How do I handle prevailing wage on a project with both prevailing wage and non-prevailing wage scopes? Separate the SOV into prevailing wage and non-prevailing wage sections. Each section follows the appropriate requirements. The prevailing wage section includes certified payroll references. The non-prevailing wage section follows standard commercial SOV format. The SOV total still equals the full contract value.

Do federal SOV requirements apply to subcontractors on a federal prime contract? Yes. The prime contractor is responsible for ensuring that subcontractor SOVs comply with FAR requirements. The sub's SOV must align with the project WBS, include appropriate small business identifiers, and support Davis-Bacon verification if applicable.

How often do state SOV format requirements change? State agencies update their SOV formats infrequently, typically every 3-5 years. However, statutory changes to prevailing wage laws, retainage caps, or prompt payment acts can affect SOV content requirements more frequently. Review your state compliance matrix annually.

See how SubcontractorAudit handles multi-project-type SOV compliance. Automated format validation, prevailing wage alignment, and state-specific requirement tracking built in. Request a demo.