What Co-Hosted STR Insurance Costs
Co-hosted STRs introduce a third party to the coverage architecture: the co-host or property manager who operates the property on the owner's behalf. The relationship can take several forms — a percentage-based co-host using Airbnb's platform-level Co-Host program, a property management company under a written management agreement, a friend or family member operating informally — and each form changes how coverage attaches. The Insurance Information Institute's overview of peer-to-peer home rental frames the underlying STR coverage baseline; co-hosted operations add the agency-relationship layer on top. The coverage program a typical co-hosted STR owner needs runs across six lines:
- General Liability (with co-host as additional insured): Guest bodily injury and third-party property damage. The co-host or property manager is typically named as an additional insured on the owner's GL so the same policy responds to claims arising from the co-host's decisions and actions at the property. Typical limits $1,000,000 each occurrence / $2,000,000 aggregate. See General Liability for STR.
- Property / Dwelling: The structure. Coverage attaches to the owner regardless of who manages day-to-day operations, but the policy should disclose the co-host arrangement at bind so the carrier can rate the management model correctly. See Property / Dwelling coverage.
- Loss of Rents: Rental income during a covered loss. Documentation flows through whichever party (owner or co-host) holds the platform account and booking history. See Loss of Rents.
- Tenant Discrimination Liability: Fair-housing claims arising from booking decisions. Co-hosts make case-by-case booking decisions on the owner's behalf — and discrimination claims can name both parties. See Tenant Discrimination Liability.
- Umbrella / Excess: Higher liability limits over primary GL. Particularly important when the co-host arrangement increases claim severity (more decision-makers, more potential negligence paths). See Umbrella coverage.
- Cyber Liability: Booking-platform credentials shared between owner and co-host create cyber exposure beyond what a single-operator owner faces. Phishing tailored at co-hosts, credential leakage during transitions, and shared-dashboard compromises are routine. See Cyber Liability.
Premium varies by management agreement structure, co-host scope (booking only, booking + cleaning, full operations), and the specific platform-level classification. The Insurance Information Institute's commercial general liability overview covers the additional-insured mechanics that make co-host coverage work.
Co-Hosted STR Regulation by State
Co-hosted STR regulation overlaps with both vacation rental rules and property management licensing. Some states require professional property managers to hold a real estate license; others treat informal co-hosting more permissively. The four states where co-hosted STR operations are most common each have distinct frameworks.
- Florida: Property managers handling vacation rentals require a real estate broker's license under Florida statute, with limited exceptions for owner's-agent arrangements. Vacation rentals — including co-hosted properties — must register with the Florida DBPR. Co-host arrangements that cross the property-management line need licensure.
- California: Property management licensing is required for professionals; Airbnb's Co-Host program operates outside the property-management licensing framework in most cities, but operators should confirm with the California Department of Insurance and the California Bureau of Real Estate on the specific arrangement.
- Tennessee: Nashville's Type 1 / Type 2 framework treats co-hosted properties under the non-owner-occupied (Type 2) classification when the owner doesn't live at the property. The Tennessee Department of Commerce and Insurance regulates carrier appetite.
- Texas: No state-level STR registration; Austin and Houston have city-specific licensing that applies regardless of management model. The Texas Department of Insurance regulates rate filings.
Whether the co-host needs property-management licensure depends on the scope of the relationship and the state. We work the licensure question with each owner at policy bind so the insurance and licensing pictures stay aligned.
What Makes Co-Hosted STR Insurance Different
Co-hosted STRs introduce a layer of complexity standard owner-managed STR doesn't have to navigate: a third party making decisions at the property on the owner's behalf. Five specific underwriting realities follow from the co-host relationship.
1. Co-host as additional insured
The cleanest coverage structure for a co-hosted property names the co-host as an additional insured on the owner's general liability policy. When a guest brings a claim arising from the co-host's actions, the same GL policy responds to defense and indemnity for both parties. Insurance Information Institute guidance on commercial general liability covers the additional-insured mechanics. Without the endorsement, the co-host has to maintain separate professional liability or rely on personal coverage that may not respond to STR-related claims.
2. Agency relationship liability
When a co-host makes decisions at the property — accepting a booking, denying a guest, handling an incident — they're acting as the owner's agent. Tort law extends the owner's liability to cover the agent's actions within the scope of the agency relationship. This means the owner's GL has to be sized for the co-host's decision-making, not just the owner's. The written management agreement (where one exists) is the document that defines the scope of agency; we recommend reviewing it at policy bind.
3. Platform-level co-host classifications
Airbnb operates a formal Co-Host program with platform-level classifications, payout splits, and access-control structures. VRBO has its own approach. Both platforms now route booking communications through co-host-assigned roles, which creates a paper trail that adjusters and regulators can reference. Carriers underwriting co-hosted properties typically ask about platform-level co-host configuration at policy bind — the structure affects which party holds the booking liability.
4. Distributed booking decision-making
Owner-managed STR has one decision-maker — the owner — handling all bookings consistently. Co-hosted STR has two or more parties making case-by-case booking decisions, often in different ways. The variance creates fair-housing exposure (decisions about which guests to accept can look discriminatory in aggregate even when each individual decision was neutral) and claim-handling complexity. III.org's renter and landlord insurance guidance covers parallel issues in the long-term-rental space; the STR adaptation adds platform messaging as evidence.
5. Dispute resolution between owner and co-host
The owner-co-host relationship can itself generate covered losses. Disputes over management fees, scope changes, property condition at handover, security deposits, or platform account control occasionally escalate to legal claims. Most owner GL policies don't cover disputes between the owner and the co-host directly — but they do cover guest claims that arise during the dispute period, when management responsibility is unclear. The written agreement and clear platform-level access controls matter for both prevention and claim attribution.
Common Co-Hosted STR Claims We See
Co-host booking decision triggers a fair-housing claim
A co-host at an Airbnb listing declines a booking request in a way that the prospective guest alleges was discriminatory. HUD or state enforcement opens an inquiry; the owner is named as the platform account holder. Tenant discrimination liability responds, and the additional-insured endorsement on GL covers the co-host's defense. Severity typically $25,000–$100,000 with material defense cost.
Property damage during co-host transition
A co-host transition (new co-host taking over from prior co-host) leaves the property momentarily under-supervised. A guest causes damage during the gap. Property responds, but coverage attribution between the outgoing and incoming co-host arrangements adds claim-handling complexity. Severity $5,000–$30,000 typical depending on damage scope.
Co-host injury while working at the property
A co-host is injured while cleaning or maintaining the property between bookings. Workers' compensation or general liability may respond depending on the management agreement structure and state law. Owner-occupied STR hosts who treat their co-host as an independent contractor face a different exposure than those who employ a co-host directly. Severity $8,000–$40,000 typical on injury claims.
Mishandled guest interaction during co-host's shift
A co-host responds to a noise complaint, neighbor dispute, or guest incident in a way that escalates rather than de-escalates. The resulting guest complaint, platform suspension, or third-party claim ties back to the co-host's decision. GL responds with the additional-insured endorsement; without it, the co-host's response is uncovered. Severity varies sharply by incident type.
Co-host inventory loss during management transition
When a co-host's tenure ends, inventory of furnishings, supplies, and small fixtures occasionally doesn't reconcile. Contents coverage may respond to losses with theft or vandalism evidence; routine wear-and-tear losses sit outside coverage. The written management agreement's inventory clauses matter for the property-condition baseline.
Why Co-Hosted STR Operators Choose STR Guard
We structure the additional-insured arrangement at bind. The single most important co-hosted STR underwriting decision is whether the co-host is named as additional insured on the owner's GL. We work the question with each owner at policy bind — including reviewing the management agreement scope and confirming carrier appetite for the specific co-host arrangement.
We address agency-relationship liability. Owner exposure extends to the co-host's decisions when the co-host acts within the scope of the agency relationship. We size GL and umbrella limits with the agency exposure in mind, rather than just the owner's direct exposure.
We coordinate platform-level configurations. Airbnb's Co-Host program, VRBO's host-tier classifications, and other platform-specific arrangements affect how claims attribute. We document the platform configuration at policy bind so the claim handler at first notice of loss has the structural picture.
We respond in 1–2 hours during business hours. Co-hosted STR quote requests submitted through the STR Guard quote form are typically returned within 1–2 hours during business hours. Quotes involving complex management-agreement review may take longer, but you'll hear back from us the same business day.