The Infrastructure Investment and Jobs Act (IIJA) is the largest federal infrastructure investment in US history; $1.2 trillion in total, with $550 billion directed at new spending across roads, bridges, transit, water, broadband and clean energy. For contractors pursuing this work, it is the most significant pipeline of public construction opportunity in a generation. It is also the most compliance-intensive. Every dollar of IIJA funding comes attached to reporting obligations; Davis-Bacon certified payroll, Buy America documentation, subcontractor compliance flow-down and federal audit trail requirements; that manual, fragmented construction reporting processes simply cannot meet at enterprise scale.
The 2024 Davis-Bacon Final Rule; the most significant update to prevailing wage requirements since the Reagan administration, expanded coverage, restored the three-step wage determination methodology and increased enforcement penalties. The message from Washington is not ambiguous: construction reporting automation is the operational standard the federal government expects on IIJA projects. Contractors who cannot demonstrate it are not equipped to access the work.
What IIJA Actually Requires: The Three Reporting Obligations That Matter
The IIJA's compliance framework is not a single checklist. It is three interlocking statutory obligations; each with its own enforcement mechanism and each carrying consequences that flow down to every subcontractor tier. Understanding precisely what each requires is the starting point for assessing whether your construction reporting automation infrastructure is adequate.
1. Davis-Bacon weekly certified payroll; every worker, every week, every tier
Under Section 41101 of the IIJA, all contractors and subcontractors on IIJA-funded projects must pay prevailing wages and fringe benefits as determined by the Department of Labor, and submit weekly certified payroll reports, Form WH-347 for every worker on site. The 2024 Davis-Bacon Final Rule tightened this significantly: wage determinations are now updated more frequently, worker classifications are more precisely defined and liquidated damages for violations have increased to $29 per day per affected worker.
- Submission: Weekly - WH-347 or approved equivalent with signed Statement of Compliance
- Scope: Every contractor and subcontractor at every tier on IIJA-funded work
- Classification: Correct trade classification per DOL wage determination; misclassification is a violation regardless of intent
- Fringe benefits: Must be paid as specified in the wage determination, or an equivalent cash amount paid directly to workers
- Record retention: Minimum three years after project completion; basic records, certified payrolls and fringe benefit evidence
- Penalties: Back wages + $29/day liquidated damages per violation + contract debarment for wilful non-compliance
The flow-down liability is what makes this particularly significant for enterprise contractors. Prime contractors bear ultimate responsibility for Davis-Bacon compliance across every subcontractor tier, regardless of how many layers of subcontracting sit below them and regardless of whether they were aware of a violation. Without construction reporting automation that extends to subcontractor payroll data across the full chain, prime contractors have no reliable mechanism for meeting this obligation.
2. Build America, Buy America (BABA) - domestic content documentation on every procurement
The Build America, Buy America Act enacted as part of the IIJA requires that all iron, steel, manufactured products and construction materials used on IIJA-funded projects are produced in the United States, with specific domestic content thresholds that vary by material category. The requirements are categorical:
- Iron and steel: all manufacturing processes from initial melting and pouring through to coatings must occur in the United States. No exceptions for partial US manufacturing.
- Manufactured products: must be manufactured in the US and the cost of domestic components must exceed 55 percent of total component costs requiring detailed sub-component tracing.
- Construction materials: all manufacturing processes must occur in the US. Certain materials; cement, aggregates, binding agents are currently excluded from this requirement, but the exclusion list is narrow.
BABA waivers for Public Interest, Nonavailability, or Unreasonable Cost exist but require a rigorous application and review process, typically involving public comment and the Made in America Office. They are not a routine fallback. For enterprise contractors, the practical implication is that every procurement decision on an IIJA-funded project requires documented domestic content evidence at the point of purchase, not assembled retrospectively when an audit request arrives.
3. Federal audit trail - comprehensive, on-demand, covering the full project lifecycle
Both Davis-Bacon enforcement, conducted by the Department of Labor's Wage and Hour Division and BABA compliance reviews operate through federal audit. The expectation is not that contractors can produce documentation if given sufficient time to locate it. The expectation is that documentation is immediately accessible, organised and complete. Audits can be requested years after project completion. Construction reporting automation that maintains a continuous, real-time audit trail; covering payroll, procurement, subcontractor engagement, change orders and cost allocation, does not need to prepare for audit. It is always prepared.
Construction Reporting Automation: Built In Versus Bolted On
There are two ways enterprise contractors approach construction reporting automation on IIJA projects. The first is to bolt compliance tools onto existing systems; a certified payroll module attached to a standalone HR platform, BABA tracking maintained in a separate procurement spreadsheet, audit documentation compiled from email chains and file servers. The second is to build reporting automation into the operational fabric; where payroll, procurement, subcontractor data, and project cost management share a single integrated environment, and compliance outputs are a natural by-product of daily operations.
The difference is not marginal. It is architectural. And it shows up precisely when it matters most.
Certified payroll: weekly export vs. live output
In the bolted-on model, certified payroll is a weekly manual exercise: export payroll data, cross-reference against the DOL wage determination for each classification, populate a WH-347 form, chase subcontractor submissions, and sign off. In a construction reporting automation environment built on unified ERP data; where Xpedeon connects workforce records, trade classification and project assignment to live payroll, the WH-347 is generated automatically from the data that already exists. There is no export, no reconciliation and no dependency on a project manager remembering to initiate the process. The report is a live output of how the project is running.
BABA documentation: closeout assembly vs. procurement capture
In the bolted-on model, BABA documentation is a closeout task; a retrospective effort to locate supplier certifications, country-of-origin evidence, and domestic content declarations for materials that were procured months earlier. In a construction reporting automation environment where procurement is connected to project records at purchase order level, domestic content evidence is captured at the moment of procurement, linked to the specific IIJA project, and stored with full provenance. When the audit request arrives, the documentation package is already assembled.
Audit trail: reconstructed vs. always current
In the bolted-on model, producing an audit trail under pressure means weeks of searching across disconnected systems; email archives, cloud storage, HR platforms, accounting software trying to reconstruct a coherent record of what happened on a project that may have completed 18 months ago. In a construction reporting automation environment built on integrated ERP data, the audit trail is not reconstructed. It has been running continuously since day one. Every payroll submission, procurement decision, subcontractor engagement, and cost allocation is logged automatically with user, timestamp, and status, producible in hours, not weeks. This is the kind of operational readiness that construction governance reporting frameworks are designed to support and that the IIJA's enforcement environment now demands.
How Xpedeon Delivers Construction Reporting Automation for IIJA-Funded Projects and What to Look For
Xpedeon is an end-to-end ERP platform built specifically for construction and infrastructure. Its construction reporting automation capabilities are not a compliance module attached to a generic project management system, they are a native output of the same unified data environment used by every operational function across the business. Cost management, commercial management, contract administration, procurement and subcontractor management all operate within the same data architecture. Construction reporting automation is what architecture produces automatically.
For enterprise contractors operating on IIJA-funded infrastructure, Xpedeon connects:
- Workforce data to certified payroll output: hours, trade classification and project assignment connected to DOL wage determinations, applying the correct prevailing wage rate automatically and generating WH-347-compliant output weekly without manual data preparation.
- Subcontractor compliance tracking: subcontractor payroll submissions monitored across all tiers, with automated alerts for missing or late submissions before they become prime contractor liability exposure.
- Procurement to BABA documentation: domestic content evidence captured at purchase order level through contract management workflows, linked to the specific IIJA project and contract, producible for federal audit on demand without manual assembly.
- Real-time audit trail: every cost allocation, payroll submission, procurement decision, subcontractor engagement and compliance verification logged automatically with user, timestamp and status across all entities and all IIJA-funded projects simultaneously.
- Portfolio-level compliance visibility: certified payroll status, BABA compliance flags and subcontractor submission tracking consolidated at portfolio level connected to the same construction governance reporting and forecasting layer used across the business.
- Cost and compliance in a single view: subcontractor compliance data connected to project cost, CVR and cash flow forecasting, so compliance and commercial management are part of the same operational picture, not parallel disconnected processes.
The RICS Digitalisation in Construction Report 2024 identifies data fragmentation as the primary barrier to digital compliance capability across the sector. Construction reporting automation built on connected ERP data; where payroll, procurement, subcontractor and cost data share the same source resolves that fragmentation for federal compliance reporting as completely as it does for project cost and commercial management.
What to look for when evaluating construction reporting automation for federal projects
- Certified payroll integration: does the platform generate WH-347-compliant output directly from workforce and project data, or require manual assembly?
- Wage determination management: does it apply the correct DOL prevailing wage rate automatically by project, country and trade classification; and update as determinations change?
- Subcontractor compliance tracking: does automation extend to every subcontractor tier; with alerts for missing or non-compliant submissions before they become prime contractor liability?
- BABA documentation at procurement: is domestic content evidence captured at purchase order level, linked to the specific IIJA project and producible on demand without manual assembly?
- Real-time audit trail: is every compliance event logged automatically with full provenance, accessible across all projects and entities without manual preparation?
- Integration with cost and commercial data: is compliance reporting connected to the same environment as project cost, CVR and forecasting; or maintained in a silo?
Conclusion
The $550 billion in IIJA infrastructure funding is the most significant construction opportunity of this decade in the United States. It is also a direct test of whether enterprise contractors have the construction reporting automation infrastructure to access it. Davis-Bacon's 2024 rule update, BABA's domestic content enforcement and the federal government's explicit investment in digital construction management systems collectively signal that manual reporting processes are not the baseline the federal government expects on IIJA-funded work.
Prime contractors that cannot demonstrate automated, connected, audit-ready reporting across certified payroll, procurement and subcontractor compliance are carrying liability exposure on every IIJA-funded project they operate; and are at risk of losing access to the contracts entirely. The $100 million earmarked for digital construction management is not a reward for early adopters. It is a clear statement of the standard.
For enterprise contractors, the question is straightforward: does your construction reporting automation cover the full IIJA compliance picture; certified payroll, BABA, subcontractor tracking and real-time audit trail, connected to the same data environment as your construction analytics platform and portfolio reporting? If not, the gap is not a technology problem. It is a market access problem.
See how Xpedeon's construction reporting automation connects certified payroll, compliance and real-time audit trail with project cost and commercial management.