What is the difference between a sub-association and master-association insurance program?

Large master-planned developments are rarely governed by a single association. They are built as a layered structure: an umbrella master association that owns and governs the shared spine of the community, sitting above one or more sub-associations, each governing a distinct neighborhood, village, condominium, or product type inside the same development. Every owner belongs to a sub-association and, through it, to the master. The two layers have separate boards, separate budgets, separate governing documents, and separate insurance programs, and that separation is the entire reason the coverage question gets complicated.

The master association typically owns and maintains the things that serve the whole community: the entry roads and gates, the perimeter walls, the clubhouse and pools, the golf course or trail network, the retention ponds and drainage, the guardhouse, and the common landscaping along the arterial roads. A sub-association owns and maintains the things inside its own parcel: the buildings in a condominium village, the private streets and shared roofs of a townhome pod, or the amenity that serves only that neighborhood. The insurance program on each layer is scoped to what that layer actually owns, which is why you cannot answer a coverage question for the community without first knowing which layer holds the asset.

On the property side, the split usually tracks ownership cleanly. The master association carries property coverage on the structures it owns outright, the clubhouse, the maintenance building, the guardhouse, pump houses, and amenity structures, and it does not insure the buildings inside a sub-association. Each sub-association carries the master property policy on its own buildings and common elements, written to replacement cost on the same basis any standalone condominium or townhome association would use. The most common mistake is assuming the master's amenity policy somehow reaches down into the villages; it does not, and a village left uninsured because its board assumed the master 'has it covered' is a real and recurring failure.

On the liability side the picture is different, because liability follows activity and control, not just title. The master association's general liability responds to injuries on the roads, at the pool, on the trails, and at the amenities it operates, while each sub-association's general liability responds to injuries on its own private drives, walkways, and neighborhood common areas. Problems cluster at the seams, a sidewalk that runs from a master road into a village, a pool shared by two sub-associations, a gate one layer maintains and another controls, where it is genuinely unclear which policy is primary. Those boundaries should be resolved in the governing documents and confirmed on the certificates before a claim forces the question.

The line between what the master insures and what a sub-association insures is set by the recorded declarations and the master governing instrument, not by whatever a certificate of insurance happens to say. The master declaration defines the common area it controls; each sub-association's declaration defines its own common elements and, critically, its valuation basis, bare walls, single entity, or all in, which governs how far its master property policy reaches into a unit interior. Two sub-associations inside the same development can carry different valuation bases, which means an owner's personal responsibility differs from one village to the next even under one master.

Read the insurance article of each layer's governing documents side by side before assuming the programs align. The master instrument usually states what the master must insure and often requires each sub-association to carry specified minimum limits and to name the master as an additional insured. When a sub-association quietly drops below those minimums, or lets its coverage lapse, the deficiency does not stay contained to that village; it can pull the master into a claim the master expected the sub-association's policy to absorb. Cross-checking the two document sets is the single most useful thing a manager can do on a layered account.

The hardest coordination problem in a layered community is the umbrella. An umbrella, or excess liability, policy sits above the primary general liability and, where scheduled, hired and non-owned auto and directors and officers coverage, adding a shared limit for a catastrophic claim. In a layered structure the question is whether the master and its sub-associations each buy their own umbrella, or whether a single master umbrella extends down over the sub-associations as named or additional insureds. Both structures exist, and each has a failure mode a board should understand before renewal.

When each layer buys its own umbrella, the advantage is that every association controls its own limit and no one layer's claim erodes another's protection; the risk is gaps and inconsistency, one village carrying a thin limit that does not match the master's, or an underlying schedule that omits a policy so the umbrella never drops down. When a single umbrella is written to span the whole development, the advantage is a consistent, often higher shared limit bought more efficiently; the risk is aggregation, a single severe claim in one village can consume limit that every other layer was also relying on, leaving the rest of the community exposed for the remainder of the policy term. Because excess capacity is priced per layer and costs far less per dollar than raising each primary policy, communities frequently carry meaningful excess limits, commonly in the $5M to $25M range and higher for large high-rise or amenity-heavy developments, but the number on the declarations page means nothing until you confirm which associations it actually protects and over which underlying policies it follows form.

Whichever structure a community uses, the umbrella schedule of underlying insurance has to list the correct primary policies on the correct layer. An umbrella only drops down over policies actually named on its schedule, so a master umbrella that is supposed to extend to a sub-association but does not list that sub-association's general liability is a hole in the tower even when the headline limit looks generous.

Beyond limits, the two layers have to be wired together with the right endorsements. The master governing documents typically require each sub-association to name the master association as an additional insured on its general liability, so that a claim arising in a village, but pulling in the master, is defended and paid by the village's carrier rather than the master's. Reciprocal additional-insured status and a waiver of subrogation between the layers keep the two carriers from litigating against each other after a shared-boundary loss. These are cheap endorsements that are worthless if no one confirms they were actually issued.

The practical control is a disciplined certificate flow. The master's manager should collect a current certificate of insurance from every sub-association each year, confirm the limits meet the master declaration's minimums, and confirm the additional-insured and waiver language is present, while each sub-association should do the same in reverse for any amenity or road it shares control of with the master. On a large layered account this reconciliation is annual work, not a one-time setup, because any single sub-association changing carriers or dropping a limit can quietly break the coordination the whole structure depends on.