Wrap-ups are one of the more misunderstood things in construction insurance, mostly because the name suggests they wrap up everything. They do not. A wrap-up is a single insurance program that generally covers the enrolled parties on one specific project, and it is a useful structure on large jobs. The trouble starts when a contractor treats enrollment as permission to stop thinking about their own coverage. The wrap has edges, and your business lives well beyond them.
What a wrap actually is
The two you will hear most are the OCIP, an owner-controlled insurance program, and the CCIP, a contractor-controlled one. The difference is who sponsors and controls the program, but the idea is the same. Instead of every contractor and sub carrying their own separate coverage for the project, one program provides certain coverage for the enrolled parties on that project. It can simplify a big job and align everyone’s insurance under one set of terms. For the covered work, on the covered site, it does real work.
What the wrap generally does not do
Here is where contractors get caught. A wrap is tied to a project. It generally covers on-site work for that specific job, for the enrolled parties, subject to the program’s terms. It usually does not cover your work off the project site, your other jobs running at the same time, or exposures the program excludes. If you fabricate or stage materials off site, run a second project across town, or have any operations outside the wrapped job, those generally still lean on your own policy. A wrap is a project solution, not a company solution.
The off-site and other-project gaps
Two gaps show up most. The first is off-site work. Fabrication, staging, and prep that happen away from the covered site can fall outside the wrap even though they support the wrapped project. The second is your other operations. The wrap does nothing for the jobs you run outside it, and if you let your own general liability limits go thin because you assumed the wrap had you covered, those other jobs can be underinsured. This is the same failure mode we describe in why contractor GL claims get denied, where the work at issue simply was not what the policy in play was built for.
The products-completed question
The quietest gap is what happens after the work is done. Claims tied to completed work can surface long after a project closes, and wrap programs handle completed operations differently. The coverage can be time-limited, and the program may not follow the work indefinitely. Because this is where some of the most serious construction claims live, it is worth confirming in writing how the wrap treats completed operations, and what your own policy carries once the wrap winds down. Our overview of contractor general liability exclusions covers how completed-work coverage behaves more broadly.
Reading the two together
The point is not that wraps are bad. They are common and useful on the projects that use them. The point is that a wrap and your own policy have to be read together, so you can see which exposures the wrap handles and which still ride on your own coverage. Done right, they interlock. Done carelessly, a contractor can end up with a project that is well covered and a business that is not.
Questions to ask your advisor
- What exactly does this wrap cover, and for which parties?
- Does the wrap reach my off-site fabrication and staging?
- How are my other, non-wrapped jobs covered while this runs?
- How does the wrap handle completed operations, and for how long?
- Should I keep my own limits in place rather than letting them drop?
A wrap-up can be a clean way to insure a big project, but it is a project tool with defined edges. Off the site, on your other work, and after the job is complete, your own policy generally still has a job to do. Reading the wrap against your own coverage is what keeps enrollment from quietly opening gaps you did not know you had.
Want guidance first? Compare your coverage. Already know what you need? Get a quote.