A verbal or loosely-texted co-hosting arrangement is the single biggest source of disputes between hosts and co-hosts — unpaid commission after a cancellation, arguments over who covers guest damage, unpaid extra work no one agreed to. This article fixes that by laying out every section a co-hosting agreement legal template should contain, with a clause-by-clause structure you can adapt. Read it as the operational follow-through once you've already settled on rate and structure.

One thing to be clear about upfront: what follows is a structural starting point to have reviewed by a local attorney, not a ready-to-sign legal document. Requirements vary by state and province, and vary further depending on whether your co-host is classified as an independent contractor or an employee — a distinction with real legal and tax consequences you shouldn't guess at.

The Core Sections Every Co-Hosting Agreement Should Include

A workable agreement covers six areas at minimum. Skip any of these and you've left room for exactly the disputes this document exists to prevent.

Scope of Responsibilities Scope of work — the precise list of what the co-host is and isn't responsible for — is the most important section and the one most often left vague. Specify exactly which tasks the co-host handles: guest messaging, pricing authority, cleaning coordination, maintenance, guest issue resolution, and where each responsibility ends. If pricing authority is included, state whether it's independent or bounded by owner-set limits. Ambiguity here is the leading cause of co-hosting disputes, covered in more detail below.

Payment Structure and Schedule State the rate, the structure (percentage, flat fee, or hybrid), and critically, the timing and the edge cases. Specify what the percentage is calculated on (gross booking, payout after platform fees), when payment is due, and what happens to commission when a booking is cancelled or refunded. This last point causes more payment disputes than any other. If you haven't finalized the rate itself yet, the Airbnb co-hosting rates guide and the broader co-hosting rates pillar cover how to set it.

Access and Key/Lockbox Handling Specify how the co-host accesses the property: physical keys, lockbox codes, smart lock credentials, and who's responsible if access credentials are compromised. For arrangements involving other people (cleaners, contractors the co-host manages), specify who may hold or share access.

Liability and Insurance Responsibility State who carries what coverage and who is liable for what. This is where indemnification — a contractual promise by one party to cover certain losses or damages incurred by the other — belongs. Specify who holds co-hosting liability insurance and what it covers; co-hosting liability insurance breaks down how that coverage is typically structured. Getting this wrong means a guest-damage incident becomes a fight over who pays, exactly when you need clarity most.

Termination and Notice Period Define the notice period — the amount of advance warning either party must give before ending the arrangement — and what happens to in-progress and future bookings when the agreement ends. Specify how final payment is handled for bookings that were secured before termination but check out after it.

Confidentiality and Guest Data Handling Specify how guest data is handled, who retains access to booking records after termination, and any confidentiality obligations. This matters more than operators expect, since a departing co-host retaining guest contact data or platform access is a real risk.

The Clause-by-Clause Template Outline

Use the structure below as a drafting starting point — a checklist of what each section should specify — then have the finished document reviewed by a local attorney before signing. This is deliberately a structural outline, not legal boilerplate.

1. Parties and Properties. Full legal names of both parties; specific property or properties covered; effective date.

2. Scope of Work. Itemized list of included responsibilities; explicit list of what's excluded; whether pricing authority is independent or bounded; expected response-time or performance standards if any (co-host performance metrics you intend to hold them to).

3. Compensation. Rate and structure; calculation basis (gross vs. net of platform fees); payment timing and method; treatment of cancellations, refunds, and chargebacks; treatment of bookings that span the start or end of the agreement.

4. Access and Security. Method of property access; credential management; who may be granted access; return or revocation of access on termination.

5. Liability and Insurance. Each party's insurance obligations; indemnification terms; responsibility for guest damage, non-payment, and third-party (cleaner, contractor) actions.

6. Term and Termination. Start date and duration or at-will status; notice period for termination; handling of in-progress and future bookings; final payment reconciliation.

7. Confidentiality and Data. Guest data handling; confidentiality obligations; post-termination access and data return.

8. Amendments. How changes are made (see amendments section below); requirement that changes be in writing and signed.

9. Classification and Governing Law. Independent contractor vs. employee classification statement; governing state/province; signature blocks.

Two sections experienced operators tend to add only after a bad first experience: a co-host background check process clause (specifying that a background check was completed or is required, particularly where the co-host handles keys and guest access), and a defined co-host performance metrics standard tied to the termination clause, so underperformance has a contractually clear consequence rather than becoming a subjective argument.

What Happens When Scope Isn't Clearly Defined

Vague scope is the single most common source of co-hosting disputes, and it usually plays out in one of a few predictable ways.

Unpaid extra work. The co-host handles something they considered outside the original arrangement — a major guest complaint, an emergency repair coordination — and expects extra compensation the owner never agreed to. Without a scope section defining what's included, both parties are arguing from memory.

Gaps nobody covered. The reverse: a responsibility (say, restocking supplies or handling a specific type of guest issue) that neither party thought was theirs, discovered only when it's already a problem for a guest.

Creeping expansion. Scope creep — the gradual expansion of the co-host's actual workload past what the rate was set against — accumulates until the co-host feels underpaid and the owner feels the rate already covers it.

A precise scope section prevents all three by making "is this included?" a document-lookup question instead of a negotiation held at the worst possible moment.

How to Specify Payment Terms Without Ambiguity

Payment disputes almost always trace back to an edge case the agreement didn't address. Specify all of these explicitly:

  • Calculation basis. Is the percentage on the gross booking amount or the payout after platform fees? These produce meaningfully different numbers.
  • Timing. When is payment due — on guest checkout, on platform payout, monthly? Tie it to a concrete trigger.
  • Cancellations and refunds. If a guest cancels or is refunded after the co-host has done the work, is any commission owed? This is the most common payment dispute and needs an explicit answer.
  • Chargebacks and damage claims. Who absorbs the loss if a payment is reversed after commission was paid?
  • Bookings spanning the agreement's start or end. Who earns commission on a booking secured before the co-host started, or checking out after they've left?

Modeling the actual split against these scenarios before drafting helps — the co-hosting revenue split calculator lets you see how a proposed structure behaves across cancellations and edge cases before you write the terms into a binding document. And because payment structure affects how income is reported, it's worth understanding the co-hosting tax implications of the arrangement before finalizing the terms.

How to Handle Amendments as the Arrangement Changes

Co-hosting arrangements evolve — a second property gets added, scope expands, the rate is renegotiated. The agreement should specify that any amendment must be in writing and signed by both parties, and should avoid relying on informal text-message changes that recreate exactly the ambiguity the document was meant to eliminate.

For adding a property, decide whether you're amending the existing agreement or executing a separate one per property. A single agreement with a schedule of covered properties is often cleaner for a growing arrangement, since it keeps terms consistent while letting the property list expand through signed amendments. Pair this with a co-hosting onboarding checklist for each new property so the operational handoff stays consistent as the arrangement scales.

For execution, a reputable e-signature tool keeps a clear signed record of the original agreement and each amendment, which matters if a dispute ever turns on which version of the terms was in effect. That audit trail is worth more than it seems until the moment you need it.

Frequently Asked Questions

Do I really need a written co-hosting agreement for someone I know?

Yes. Informal arrangements between people who trust each other are among the most common to end in disputes, precisely because nothing was written down to resolve the disagreement. A written agreement protects the relationship as much as the money.

Is a template enough, or do I need a lawyer?

A template is a structural starting point, not a substitute for legal review. Co-hosting agreements touch on liability, tax classification, and state-specific requirements that a generic template can't safely resolve. Have a local attorney review the adapted document before signing.

What's the most important clause to get right?

Scope of work, followed closely by the cancellation/refund treatment in the payment section. These two account for the majority of co-hosting disputes, and both are entirely preventable with specific language.

Should my co-host be an independent contractor or an employee?

That classification has significant legal and tax consequences and depends on how the arrangement actually operates, not just what the agreement says. This is a specific question for a local attorney or accountant, since misclassification carries real penalties.

How do I handle adding a second property later?

Either amend the existing agreement with a signed schedule of covered properties or execute a separate agreement. A single agreement with an expandable property schedule is usually cleaner, as long as amendments are made in writing and signed.

The Takeaway

A co-hosting agreement legal template is only useful when it's specific — vague scope and unaddressed payment edge cases are what turn a working arrangement into a dispute, so the value is entirely in the detail you put into each section. Use the clause-by-clause outline above as your drafting structure, model the payment edge cases before you commit them to writing, and have the finished document reviewed by a local attorney before anyone signs.