Public Works Survival Guide CA

Public works contracts subject to prevailing wage generally require the contractor — and applicable subcontractors — to be registered with the Department of Industrial Relations before bidding, not just before starting work. Registration has to be renewed annually and lapses can affect bid eligibility.

Prevailing wage itself sets minimum pay rates by trade classification and locality, determined by DIR, separate from whatever a contractor's normal payroll structure looks like — misclassifying workers or paying below the applicable rate is a compliance issue independent of insurance.

Performance and payment bonds are standard on public works above a state or local dollar threshold, and the bonding process for a specific project is a separate underwriting exercise from a standard annual contractor license bond — surety review commonly covers financial statements, working capital, bonding history and current backlog, not just credit.

Bonding capacity — both single-job and aggregate — is a real constraint for growing contractors. A contractor bidding several public projects at once needs enough aggregate capacity to cover all of them, not just the one currently being bid.

Once work begins, certified payroll reporting is typically required on a regular schedule for the duration of the project, documenting that workers were paid at least the applicable prevailing wage rate for their classification. Missing or inaccurate certified payroll reports are a common source of compliance findings on public jobs.

Subcontractor compliance is the prime contractor's problem too — verify that subcontractors working on a public project are separately DIR-registered and submitting their own certified payroll, rather than assuming it's handled.

The most common rejection points aren't exotic — an expired DIR registration, a certificate of insurance that doesn't match the contract's actual required limits or endorsements, a bond that's short of the project's required amount, or an AM Best rating on the carrier that doesn't meet the stated minimum.

Reading the actual bid documents' insurance and bonding requirements before bidding — not after award — is what avoids a scramble to fix a mismatch on a compressed timeline. If a requirement looks unusual or unclear, ask the awarding body directly rather than guessing.

Whether a contractor is a union signatory or runs open shop, California's prevailing wage law applies the same way on a covered public works project — the state sets a wage floor for each craft classification that has to be paid regardless of union status. A signatory contractor meets part of that obligation through union trust fund contributions (health and welfare, pension, training); an open shop contractor typically has to pay the equivalent fringe amount directly in cash. Apprenticeship utilization rules apply to both as well, and an open shop contractor fulfills them through any DIR-approved apprenticeship program, not just a union hall.

Some larger public projects — school construction, hospital work, major municipal infrastructure — are built under a Project Labor Agreement (PLA), a pre-hire agreement covering the whole project. An open shop contractor can bid a PLA project, but agrees to follow the PLA's wage, hour, and hiring terms for that project only; it doesn't change their company's union status elsewhere. What a PLA does not change is the insurance and bonding picture — GL, workers compensation, and bond requirements are still set by the bid documents and apply the same way regardless of union status. Requirements in this area are set by statute, regulation, and the specific contract or project documents involved, and they can change — this is general educational information, not legal advice; for anything case-specific, consult a licensed attorney or the applicable regulatory authority having jurisdiction.

A new or extended water main isn't accepted just because it holds pressure — it has to pass a specific sequence under AWWA standards: hydrostatic pressure testing (AWWA C600) to confirm the pipe withstands test pressure without leakage, followed by disinfection (AWWA C651) — flushing debris, introducing a chlorine solution (typically 25 to 50 mg/L), and holding it for a minimum of 24 hours. Only after that comes the real acceptance gate: two consecutive sets of clean bacteriological (coliform) samples, taken 24 hours apart, before the main can actually be placed in service.

A real-world example: a contractor completes pressure testing successfully and assumes the main is ready to connect, only to find the water district won't authorize service until the second clean coliform sample clears — a minimum 48-hour clock from the start of disinfection that can't be compressed no matter how good the pressure test looked. The responsible parties are the contractor (running the test sequence correctly, in order) and the water district's inspector (reviewing and authorizing each step before the next proceeds).

The insurance and bonding impact: a water main that fails coliform testing after passing pressure testing isn't a workmanship failure in most cases — it's a sequencing or contamination issue during construction, but the schedule delay it causes is identical either way, and on a bonded public works project that delay can push toward retention and bond-release timelines discussed elsewhere in this guide. Planning the full disinfection-and-sample sequence into the schedule from the start — not treating it as a quick formality after pressure testing — avoids a real, common source of turnover delay.

Sewer acceptance layers three distinct tests, each catching a different failure mode: CCTV inspection (commonly NASSCO-standard video review, checking pipe condition, joints and lateral connections along the full run — covered in more depth in the Utility Coordination guide); mandrel testing, which pulls a sized gauge through the pipe to confirm it hasn't deflected out of round beyond an allowable tolerance; and manhole vacuum testing, which confirms manhole structures themselves are watertight, independent of the pipe runs between them.

A real-world example: a gravity sewer line passes CCTV inspection with no visible defects, but fails mandrel testing because bedding compaction under the pipe was inconsistent, letting the pipe deflect beyond tolerance even though nothing looks wrong on video — a defect CCTV alone wouldn't catch. The responsible parties are the contractor (installation and bedding) and the agency inspector (verifying all three tests independently, not accepting one as a substitute for another).

The insurance and public works impact: a mandrel or vacuum test failure discovered after backfill generally means excavating back into a completed section to correct it — a real cost and schedule consequence that a passed CCTV inspection alone won't prevent. Confirming bedding and compaction meet spec before backfill, not relying on CCTV as the only quality check, is what actually prevents this specific, avoidable rework.

Storm drain (MS4 — municipal separate storm sewer system) infrastructure is regulated as a genuinely distinct system from sanitary sewer, not just a differently named pipe — storm drain discharge falls under the NPDES framework administered by the State Water Resources Control Board and the 9 Regional Water Quality Control Boards, tied to stormwater pollution prevention requirements rather than sanitary sewer capacity and treatment. A contractor treating storm drain acceptance as functionally identical to sewer acceptance — same tests, same department, same expectations — is working from the wrong assumption.

A real-world example: a development's storm drain system passes the same CCTV and pressure verification a sewer line would need, but the acceptance review also checks detention basin functionality and connection to the broader MS4 system in a way sanitary sewer review never would — because the storm drain system's actual regulatory purpose (preventing pollutant discharge into waters of the state) is different from sewer's. The responsible parties are the developer/contractor and, often, a genuinely separate review team or agency division than the one handling sanitary sewer on the same project.

The insurance and public works impact: confirming which department or agency actually reviews storm drain acceptance on a specific project — rather than assuming it's the same sewer team — avoids submitting a turnover package to the wrong reviewer or missing a stormwater-specific requirement (like detention basin capacity verification) that a sewer-focused submission wouldn't have anticipated.

Electrical acceptance on a project actually involves two genuinely separate approvals, not one: the city or county building department (the AHJ) conducts its own electrical permit inspections — rough-in and final — checking that wiring, grounding, GFCI/AFCI protection and panel labeling meet code. Separately, the serving electric utility (PG&E, SMUD, or the applicable municipal utility) has to inspect and accept the actual service equipment — transformer, meter, service point — before it will energize the connection. Passing one doesn't authorize the other.

A real-world example: a project passes its final AHJ electrical inspection and is ready to be energized as far as the city is concerned, but the utility hasn't yet inspected the transformer pad clearances or completed its own service-point review — the project sits unenergized despite being fully code-compliant from the building department's perspective, because the utility's separate acceptance is still pending. The responsible parties are the electrical contractor (coordinating both approvals, not just one), the AHJ inspector, and the utility's own service planner/inspector.

The insurance and bonding impact: an unenergized project awaiting utility acceptance after passing AHJ inspection is a real, easy-to-underestimate schedule risk — confirming utility acceptance timelines early (covered in more depth in the Utility Coordination guide's energization-delay content) and tracking the two approval paths separately, rather than assuming AHJ sign-off means the project is done electrically, avoids discovering this gap at the worst possible time in the schedule.

Gas main and service acceptance runs on its own pressure-testing and safety sequence, distinct from both water and electric — a new or relocated gas line generally needs to hold a specified test pressure for a defined duration with no measurable drop before the utility will authorize the next step, purging the line of air and introducing odorized gas under a controlled procedure.

A real-world example: a gas line passes its pressure test cleanly, but the purge procedure itself — displacing air with gas in a controlled, monitored sequence — is what the utility actually requires directly before service, and skipping ahead of that controlled purge (rather than letting the utility crew run it per their own protocol) is both a real safety violation and a common reason a gas acceptance gets held up. The responsible parties are the utility's own crew (who generally perform or directly oversee the purge) and the contractor (ensuring the line and test documentation are ready before requesting it).

The insurance and public works impact: gas acceptance delays tend to be less forgiving on schedule than other utilities specifically because of the safety-driven purge sequence — it can't be rushed or worked around the way some administrative delays can. Requesting gas service and scheduling the purge early, with test documentation ready in advance, avoids adding an entirely avoidable delay on top of a step that already has a fixed minimum timeline.

Fiber and telecom acceptance is a genuinely different animal from water, sewer, storm drain, electric and gas — there's no single statewide regulatory body setting a mandatory public acceptance standard the way AWWA governs water or NPDES governs storm drain. Acceptance criteria come from a mix of industry standards, the specific project's own specifications, and the reviewing engineer's judgment — the formal certification standard (TIA-568.3-D) actually requires Tier 1/OLTS testing, even though OTDR testing is common in practice and frequently used for cable acceptance, splice and connector loss verification, and fault location.

A real-world example: a contractor submits OTDR traces expecting them to satisfy a fiber provider's acceptance requirement, only to learn the specific project spec calls for formal Tier 1 certification — a different, more rigorous test than what was actually performed, requiring re-testing before turnover can proceed. The responsible parties are the contractor (confirming which specific test standard a particular provider or contract actually requires, not assuming OTDR alone satisfies it) and the fiber provider or GIS/telecom reviewer (whose acceptance criteria can genuinely vary project to project).

The insurance and public works impact: because fiber acceptance isn't standardized the way the other five utilities are, confirming the actual testing requirement directly with the specific provider or contract — in writing, before construction — matters more here than on any other utility type covered in this guide, since there's no single external standard to fall back on if expectations weren't confirmed up front.

Each utility's testing regime comes from a different governing body, and none of them substitute for another: water follows AWWA (C600 pressure, C651 disinfection); sewer and storm drain commonly follow NASSCO-standard CCTV practice alongside mandrel and vacuum testing, though storm drain acceptance layers additional NPDES-driven requirements sewer doesn't have; electric and gas each follow the serving utility's own internal standards, separate from AHJ code inspection; and fiber follows a mix of TIA standards and project-specific specifications with no single mandatory public regulator.

The practical impact of this fragmentation: a testing plan built around one utility's requirements generally can't be reused for another, even superficially similar one, on the same project. Building a project's testing schedule around each utility's actual, specific requirement — confirmed with that utility or agency directly — rather than assuming a generic "utility testing" checklist covers all six, is what actually keeps a multi-utility project's turnover on schedule.

A turnover submission generally needs several distinct documents, not just a completed test result: the actual test reports (pressure, disinfection, CCTV, mandrel, vacuum, OTDR/Tier 1, whichever apply to that utility), material certifications confirming the pipe, conduit or equipment installed matches what was specified, and a contractor's certification of installation confirming the work was performed per the approved plans.

A real-world example: a contractor submits clean test results but the turnover package is rejected because material certifications for the pipe actually installed weren't included — the testing was fine, but the agency can't confirm the correct material was used without that separate document. The responsible parties are the contractor (assembling the complete package, not just the test results) and the agency reviewer (checking the full package against its own checklist, not just the headline test outcome).

The insurance and public works impact: an incomplete documentation package is one of the single most common, most avoidable causes of turnover delay covered throughout this guide — building the documentation file as work happens, confirming exactly what each agency's package requires before assembling it, and treating documentation as equal in importance to the physical testing itself is what actually prevents this.

California Government Code Section 4216, effective January 1, 2022, requires water utilities to use GIS to record the location of newly constructed distribution system assets — a real, current statutory requirement that's changed what "record drawings" means in practice at most California water and sewer agencies. A hand-marked redline print, while still the starting point, generally isn't the final deliverable anymore — many agencies now require digital CAD and/or GIS-compatible submission (shapefiles or geodatabase files with attribute data), not just a scanned paper record.

A real-world example: a contractor submits traditional hand-marked as-built drawings expecting them to satisfy record drawing requirements, only to learn the water district specifically requires GIS-compatible digital submission to update its own distribution system mapping under its Section 4216 obligations — requiring the drawings to be converted or resubmitted before turnover can close. The responsible parties are the contractor or surveyor preparing the record drawings and the agency's own GIS/engineering department reviewing the submission format.

The insurance and public works impact: confirming the actual required submission format — CAD, GIS-compatible, or both — directly with each specific agency before finalizing record drawings, not assuming a traditional hand-marked print will satisfy a modern digital requirement, avoids a real, current, and increasingly common source of turnover delay tied directly to a real 2022 statutory change most contractors haven't fully caught up with yet.

A multi-utility project generally needs a genuinely separate turnover package for each utility — water, sewer, storm drain, electric, gas, fiber — each assembled to that specific agency's own requirements, reviewed by that agency's own staff, and signed off independently. There's no single combined "utility turnover" submission that satisfies all six at once, even on a project where all six utilities were installed in the same joint trench.

A real-world example: a subdivision developer assumes that once the water district accepts its utility, the remaining turnovers will follow quickly since all the infrastructure was built together — but the sewer, storm drain, electric, gas and fiber turnovers are each on their own independent timeline, reviewed by different staff with different workloads, and one utility's acceptance genuinely has no bearing on another's status. The responsible parties are the developer or GC (tracking all six turnover packages independently, not assuming progress on one implies progress on another) and each individual utility or agency's own review staff.

The insurance, bonding and public works impact: because retention release and bond release (covered elsewhere in this guide) generally depend on full project acceptance, a single lagging utility turnover — even a minor one like fiber — can hold up the financial closeout of an otherwise fully complete project. Tracking all six turnover packages on their own independent log, with their own status and next steps, rather than treating utility turnover as one combined task, is what actually keeps a multi-utility project's closeout from stalling on the single slowest utility.

This guide's utility acceptance and turnover content is educational information about how these processes generally work across California water, sewer, storm drain, electric, gas and fiber utilities — not legal, engineering or insurance advice for a specific project. Testing standards, documentation requirements, and record drawing formats are set by the specific utility, agency, statute and regulation involved, and they change — the actual project documents, contract requirements, and the specific utility or agency's current standards control, not this general overview.

For anything project-specific — confirming a specific utility's current testing or documentation requirement, resolving a turnover dispute, or reviewing how a delayed utility acceptance affects bonding or insurance on an active project — work directly with the utility or agency itself, your broker and surety, and, where legal questions are involved, a licensed attorney.

For how a surety actually calculates what a contractor can bond, see How Sureties Commonly Set Bonding Capacity, and for what changes for a subcontractor working under an owner-controlled program, see OCIP vs. CCIP for Subcontractors. For how prevailing wage requirements move the actual cost of a public-works insurance program, see How Prevailing Wage Can Affect Your Insurance Costs on Public Works.