Public works compliance software.

Software that automates the statutory filings required on publicly-funded construction projects under Davis-Bacon, the Service Contract Act, state prevailing wage laws, and project-specific labor compliance programs. Core capabilities: certified payroll (WH-347), apprenticeship filings (DAS 140 and 142 in California), prevailing wage rate determinations, mechanic lien rights tracking, certificate of insurance cascade, and OSHA injury logs. Generic construction management software (Procore, Fieldwire) does not include these workflows natively.

WH-347 is the federal Statement of Compliance form prescribed by the US Department of Labor for federal-aid public-works projects under Davis-Bacon. "Certified payroll" is the broader term — states often have their own forms in addition to or in place of WH-347. California requires DIR eCPR uploads through the DIR portal; Massachusetts uses its own WR-1; New York LS-185 supplements WH-347. A complete certified payroll workflow generates the right form for each jurisdiction from a single set of timesheet inputs.

On a California public-works project subject to apprenticeship rules, the contractor files DAS 140 to give the local apprenticeship committee notice that the project exists and the contractor intends to comply. If the contractor needs apprentices it does not have on its own program, it files DAS 142 to request the committee provide dispatched apprentices. Both forms are submitted to every apprenticeship committee in the geographic area of the project, in every craft on the job. Manual filing is the failure mode that triggers DIR penalties on otherwise compliant projects.

Most state public-works claim statutes require the contractor to give written notice of a claim event within a short window — five days is the common California threshold for certain claim types — before the right to recover is forfeited. The failure mode is administrative: the project team encounters the event but fails to recognize it, log it, and serve formal notice within the window. Compliance software detects the event from existing project signals (RFI, change-order request, daily report photo, T&M ticket), starts the clock, and surfaces the deadline to a responsible role before forfeiture. The dollar exposure on a single missed claim is routinely six or seven figures.

On a typical public-works project, the owner requires the GC to carry insurance, the GC requires every sub to carry insurance, and the sub requires every lower-tier sub to carry insurance. Each layer must have the right limits, the right additional insureds, the right primary-and-non-contributory wording, and the right endorsements. The cascade fails when one sub uploads a COI but the lower-tier-sub COI is missing or expired. Software tracks every certificate by issue and expiry date with alerts at 90/60/45/30/15/0 days, blocks workflow on missing required policy kinds, and produces verification records auditors can read.

The Experience Modification Rate (X-Mod) is computed by NCCI or a state bureau like WCIRB-CA from a contractor's payroll by workers-comp class code and actual loss experience over the prior three policy years. An X-Mod above 1.0 prices the contractor out of bids that have an X-Mod cap. Real-time X-Mod scenario modeling — off live certified payroll, not last year's audit — lets a contractor see the next-year impact of a safety improvement or a class-code change before binding the renewal.

On a generalist stack: yes, typically four to six tools plus integration tax. The data does not flow between them; the certified payroll system does not know about the change order that drove the labor overrun; the COI tracker does not block the clock-in when the WC policy lapsed. The result is statutory deadlines missed in the gaps. A single-data-layer platform built for public-works contractors trades feature parity with horizontal SaaS for integrated workflow that catches the deadline before forfeiture.