Umbrella insurance is excess liability that sits over underlying P&C policies. Carriers, MGAs, and TPAs running umbrella programs need a platform that validates underlying limits cleanly at every touch.
Personal umbrella insurance is excess liability coverage that sits on top of underlying P&C policies — home, auto, and other P&C — and pays after the underlying limits are exhausted. For carriers and MGAs, umbrella is a profitable personal-lines product that requires strict underlying-limit validation at quote, bind, endorsement, and renewal.
This page is a line-of-business reference for umbrella carriers, MGAs, TPAs, and program administrators evaluating a policy administration platform for their umbrella book.
An umbrella policy pays when an underlying liability claim exceeds the underlying policy's limit. A claim on the insured's auto policy that exceeds the auto BI limit reaches into the umbrella for the excess; a homeowners liability claim works the same way.
For the platform, that mechanic means the umbrella product has to validate the underlying policies' limits every time the umbrella is quoted, bound, endorsed, or renewed — and every time an underlying policy is endorsed or non-renewed.
Carriers require specific underlying limits (for example, $300,000 on homeowners Coverage E; $250/500/100 or $300 CSL on auto) as a condition of umbrella issuance. If an underlying policy drops below the threshold, the umbrella is exposed.
Mercury's configurable underwriting workflow and field-level validation enforce underlying-limit checks at quote, bind, endorsement, and renewal, and can raise workflow alerts when an underlying endorsement compromises the umbrella's validity.
Umbrella rating is driven by the number and type of underlying exposures (vehicles, drivers, homes, rental properties, watercraft), risk features (pool, trampoline, dogs, teen drivers), household characteristics, and loss history across all underlying policies.
The rating engine has to pull underlying data, apply risk-feature factors, and check declinable exposures through configurable underwriting rules. Mercury supports date-driven rating tables and configurable underwriting rules at this level of granularity.
The hardest problem in umbrella administration is cross-policy integrity: when a change on an auto or home policy silently compromises the umbrella's eligibility. Limit reductions, driver removals below a required minimum, or vehicle additions above a declinable class all need to surface to the umbrella workflow.
Mercury's API-first architecture and configurable underwriting rules let underlying-policy events raise workflow alerts on the umbrella record, so exposed umbrellas get reviewed rather than silently drifting out of compliance.
Does Mercury enforce umbrella underlying-limit requirements?
Yes. Mercury's configurable underwriting rules and field-level validation enforce underlying-limit checks at quote, bind, endorsement, and renewal, and can raise workflow alerts when an underlying endorsement would compromise the umbrella.
Can Mercury run umbrella on the same tenant as the underlying policies?
Yes. Running umbrella on the same policy administration tenant as the underlying home and auto is the cleanest configuration, because cross-policy events can raise alerts directly on the umbrella record without external integration.
Does Mercury support excess and surplus lines variants of umbrella?
Mercury's configurable rating, forms library, and multi-carrier MGA quoting support personal umbrella programs and excess liability variants. Specific lines, forms, and filings are driven by product configuration.
