Surviving an OCIP/CCIP Wrap-Up Audit

Wrap-up audits are not a one-time event at project close. Annual premium audits run throughout the program — the carrier's auditor may conduct a physical review of your payroll records each year, or may request a voluntary submission from your office. At project completion, a final audit reconciles all payroll submitted during the program against your actual records and determines whether the initial insurance credit calculation was correct.

The audit has three verification targets. First, your monthly on-site payroll records must match the payroll submissions you made to the administrator throughout the project. Second, every subcontractor and sub-tier contractor must have been enrolled in the program with written confirmation before they started work. Third, any contractor excluded from the wrap-up must have maintained their own coverage while on-site — and you must have their certificates on file to prove it.

The final audit also determines the true-up: whether the actual payroll for the project matches the estimate used when the insurance credit was originally calculated. If actual payroll exceeded that estimate — which happens when projects go over schedule or add scope through change orders — the difference results in additional premium. Most GCs don't see it coming because the original credit was set at bid time and no one updated it when labor overruns accumulated.

GCs who track subcontractor compliance at scale — enrolled subs, excluded subs, COI expirations, and payroll documentation — use dedicated software rather than spreadsheets. See how YourStanding compares to tools like MyCOI for managing wrap-up and subcontractor insurance compliance.

"On-site payroll" in a wrap-up program is a specific, narrow definition. Only labor performed at or directly emanating from the project site is covered. Off-site fabrication, remote design work, and material hauling are excluded. A contractor's total company payroll across all projects is not the number — only the hours worked on this site under this program.

Payroll must be allocated by Workers' Compensation class codes — the NCCI classifications that correspond to trade and work type. These do not map exactly to CSI specification divisions. Mixing class codes in payroll submissions, or lumping all labor under a single classification, is an audit finding that triggers corrections and additional scrutiny.

Monthly reporting runs through the full project period. If site work pauses — a weather delay, permit hold, or winter demobilization — the program's reporting schedule doesn't pause with it. Administrators track delinquent submissions, and gaps in the monthly record are an audit liability even when the underlying payroll was zero.

Red flag: A contractor who submits payroll reports in a batch at project close rather than monthly during the project signals poor record-keeping and gives the auditor reason to scrutinize the numbers more closely. Monthly cadence is a program requirement, not a recommendation.

Action: Submit monthly payroll reports on the administrator's required schedule for every period, including pauses in active site work. Maintain source records (certified payroll by class code, per project) through the project's statutory period, which varies by state and can extend years beyond substantial completion.

Every subcontractor and sub-tier contractor of every tier must be enrolled in the wrap-up program before work begins. Enrollment is not automatic. The wrap-up administrator reviews and processes each application separately. A subcontractor that starts site work before receiving written enrollment confirmation from the administrator is not covered under the program.

The GC's obligation is to submit a Notice of Contract Award form to the administrator for each lower-tier contractor prior to their mobilization. The administrator then processes the enrollment and issues written confirmation. That confirmation document — not a verbal assurance that the application is "in process" — is what the audit requires to confirm enrollment was in place when work started.

Second- and third-tier subcontractors are the most common coverage gap in wrap-up programs. Most GC contract management systems track direct sub enrollment. The subs of your subs are where enrollment falls through. If a tier-two contractor started site work without enrollment confirmation, the work they performed is uninsured under the program, and that exposure falls to the GC.

Red flag: A subcontractor that mobilizes while the administrator says their enrollment is "pending" is creating a coverage gap in real time. The confirmation letter is what matters — not the application date, not the administrator's phone assurance.

Action: Build a pre-mobilization gate: Notice of Contract Award submitted to the administrator, written enrollment confirmation received, copy filed in the sub's record. No subcontractor or lower-tier contractor touches the site before those three steps are complete. At audit, the administrator will check the enrollment timeline against site-start dates — a sub who mobilized before confirmation is an audit finding regardless of whether they were subsequently enrolled.

Not every contractor on a wrap-up project is enrolled. Certain trades are routinely excluded: hazardous materials abatement and demolition contractors, as well as subcontractors with elevated loss histories. Excluded contractors are still on your site. They must maintain their own commercial general liability and workers' compensation coverage for the duration of their work — and the GC must have their certificates of insurance on file.

The wrap-up administrator requires COIs for excluded contractors to verify that non-wrap-up coverage exists while those contractors are on-site. This is separate from the endorsement requirements that apply to enrolled subs' external policies. Excluded subs bring their full independent insurance program; an ACORD 25 certificate plus evidence of workers' compensation coverage is the audit check.

At audit, the administrator reconciles enrolled subs against enrollment confirmations and excluded subs against their COIs. If you can't produce either document for a contractor who was on-site, that contractor's work is an unresolved finding.

Red flag: An excluded subcontractor whose certificate expired mid-project while they were still on-site. Certificate expiration dates frequently fall during project execution, and tracking renewals for excluded subs gets dropped when the project team's attention is on active work.

Action: Maintain a running log of excluded subcontractors with certificate expiration dates alongside your enrolled sub records. Request certificate renewals before they lapse, and verify continued on-site work does not extend past the certificate period. Treat excluded sub COIs as a live compliance item throughout the project, not a one-time collection at contract signing.

The insurance credit in your contract was calculated at bid time from estimated payroll. The true-up at project close reconciles that estimate against the actual payroll reported under the program. If actual payroll exceeded the estimate, the difference produces additional premium. If actual payroll came in lower, the sponsor owes you a credit adjustment. Some programs specify how the final credit is calculated in the CIP addendum — verify that mechanism is there before signing.

Change orders are the main driver of true-up exposure. The original insurance credit calculation does not automatically update when a change order is executed. A change order that adds three months of schedule and significant additional labor expands the on-site payroll base — but unless the GC notifies the wrap-up administrator, the program's payroll estimate stays fixed at bid time. The gap between the original estimate and actual payroll is the GC's liability at closeout.

Red flag: A CIP addendum that specifies an insurance credit at contract award but doesn't describe how the credit adjusts at project close. If the addendum has no true-up provision, you may be undercompensated for insurance exposure that exceeded the bid-time estimate — or have no mechanism to recover the surplus if actual payroll came in below estimate.

Action: Before signing the CIP addendum, verify that a true-up provision is specified. When change orders add on-site labor, quantify the payroll impact and notify the wrap-up administrator. Track cumulative change order payroll separately from base contract payroll so the final credit calculation can be verified against your own records.

The most consistent audit error GCs make on wrap-up programs has nothing to do with the wrap-up program itself — it happens at their own year-end workers' compensation audit. If the GC fails to exclude OCIP-covered payroll from their regular WC policy, they pay WC premium twice on the same payroll: once under the wrap-up program, and again under their own policy. The OCIP or CCIP covers on-site workers' compensation for enrolled contractors. Including that same payroll in the company's regular year-end WC audit generates duplicate premium.

Preventing this requires two steps. First, obtain wrap-up certificates of insurance for each project covered under an OCIP or CCIP — the wrap-up administrator provides these to enrolled contractors. Second, present those COIs to your regular WC carrier at the annual audit and explicitly exclude the covered on-site payroll from the audited premium base. If you don't have the wrap-up COIs filed separately, your regular carrier has no mechanism to apply the exclusion and will charge premium on the full payroll.

The wrap-up COIs belong in your regular policy file — not just the project file. A COI stored only in the project's document folder doesn't surface during the year-end WC audit unless someone specifically retrieves it.

Red flag: A year-end WC audit where total payroll includes on-site hours for an OCIP or CCIP project with no exclusion applied. If you've had multiple wrap-up projects in recent years, pull your WC audit history and check whether covered payroll was excluded from the premium base each year. Retroactive corrections are possible but require documentation that not all carriers accept.

Action: Request wrap-up COIs from the administrator at enrollment — not just at closeout — and file them in your regular WC policy records. Before each year-end WC audit, compile a list of OCIP/CCIP projects active in the audit period, pull the wrap-up COIs, and present them to your WC auditor as explicit exclusions from the base payroll. Confirm in writing that the exclusion was applied.

IRMI — Traditional versus Project Insurance — OCIP/CCIP sponsor roles, premium structure, monthly payroll reporting requirement, accessed June 24, 2026.

IRMI — Best Practices for Participating in a Wrap-Up — enrollment best practices, subcontractor documentation, true-up provision, accessed June 24, 2026.

IRMI — Wrap-Up Insurance Credit Methodologies — insurance credit true-up methodologies, payroll definition, credit adjustment at project close, accessed June 24, 2026.

IRMI — Contemplating a CIP, Part Two — OCIP vs. CCIP sponsor distinctions, WC class code allocation by trade, accessed June 24, 2026.

CR Solutions — Wrap-Up Insurance FAQ — audit triggers, payroll reporting requirements, excluded contractor COI obligations, duplicate-premium trap, accessed June 24, 2026.

CR Solutions — Wrap-Up Basics for Contractors — enrollment confirmation requirement, Notice of Contract Award, class code allocation, final audit reconciliation, accessed June 24, 2026.

CR Solutions — OCIPs vs. CCIPs — GC control under CCIP, sponsor and program management distinctions, accessed June 24, 2026.