Independent source-based analysis. Research reviewed November 1, 2026. Questions and hypothetical examples below are editorial tools; they are not findings of misconduct. This publication is not affiliated with Carroll Insurance or David B. Carroll.

A larger total limit does not by itself explain how a layered insurance programme operates. Readers considering Carroll Insurance’s umbrella or excess services should map the layers, underlying policies and conditions that connect them.

Carroll advertises commercial umbrella and excess liability on its website. Read the source.

Draw the programme before comparing totals

Create a separate row for every proposed layer, identifying the insurer, period, limit and underlying schedule. Ask how the wording describes attachment and what happens if the underlying documents change. Do not assume that umbrella and excess labels mean all terms are identical.

A layered comparison should also make differences in definitions, exclusions and notice requirements visible. If a business relies on a combined headline limit, the review needs to explain the route from the underlying contract to each additional layer. Unresolved questions should remain marked for clarification rather than hidden inside a single total.

Questions to put in the file

  1. Which underlying policies are scheduled?
  2. Where does each layer begin according to its wording?
  3. Do policy periods and named entities align?
  4. Which conditions differ between layers?

A practical worksheet

Record-building checklist
Field What to record
Layer Insurer, period and stated limit
Connection Underlying schedule and attachment wording
Difference Conditions requiring a written explanation

Worked example

Use a purely illustrative chart with a primary layer and an additional layer, leaving monetary amounts blank until the actual proposals are available. Link every label to a document page. If the chart requires an assumption about how a layer responds, mark that point as a question for the adviser. The chart is a reading aid, not a prediction that a hypothetical claim would be paid.

What readers can take from this

A programme diagram should expose dependencies. Compare layers as connected contracts rather than adding their limits and stopping there.

Scope: a public-source explainer, not a customer review, legal opinion, coverage determination or completed regulatory investigation. Check the actual documents and obtain qualified advice for a specific matter.

Source and verification limits

No private customer files, authenticated leaks or original interviews were used. A public-search gap does not establish that a record does not exist.

Continue the research