Restoration is a business built around endings. The equipment comes out, the final walkthrough happens, somebody signs, the invoice goes in, the file closes. That rhythm is the whole shape of the work — you are called because something ended badly, and you are paid once you have finished ending it well. Everything in your operating life confirms that a job is a thing with a last day.
Your policy does not use that definition. The work is finished; the exposure is not. And the claim that tests the difference never arrives while you are on the job — it arrives long after, addressed to a company that has moved on, about a house that closed out perfectly cleanly.
This post is about that stretch of time. General liability is the line that answers it, and its coverage page owns the architecture: how the products-completed-operations hazard is built, how the triggers differ, how the aggregates work. What follows is narrower and, for most owners, more useful — why the ending feels so much like an ending, and why the question a late claim asks is not the one you have spent your whole career answering.
In this trade, the job ends twice
Most contractors get one ending per job. You get two, and both of them feel completely real.
The first is mitigation. The water is extracted, the structure is dried, the affected material is out, the readings say what they need to say, and the emergency is over. That is a genuine finish: the crisis is done, the customer can breathe again, and the gear goes back on the truck. It feels like an ending because the thing that made it urgent has stopped happening.
Then, on a great many jobs, the rebuild begins — and it ends too. Framing, drywall, flooring, trim, cabinets, paint, a final walkthrough, a punch list, a signature. Reconstruction is quieter work than the emergency that preceded it, but it is the part that stays. When the crew drives away this time, they leave behind a structure your business built, and it will still be standing there through every season that follows.
Two endings, both convincing, and neither is the ending your insurance program recognizes. The reconstruction is the part that can fail later — and later is a place the trade’s entire sense of closure has no word for.
The envelope about a job you no longer remember
Here is how it actually shows up, and it is almost boring, which is part of why it lands the way it does.
Something arrives. A letter, a call from a general contractor you worked under, a demand from a party you have never met. It concerns a rebuild your business finished long enough ago that you have to go looking for the file. The lead who ran it does not work there any more. The subs have changed. The photographs are in a folder somewhere, or they are not. And what is being alleged is that work your company completed — finished, signed off, paid for, closed — caused injury or damage after everybody had stopped thinking about it.
Real-World Scenario: A restoration company mitigates a water loss in a finished basement and then rebuilds it — framing, drywall, flooring, trim. The job passes its walkthrough, the customer is satisfied, the file closes, and the company moves on to the next call. Long afterward, something in that completed work is alleged to have failed, and the damage that follows is neither the original loss nor anything the crew did while it was there. It is the finished work, doing something it was not supposed to do, with nobody from the company anywhere near it. The claim is pointed at the business. What comes up first is not a question about the crew or the workmanship, and not even whether the policy covers finished work at all — that part is ordinary coverage. It is a question about calendars: when did the company finish, when did the damage occur, when was this reported, and which of those dates does the policy actually care about. None of that is answerable from the job file. It is answerable only from the policies, and from a stretch of program history nobody has looked at in years.
A tail makes no noise while it runs
The reason nobody sees this coming is structural. A completed-operations exposure produces no signal at the moment it is created.
On the day you finish a rebuild, the tail starts. Nothing happens. You are not notified. It does not appear on a renewal or on a certificate, and it does not affect the walkthrough or the payment. The exposure simply runs, quietly, in a building you no longer visit, doing nothing at all — which on the overwhelming majority of jobs it will do forever. Almost every tail your business has ever started has ended in nothing whatsoever, and that is exactly what makes them invisible.
So the mental filing works perfectly, for years. Job closed, file closed, done. Nothing ever contradicts it, because nothing happening is what a healthy tail looks like — and it is also precisely what an unhealthy one looks like, right up until the day it isn’t. The only difference between them is a piece of information you do not have yet.
The question is a date, not a fact
When a late claim does arrive, it asks a different kind of question than any you have spent your career answering.
Every other coverage conversation in your business is about whether. Is this covered. Is that carved out. Does the policy reach the substance you were hired to remove — that one is its own subject with its own line, and it runs through contractors pollution liability rather than here. A completed-operations claim about your finished construction usually gets past whether fairly quickly, because answering harm your completed work causes is what this part of the policy is built to do. That is standard coverage, not a fight.
Then it stops on when. And it stops there because there is not one date — there are several, and they can sit a long way apart.
There is the day you finished: the walkthrough, the last invoice, the day the work left your control. There is the day something actually went wrong in that finished work, and somebody was hurt or something was damaged. And there is the day you found out — the day a claim was made and reported to your insurer. On a job that fails well after the crew left, those can land in different policy periods, under different programs, possibly with different insurers. Only one of them decides, and which one depends entirely on how your form is written.
That is the whole shift. You are used to being asked what happened. Now you are being asked when — and the answer is not in your job file. It is in paperwork from a year you stopped thinking about a long time ago.
Which policy year is this claim?
Now the mechanics, briefly, because the general liability page takes them apart properly.
The standard commercial general liability form — typically the occurrence-based ISO form known as CG 00 01, though editions vary by insurer, and plenty of specialty programs are written on manuscript wording that departs from it — answers your finished work through what it calls the products-completed-operations hazard: a defined term reaching bodily injury and property damage arising out of your work after it is completed. On an occurrence form, the date that matters is the day the injury or damage happened. It does not matter when the claim finally surfaces; the policy in force when the damage occurred is the one that answers, even if that program ended long ago and you are with a different insurer now.
There is a claims-made counterpart — the CG 00 02 form — and it does something quite different. It looks at when the claim is made and reported rather than when the damage occurred, which makes it depend on the retroactive date and on unbroken coverage to reach work you did earlier. Move programs, let a gap open, set a retroactive date later than your work history begins, and jobs you have already delivered can be stranded in a way that has nothing to do with how well you did them.
The practical consequence is uncomfortable and worth sitting with. On a claim about finished work, the answer may depend less on the job than on the shape of your program history. Two contractors who built the same basement the same way can land in very different places based only on which structure they were on and whether they kept it. Which is why we renewed and we are covered are not the same sentence.
<text x="150" y="70" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">The day you finished</text>
<text x="150" y="92" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">Walkthrough, last invoice.</text>
<text x="350" y="70" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">The day it went wrong</text>
<text x="350" y="92" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">Damage in the finished work.</text>
<text x="550" y="70" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">The day you found out</text>
<text x="550" y="92" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">The claim is made and reported.</text>
<path d="M 150 106 L 150 138" fill="none" stroke="#12703F" stroke-width="1"/>
<path d="M 350 106 L 350 138" fill="none" stroke="#12703F" stroke-width="1"/>
<path d="M 550 106 L 550 138" fill="none" stroke="#12703F" stroke-width="1"/>
<path d="M 50 144 L 648 144" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#tail-arrow)"/>
<circle cx="150" cy="144" r="6" fill="#12703F"/>
<circle cx="350" cy="144" r="6" fill="#12703F"/>
<circle cx="550" cy="144" r="6" fill="#12703F"/>
<rect x="70" y="172" width="160" height="46" rx="8" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="150" y="200" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">One policy year.</text>
<rect x="270" y="172" width="160" height="46" rx="8" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="350" y="200" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">Possibly another.</text>
<rect x="470" y="172" width="160" height="46" rx="8" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="550" y="200" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">Possibly another insurer.</text>
<rect x="60" y="248" width="580" height="64" rx="10" fill="#C7683F" stroke="#12703F"/>
<text x="350" y="276" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="15" font-weight="600" fill="#1A1A1A">The claim does not ask what happened. It asks when.</text>
<text x="350" y="298" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" fill="#1A1A1A">And the form decides which of these moments it answers to.</text>
<text x="350" y="344" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">An occurrence form looks at the day the damage happened.</text>
<text x="350" y="368" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">A claims-made form looks at the day it was reported.</text>
<text x="350" y="398" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">Same job, same failure — and a different policy answers, or none does.</text>What the tail outlives
It is worth being blunt about what a long tail is actually longer than.
It outlives your memory of the job — you will be reconstructing it from a file rather than from your head. It outlives your crew: the people who did the work have moved on, and their knowledge went with them. It usually outlives the business relationship, so the customer, the general contractor, and the program that sent you the work may all be gone. And it can outlive your program. Insurers change, panels change, forms get rewritten, and businesses shop their coverage on a perfectly reasonable schedule. The finished work sits in that building through every one of those changes, indifferent to all of them.
That is what makes documentation on a rebuild worth more than it feels like on the day, and it is what makes continuity worth more than a small saving at renewal. The version of your business that has to answer for the work is not the version that did it.
Questions worth asking about work you already finished
These are not questions about your next job, and that is the strange part. You cannot improve a tail by working better from now on — the work is already done. The only variable left is what is still watching it.
- If a rebuild my company finished in an earlier period is alleged to have failed, which policy answers — the one I have now, or the one I had then?
- Is my general liability written on an occurrence basis or a claims-made basis? Do I know that without checking?
- If it is claims-made, where does the retroactive date sit, and does it reach back over the work I have already delivered?
- When I moved programs, did anything get stranded — is there a stretch of finished jobs no policy is looking at any more?
- Does the completed-work side of my policy carry its own aggregate, and is it doing its own job rather than sharing?
Ask them of somebody who reads this class. Quick answers mean the program was built with the tail in mind. Vague ones are the finding — and unlike most findings, this one concerns work you cannot go back and redo, which is exactly why you want it early rather than accurately.
The job you closed is still open somewhere
The final walkthrough is real. The signature is real. The file closing is real, and there is nothing wrong with the rhythm — a business that could not finish things could not do this work at all.
It is simply that finished is your word, and the policy keeps its own. Your completed work goes on standing in a building long after you have stopped thinking about it, and if it ever causes harm, the conversation opens with a calendar rather than with your craftsmanship. There is nothing broken in that. It is what completed operations is: the policy staying at the job considerably longer than you did — which is exactly what you want it to do, provided somebody has confirmed that it is the right policy and that it is still watching.
General liability is where that lives, and the coverage page is worth reading for how the tail is genuinely built. Then read your own: the form, the trigger, the retroactive date if there is one, and whether your program history has a hole in it. If a contract has ever pushed you into excess limits above the primary layer, whether that height follows your completed work is its own question worth asking out loud.
On a restoration program the tail is not the last thing we look at. The finished work already on your books is an exposure today, and it will still be one at your next renewal. Send us what you have, and we will read it against the jobs you have already delivered.