Somewhere in the last stretch of contracts, somebody asked you for more total limit than your program carried. A general contractor, a property manager, a program agreement — the requirement arrived, you called your broker, and a layer went on top. The paperwork came back showing the amount they wanted, the demand stopped, and the job started.
That layer is real and it is doing real work. But a liability program is not one policy that grew taller. It is a stack of separate contracts, and the one on top has its own opinion about what sits beneath it. The excess liability page owns the architecture — how a layer attaches, what an underlying schedule is, why the tower has to stay continuous. What follows is narrower and, for a restoration operator, more useful: what your height is actually standing on, and how a tower can be genuinely tall and still have a hole at exactly the place your trade lives.
The contract asked for a number, and you met it
Nobody buys excess out of curiosity. It enters the conversation because a piece of paper demanded it — a total limit the primary program cannot show on its own, on a reconstruction or a commercial job you wanted.
So look closely at what that demand asked. It named an amount. It probably named the general liability it had to sit over, because general liability is the line every contract knows how to ask about. And then it stopped. The requirement had no view about the mold behind a wall, no view about the sewage in a Category 3 loss, no view about the contaminated material that leaves the site on your truck. It was not being careless. It was a general contractor protecting a general contractor, and it asked the only question it needed answered.
You met it. The layer satisfies the requirement precisely. The thing worth noticing is that the transaction which created your entire tower asked exactly one question — how high — and never asked the second one. Over what.
Height is not the same as reach
Here is the part that collapses in most people’s heads into a single idea.
An excess layer does not float above your program in general. It attaches over specific named underlying policies and rises from the top of what it names. A line that is not on that list is not a line the layer sits above — not because the insurer is being difficult, but because the layer was never built there. There is no quiet default that sweeps in the rest of your program.
So the height you bought has two dimensions, and only one of them is on the paperwork. The amount answers how high. Nothing but the wording answers over what. An operator reading a total limit and feeling covered is reading an honest answer to a question they did not mean to ask.
Your ground floor is not one room
Stop picturing a stack and picture a building.
The ground floor of a restoration program is not a single slab. It is several rooms, each with its own contract and its own wording. General liability answers the harm your crew causes third parties and their property. Commercial auto answers the response fleet out on the road. Contractors pollution liability answers the substance you were hired to remove — the line that exists because general liability carves that substance out. Professional liability answers a judgment you were paid to render. Separate rooms. Separate forms.
Which reframes the whole purchase. When you buy height, you are not buying height over the building. You are buying height over the rooms the layer names. The silhouette of a real program is uneven — tall over some rooms, flat over others — and the shape of it was decided by a contract requirement rather than by anything about your work.
What “follows form” is actually promising
The mechanism that is supposed to hold this together is follow-form: the layer adopts the terms of the policy it sits over, so the excess answers the way the primary does. It is a real promise and it is the reason excess is a sensible thing to buy at all.
What it is not is a switch. Follow-form is a promise whose scope varies, and it varies in both directions. A layer can follow the general liability form beneath it faithfully and still carry exclusions of its own. It can name a specialized contractors pollution policy as underlying and still substitute its own terms for that policy’s wording. Some layers follow broadly; some follow narrowly; the phrase appears on all of them.
Which means there is no honest general claim available here, and you should be suspicious of anyone who offers you one in either direction. Nobody can tell you what your excess follows without reading your excess. The only thing that settles the question is the wording actually attached to your program.
Real-World Scenario: A restoration company carries general liability, commercial auto, contractors pollution liability, and an excess layer added to satisfy a limit requirement on a large commercial reconstruction. Long after that job closes, a mold claim arrives from a different loss entirely. The pollution policy responds — it is the line written for exactly this — and the claim is serious enough to run through its limit. The company turns to the excess layer, which has been sitting on the program the whole time at a total limit everybody has been quoting on certificates. The layer’s schedule of underlying insurance names the general liability and the commercial auto. The pollution policy is not on it. Nothing was mis-sold and nothing was hidden: the layer was bought to answer a contract that specified general liability limits, and it does that exactly. The height was real. It was over the other rooms.
The policy that only performs on your worst day
Every other line on your program gets rehearsed. General liability answers the small third-party claims. Auto answers the parking-lot damage. The equipment coverage answers a stolen air mover. You learn what those policies do because they keep doing it.
The excess layer is built specifically not to be touched. It attaches above a primary limit and stays silent until a covered loss exhausts what is beneath it — which is the design functioning correctly, not a signal about the wording. Renewal after renewal goes by, the layer never says anything, and the silence starts to feel like confirmation.
It is not confirmation. It is the absence of a test. And this line differs from every other one in a way that ought to bother you slightly: the first time it is ever asked to perform is, by definition, the largest loss your business has ever had. Everything else on the program has a track record. This one debuts on your worst day.
Nobody built this wrong
It is tempting to read all of this as a layer sold under false pretenses. It was not, and believing it was will cost you the time you could spend fixing it.
Excess adds limit, not coverage. That is the design, stated plainly, and it is why the line is worth what it costs — a layer that broadened coverage beyond the policies it sits over would not be an excess policy, it would be a primary policy wearing a costume and priced like something else entirely. The layer is affordable precisely because it inherits terms rather than inventing them. Inheritance is the product.
And the underwriter was not hiding. They wrote a layer over the lines they were asked to write over. The requirement that created your tower named general liability, so the layer named general liability. Everyone did their job.
The gap is not a trick. It is the honest consequence of a purchase made to answer a contract rather than to answer a risk — and once you see it that way, it stops being an argument and becomes a line item.
<rect x="18" y="48" width="322" height="196" rx="9" fill="#F1E5D6" stroke="#12703F"/>
<text x="179" y="82" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="14" font-weight="600" fill="#12703F">The excess layer adds height here</text>
<text x="179" y="116" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">It rises above the lines it names</text>
<text x="179" y="136" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">as underlying — usually the ones</text>
<text x="179" y="156" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">the contract asked you to carry.</text>
<text x="179" y="206" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Height you can see.</text>
<rect x="360" y="48" width="322" height="196" rx="9" fill="#ffffff" stroke="#12703F" stroke-dasharray="7 5"/>
<text x="521" y="82" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="14" font-weight="600" fill="#12703F">And above these rooms?</text>
<text x="521" y="116" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">Only if the layer names them —</text>
<text x="521" y="136" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">and follows the wording beneath.</text>
<text x="521" y="156" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#5A5048">That promise varies by policy.</text>
<text x="521" y="206" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Height you have to verify.</text>
<path d="M 90 264 L 90 248" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#twr-arrow)"/>
<path d="M 263 264 L 263 248" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#twr-arrow)"/>
<path d="M 436 264 L 436 248" fill="none" stroke="#12703F" stroke-width="2" stroke-dasharray="4 4"/>
<path d="M 609 264 L 609 248" fill="none" stroke="#12703F" stroke-width="2" stroke-dasharray="4 4"/>
<rect x="6" y="266" width="168" height="78" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="90" y="300" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">General liability</text>
<text x="90" y="322" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">third-party harm</text>
<rect x="179" y="266" width="168" height="78" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="263" y="300" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">Commercial auto</text>
<text x="263" y="322" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">the response fleet</text>
<rect x="352" y="266" width="168" height="78" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="436" y="300" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">Pollution liability</text>
<text x="436" y="322" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">what you remove</text>
<rect x="525" y="266" width="168" height="78" rx="8" fill="#ffffff" stroke="#DCC9B0"/>
<text x="609" y="300" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">Professional liability</text>
<text x="609" y="322" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">the judgment you sign</text>
<text x="522" y="362" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">Where a restoration trade actually lives</text>
<rect x="30" y="380" width="640" height="86" rx="10" fill="#C7683F" stroke="#12703F"/>
<text x="350" y="410" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="15" font-weight="600" fill="#1A1A1A">Excess adds limit, not coverage</text>
<text x="350" y="434" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" fill="#1A1A1A">A tower can be tall and still have a hole where your trade lives.</text>
<text x="350" y="454" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" fill="#1A1A1A">Read what the layer sits over, not how high it goes.</text>What to ask about the layer above
You do not need to become an underwriter to close this, and you should not go hunting for a clause. The useful move is to ask a short list of structural questions of somebody who reads restoration programs, on a day when nothing is on fire.
- Which of my policies are named as underlying on the excess layer — and is my contractors pollution liability one of them?
- Where the pollution and professional lines are named, does the layer follow their wording, or does it substitute terms of its own?
- Where does the layer attach on each underlying line, and does that match the limits I actually carry today?
- If a pollution claim runs through the primary limit, which policy answers next — and do I own it?
- When the next contract raises the requirement, does any of this change, or does the shape stay the same?
The first question does most of the work, because the schedule of underlying insurance is a list, and a list can simply be read. Quick, specific answers mean somebody built the tower deliberately. Vague answers are themselves the finding, and you have collected it on an ordinary afternoon rather than during the largest claim of your life.
Before the next contract asks for more
The layer above your program was bought to answer a question somebody else asked, and it answered it honestly. What it was never asked — because the general contractor had no reason to ask it, and the requirement had no vocabulary for it — is whether the height stands over the substance you were hired to take out of a building.
That is worth fixing while it is a line item rather than a loss. Read the schedule, read what the layer follows, and buy the shape of the tower on purpose instead of inheriting the shape a contract happened to specify.
We build restoration contractor programs from the ground floor up rather than from the total limit down. If you want your excess layer read against the rooms your crews actually work in, ask us for a quote.