A second liability layer is often assumed to enlarge everything beneath it. It does not. It sits above the coverage that answers for harm your work does to others, and it has nothing to say about a machine of yours that burned, rolled or disappeared. That asymmetry decides who actually needs one.
An umbrella sits over liability, and a damaged machine is not liability
Start with the split that governs the whole subject. Your program answers two unrelated questions. What happens when a machine of yours is harmed, and what happens when your work harms somebody else.
The first question is answered by the equipment schedule and its own limits, inside the equipment floater. It is first-party property coverage, and if the limit there is too small the remedy is a larger limit on the schedule.
The second question is answered by general liability and the other liability parts, and it is the only half a second layer sits above. An owner who buys a layer because a large machine feels underinsured has bought protection against a completely different event. The purchase is not wasted — it is simply unrelated to the concern that prompted it.
The schedule of underlying insurance is the design
The most consequential page in an excess or umbrella policy is the list of what sits beneath it. That schedule names each underlying policy and the limit assumed to be in place, and a claim reaching the layer is tested against it.
Contractors typically schedule three: general liability, commercial auto, and the employers liability portion of workers compensation. What gets scheduled determines what can be reached. A liability exposure that lives in a policy nobody listed does not reach the layer above simply because both documents are yours.
This is worth reading rather than trusting, and the failure is mundane. A policy gets moved, a limit changes at renewal, a coverage is added mid-year and the schedule above it is never updated. Everything looks intact until the year a claim needs the arrangement to be accurate.
Umbrella and excess are two different instruments
The words get used interchangeably and the documents behave differently.
An excess policy generally follows the form beneath it. Its terms are the underlying terms, its exclusions are the underlying exclusions, and its job is purely vertical: when the limit below is exhausted, it continues on the same basis. Predictable, and no broader than what it sits on.
An umbrella can carry its own form. That sometimes makes it wider than the coverage below — reaching an exposure the primary policy did not address — and it also means the umbrella’s own form brings exclusions the primary did not have. Wider is not automatically better, because the terms that govern once the layer is paying may not be the terms you read when you bought the primary.
The practical instruction is the same either way: find out which one you have, and read what governs at the point where the layer starts paying. That question has a definite answer and it is rarely in the summary.
The attachment point and the duty to keep the layer beneath intact
A second layer starts where the underlying limit ends, and that point is a number the layer relies on rather than one it controls.
Two conditions follow. First, the underlying limit has to actually be the limit the schedule assumed. Buy a layer above a stated limit and then reduce the primary at renewal, and the gap between them belongs to you. Second, many forms expect the underlying limit to be maintained during the year, which means claim payments that erode it can leave you responsible for the eroded portion rather than the layer dropping down to fill it.
Some forms do drop down in defined circumstances, and some do not. That is another item on the short list of things worth confirming in writing while nothing is happening.
The claims that actually reach a second layer
In equipment work the claims that get there share a shape: one incident with consequences that spread well beyond the site.
A buried utility opened during excavation, where the loss is not the pipe but the outage and everything downstream of it. A fire that starts on a site and does not stay there. An injury to somebody with no connection to your payroll, in a jurisdiction where that gets litigated hard. A vehicle at fault carrying a machine on a public road, where the auto limit is exhausted by the other side of the collision alone.
Real-World Scenario: A crew running a tracked machine on a tight downtown lot clips a service line that was not where the markings said it was. The machine itself needs a hose and a half day of work. What follows has nothing to do with the machine: a full block loses service through the afternoon and into the following morning, businesses along it close early, and the claims that arrive over the following months are for business those firms lost rather than for anything the contractor owns. The equipment side of the file closes in a week. The liability side runs past the primary limit, and the only question that matters by then is whether there was a layer above it.
Notice what is common to all of these. The machine is barely involved. The exposure is what the work did, not what the work was done with, and that is exactly the half a layer sits over.
Where a contract sets the number for you
Most contractors do not choose a limit analytically. They buy what a contract requires, and that is a defensible way to arrive at a number as long as somebody reads the requirement rather than the summary of it.
The contract’s insurance exhibit will typically state a required limit, whether a layered structure is acceptable, and which statuses have to flow through to the layer. That last item is where arrangements come apart: a contract requiring additional insured status upstream generally expects that status to reach the excess layer too, and the mechanics of that are worth confirming rather than assuming. The same reading applies to whichever party asked to be named at all, which is the ground additional insured and loss payee status works through in detail.
Requirements also escalate quietly. Public agency work, work near rail, work inside an occupied building and work as a subcontractor to a large general contractor all tend to ask for more than private residential work does. A firm moving into any of those is a firm whose limit question has changed.
What a layer does not fix
It does not enlarge the equipment schedule. It does not repair a stale schedule of values, cure a category ceiling, or reduce a retention — the mechanisms worked through in deductibles, coinsurance and sublimits all sit below it and are untouched by it.
It does not reach an exposure the underlying policies excluded, at least not in the following-form case, and not reliably in the other. Buying height above a coverage gap does not close the gap; it just puts more limit above the same hole.
And it does not substitute for the primary limits being sensible. A very small primary limit under a large layer is an uncomfortable structure, because the layer is reached constantly and the arrangement starts behaving like a policy with an enormous retention. Layers work best above a primary limit that is already appropriate for the work.
Sizing it before somebody else does
The useful exercise is not a formula. It is a question: what is the worst single thing a machine of ours could do on the kind of site we work now, and would the primary limit absorb it. Firms whose sites have moved closer to occupied buildings, buried services and public traffic have usually answered that question in the affirmative without noticing.
Read the exhibit on the next contract, read the schedule of underlying insurance against the policies you actually carry, and ask what governs once the layer is paying. Then send the contract and the machine list through the quote form and we will structure the layer against the work rather than against a round number. The umbrella page sets out how we place the layer, the equipment lineup shows the machine classes behind it, and if the machines in question are not yours, rented, leased or borrowed coverage takes that case apart separately.