Threshold/Articles/Property Management
Property Management · June 2026 · 10 min read

Where Portfolio Liability Actually Concentrates

Across a multi-property STR operation, liability isn't distributed evenly by property count. It concentrates in specific places, and most operators couldn't point to where those places are in their own portfolio.

The intuitive mental model for portfolio liability goes something like this: more properties means more exposure. Two properties is twice the risk of one. Eight properties is eight times. You manage more by spreading coverage across the portfolio and making sure the aggregate limit is high enough.

This model is wrong in a specific and consequential way. Portfolio liability doesn't distribute evenly across property count. It concentrates, in specific amenity profiles, in specific booking segments, in specific regulatory environments, and in structural features of how multi-property coverage is written that most operators have never looked at carefully. The aggregate limit may be the right size. The question is whether it's actually protecting the right things.

For operators who own multiple properties, the relevant question isn't "how much liability do I have across the portfolio." It's "where in the portfolio does my tail risk actually live", because the answer is almost never "evenly distributed," and knowing where the concentration is changes every other coverage decision that follows.

The Proportionality Assumption

When operators think about scaling up from one property to five or ten, they tend to think proportionally. Five times the properties means five times the chances of something going wrong. The solution seems obvious: bigger limits, higher aggregate, and proportionally more premium.

What this framing misses is that STR liability claims don't follow an even distribution across properties. They cluster around specific features, high-severity amenities, specific booking types, regulatory non-compliance conditions, that may exist at two properties in a portfolio of twelve and generate a disproportionate share of the portfolio's total tail risk. An operator who owns twelve properties, two of which have pools and one of which has a waterfront dock, doesn't have roughly equal exposure at all twelve properties. The pool and waterfront properties carry a severity ceiling that the remaining nine don't, and the aggregate exposure of the portfolio is driven significantly by that subset.

The practical implication is that portfolio risk management isn't fundamentally about scaling what you do for a single property by the number of properties. It's about identifying where the concentration points are and making sure the coverage structure, maintenance protocols, and documentation practices address those specific points rather than treating all properties as interchangeable units of exposure.

Concentration by Amenity Profile

The most direct form of portfolio concentration is amenity-driven severity variance, the fact that specific features produce meaningfully higher claim ceilings than the baseline premises liability exposure of a property without them.

Throughout Threshold STR's incident report series, the recurring pattern is that the highest-severity claims attach to specific amenities: pools and water features (Incident №004), hot tubs (Incident №001), trampolines (Incident №010), elevated decks, exterior staircases without adequate lighting (Incident №011). None of these incidents occurred because the operator had a large portfolio, they occurred because a specific property had a specific feature with a specific severity profile. But for a portfolio operator, the distribution of those features across the portfolio determines where the severity ceiling actually lives.

An operator managing eight properties who has never done a formal amenity audit, a property-by-property inventory of every feature that carries an elevated severity ceiling or a potential coverage exclusion, is operating without a map of their own portfolio's risk concentration. This audit is not complicated: for each property, identify every amenity with an above-baseline liability profile, note whether that amenity is explicitly covered or excluded under the current policy structure, and note whether it's in compliance with applicable code requirements. What emerges from that exercise is a picture of where the portfolio's tail risk actually lives, which is almost never spread evenly across the property count.

For property managers specifically, those managing other owners' assets rather than their own, the amenity audit serves an additional function. The management company's professional liability doesn't disappear just because the property is owned by someone else. If a guest is injured at a managed property by a condition that a competent property manager should have identified and addressed, the management company is potentially exposed alongside the property owner. Knowing which properties in a managed portfolio have high-severity amenity profiles is part of the professional standard of care, not just an operational nicety.

Concentration by Booking Segment

The second concentration point is less visible but equally consequential: the type of guest experience a property is marketed toward correlates meaningfully with claim frequency and severity.

A property positioned for couples' getaways carries a different risk profile than one marketed for large family reunions. A property that books bachelor and bachelorette parties, or that describes itself as a "party house" in any form, carries a different profile still. The number of guests, their age distribution, the occasion they're celebrating, and the presence of alcohol-oriented amenities all shape the probability distribution of what incidents look like at that property.

This doesn't mean operators should avoid these booking segments, it means the coverage structure and the operational protocols should reflect the actual risk profile of the bookings the property attracts, not a generic single-property baseline. A portfolio operator who has one property explicitly positioned for large-group family bookings (multi-generational reunions, extended family stays) and another marketed to couples should not be treating those properties as equivalent units of liability exposure, because they aren't.

The connection between booking segment and amenity profile is also direct: properties marketed to families with children are more likely to have the amenities children will use, pools, trampolines, elevated play structures, which are also the amenities with the highest pediatric injury severity ceilings. The combination of a high-severity amenity and the booking segment most likely to have unsupervised children using it simultaneously is a specific, identifiable concentration point that a portfolio-level view makes visible in a way that single-property analysis might not.

The Aggregate Limit Trap

Portfolio coverage structure introduces a specific mechanical risk that doesn't exist for single-property operators: the shared aggregate limit. This is the point where the standard advice to "make sure your aggregate limit is large enough" breaks down as a complete answer, because the question isn't only whether the aggregate is sized correctly, it's how the aggregate behaves when one property has a large claim.

A portfolio policy covering eight properties might carry a $3 million aggregate liability limit across the portfolio for the policy year. If a severe claim at one property consumes $900,000 of that aggregate, settlement, defense costs, and associated expenses, the remaining seven properties now operate with $2.1 million in aggregate coverage for the balance of the policy year. They didn't have an incident. Nothing changed at those properties. But the shared aggregate is now drawn down, and if another severe claim occurs at a different property before renewal, it's working against a meaningfully smaller pool.

The standard in more sophisticated portfolio structures is per-location aggregate limits, each property has its own aggregate that operates independently of what happens at other properties. Per-location aggregates cost more in premium than a shared aggregate at the same total number, but they eliminate the correlated drawdown problem. For a portfolio where the properties carry meaningful independence from each other, different markets, different amenity profiles, different booking segments, per-location aggregates are worth evaluating explicitly, rather than accepting the shared aggregate as the default structure without understanding its implications.

The aggregate structure question also connects to how defense costs are treated. As discussed in Threshold STR's piece on liability limits and umbrellas, some policies pay defense costs outside the aggregate limit, meaning defense costs don't draw down the coverage available for the settlement. Other policies include defense costs inside the limit. For a shared aggregate that might already face drawdown pressure from multiple simultaneous minor claims, defense costs inside the limit create a compounding effect that reduces available settlement coverage faster than the per-claim picture would suggest.

Geographic Concentration and Correlated Risk

A portfolio concentrated in a single market carries a risk type that a geographically diversified portfolio doesn't: correlated catastrophic exposure. When a wildfire moves through a mountain resort community, a hurricane makes landfall on a coastal market, or a regulatory change significantly affects STR operations in a specific municipality, properties concentrated in that market face that event simultaneously.

This is the insurance industry's language for a problem that's familiar to real estate investors in a different context: geographic concentration. A portfolio spread across five markets is diversified against the local catastrophic event in any one of them. A portfolio of ten properties in the same coastal resort market faces the same hurricane risk at all ten simultaneously, and if that hurricane produces the kind of widespread damage that triggers carrier non-renewals and insurance market exits (as documented in Incident №009 for wildfire-affected western markets), the entire portfolio faces the same coverage availability challenge at once.

For most smaller portfolio operators, full geographic diversification isn't realistic or even necessarily desirable, there are good operational reasons to concentrate properties in a market where you have local knowledge, vendor relationships, and management infrastructure. But awareness of the correlated risk that concentration creates, and the specific insurance market dynamics of each geographic concentration (coastal wind and flood exposure, wildland-urban interface fire exposure, flood zone distribution), is part of portfolio-level risk management that single-property analysis doesn't surface.

The Property Manager's Specific Position

For operators who manage properties owned by others, portfolio liability concentration analysis has a layer that owner-operators don't face: the management company's own professional liability is a distinct exposure from any individual property owner's coverage.

When a guest is injured at a managed property, the liability question involves both the property owner (who owns the physical asset and is the named insured under the property's coverage) and the property manager (who made decisions about how the property was operated, maintained, presented to guests, and staffed). In many claims, both parties are named. The management company's professional liability, its exposure for failures in the standard of care it owed as a property manager, is a separate insurance question from the property's premises liability policy, and it's one that many property management companies don't address with the same rigor they apply to individual property coverage.

Portfolio concentration analysis matters specifically for property managers because the management company's professional liability exposure doesn't distribute evenly across the managed portfolio any more than the premises liability exposure does. It concentrates at the properties where the management company's decisions and actions are most directly implicated in the risk profile, the high-severity amenity properties, the high-group-capacity properties, the ones with documented prior complaints or code compliance issues. A management company that has never conducted a systematic review of which properties in its managed portfolio present the highest professional liability exposure doesn't have a complete picture of its own risk concentration.

There's also a fair housing dimension specific to property managers with portfolio scale. A management company operating practices, how guest inquiries are handled, how properties are described in listings, how accommodation requests are processed, apply across the entire managed portfolio. A systematic practice that creates fair housing exposure at one property may create it across all of them, because the management company's conduct is the common thread. Incident Report №008 in Threshold STR's case file series documented a single fair housing violation involving a single property. A property management company whose practices replicate that vulnerability across twenty managed properties isn't facing twenty times that risk, it's facing a systemic practice question that's a different order of problem entirely.

Building a Portfolio Liability Map

A portfolio liability map isn't a complicated document. It's a property-by-property summary of the specific concentration factors that make each property a distinct unit of risk, not equivalent to each other, and not necessarily proportional to their revenue contribution or physical size.

For each property, the relevant variables are: the amenity profile and which amenities carry above-baseline severity ceilings or coverage exclusions; the primary booking segment and what that segment implies about incident profile; the regulatory environment including applicable code requirements for the property's specific features; the coverage structure for that property, what's covered, what's excluded, whether defense costs are inside or outside limits, and how that structure interacts with whatever shared aggregate or per-location aggregate the portfolio uses; and any documented prior complaints, maintenance issues, or prior claims that change the ordinary-versus-gross-negligence analysis at that property specifically.

What a liability map makes visible, when built across the full portfolio, is that two or three properties almost always account for a disproportionate share of the portfolio's total tail risk. Those are the properties that warrant the most rigorous review of their coverage structure, the most current amenity audit, the most complete documentation of maintenance practices and regulatory compliance, not because they're necessarily the most valuable properties in the portfolio, but because they're where the severe claims are most likely to originate and where the coverage structure needs to be most precisely calibrated.

Operational Lessons

Map the portfolio before sizing the coverage. The right aggregate limit and the right per-location structure depend on knowing where the concentration actually is. An aggregate that seems large enough relative to property count may be inadequate relative to the concentration of high-severity amenities and booking segments that drive actual tail risk. Do the amenity audit and the booking-segment analysis before the coverage conversation, not after.

Ask specifically about per-location versus shared aggregate, and understand the drawdown implications of the shared structure. Most portfolio policies default to shared aggregate structures that are cheaper in premium but create the correlated drawdown problem documented above. Whether per-location aggregates are worth the additional premium depends on the portfolio's specific concentration profile and the probability that two independent severe claims could occur in the same policy year, which is higher when the portfolio has multiple high-severity amenity properties than when it's uniformly low-severity.

For property managers, treat professional liability as a distinct coverage question from premises liability. The management company's professional liability doesn't ride on any individual property's policy. It requires its own coverage structure, one that reflects the management company's specific portfolio-level risk concentration, including the fair housing and operational practice dimensions that apply across all managed properties simultaneously rather than at one property at a time.

Identify the two or three properties in the portfolio that carry disproportionate tail risk and give them a different level of operational attention. This means more frequent inspections, more rigorous documentation, more current regulatory compliance review, and in some cases a specific conversation about whether the current coverage structure is adequate for that specific property's risk profile rather than appropriate for the portfolio average.

Consider geographic concentration as a portfolio-level risk, not just a diversification preference. The insurance market availability and pricing in specific geographic markets, coastal wind/flood markets, wildland-urban interface markets, high-regulatory STR markets, is a portfolio-level risk factor. Properties concentrated in a single geographic market face the same event simultaneously, and the insurance market response to that event (non-renewals, premium increases, coverage exits) affects all of them at once.

The Bottom Line

Portfolio liability is not proportional to property count, and managing it proportionally, more properties, more aggregate, proportionally more premium, isn't a substitute for knowing where in the portfolio the liability actually concentrates. The operator who has mapped their portfolio's concentration points and built their coverage structure around them is in a fundamentally different position than one who has sized coverage based on count alone, even if the total aggregate numbers are similar.

The mapping exercise is not complicated and it doesn't require outside expertise to initiate. It requires an honest property-by-property inventory of amenities, booking segments, code compliance status, and coverage structure, looked at across the whole portfolio rather than one property at a time. What that view reveals, almost universally, is that a small number of properties are driving most of the portfolio's tail risk, and that those properties deserve a level of coverage precision and operational attention that the proportional approach never quite delivers.

Schedule a portfolio-level audit with Threshold STR to walk through your specific concentration profile and coverage structure, or take the free five-minute Risk Score to see where your current setup stands.


This article is prepared by Threshold STR for educational and operational guidance purposes. It does not constitute insurance, legal, or financial advice. Coverage structures, aggregate limit treatment, and professional liability requirements vary by carrier, jurisdiction, and portfolio structure. Before making coverage decisions for a multi-property operation, consult with a licensed insurance professional experienced in commercial STR portfolio coverage.

Keep reading

Related articles.

Property Management

The Five Risks That Keep STR Property Managers Up at Night

The exposures that put a manager's whole book at risk, and the questions that surface them early.
Read article
Property Management

When an Owner's Insurance Mistake Becomes the Property Manager's Problem

How an owner's coverage gap travels up the chain, and what managers can require before it does.
Read article
Liability

Why Your Umbrella Policy May Not Cover Your Rental

The extra liability layer many owners rely on often excludes the exact claim a rental produces.
Read article