An Airbnb co-host agreement has to answer four questions before anyone touches a guest message: what the co-host is paid a percentage of, who moves the money, whether the co-host is a contractor or an employee under the control test the IRS actually applies, and which state licensing rule the arrangement triggers when the co-host collects rent for someone else. Get those four right and a 15% split is a clean deal. Get them wrong and you have a payroll liability, an unlicensed brokerage question, and a fight over a month where the property lost money.
Most co-hosting arrangements start as a favor and end as a dispute, because the paperwork was a screenshot of a template that priced the work without defining the base, the boundary, or the exit. This piece is the decision sequence I use instead.
What an Airbnb co-host agreement has to decide
Airbnb's co-host feature is a permissions setting. It lets another account handle messages, calendars, and pricing on a listing. It is not a contract, it does not decide who is liable when a guest floods a bathroom, and it does not tell a tax authority who employed whom.
The agreement is the part that matters, and it needs six decisions in writing:
Scope. Which tasks, at what hours, with what response-time standard.
Pay structure. Percent, flat fee, or hybrid — and of what base.
Money flow. Whose bank account receives the payout, who reimburses expenses, who covers a chargeback.
Classification. Contractor or employee, with the control terms that support the answer.
Authority limits. Maximum spend without approval, discount and refund authority, whether the co-host may sign anything.
Exit. Notice period, account-access handover, final reconciliation, who owns the reviews and guest data.
If a term is missing from that list, it will be decided later by whoever is angrier.
Three pay structures, and what each one actually buys
Percent-of-revenue is the default because it looks aligned. It is aligned on occupancy, and misaligned on cost discipline: a co-host paid on gross revenue has no reason to argue with a discount that fills a Tuesday at a loss.
Figures in this article, in the tables and in the prose examples, are illustrative structures, not market survey data. Price your own deal from your own P&L.
Structure | What it rewards | Where it breaks | Fits when |
|---|
Percent of revenue (e.g. 10–20%) | Occupancy and rate | Co-host earns on discounted, low-margin bookings | Owner keeps pricing authority and reviews the calendar |
Flat monthly fee per unit | Predictability and process | Co-host loses on a heavy-turnover month; no upside | Stable mid-term or corporate stays |
Base fee + share of profit above a threshold | Net outcome, cost control | Requires an agreed definition of "profit" and open books | Trusted operator, multi-unit portfolio |
The hybrid is the honest structure for most portfolios, and the one people avoid because it forces a definition of net. That definition is the work.
Percent of what? Define the revenue base before the split
"Fifteen percent" is not a term. Fifteen percent of what is a term. Three bases produce three different checks on the same booking.
Line item | Booking example | Included in base? |
|---|
Nightly rate, 4 nights | $640 | Yes, in all three bases |
Cleaning fee collected | $150 | Only in "gross collected" |
Platform service fee withheld | −$19 | Excluded from "net payout" base |
Taxes collected and remitted | $77 | Never — it is not your money |
Base: gross collected (rate + cleaning) | $790 → 15% = $118.50 | |
Base: room revenue only | $640 → 15% = $96.00 | |
Base: net payout after platform fee, before cleaner pay | $771 → 15% = $115.65 | |
Same stay, a $22.50 spread on one booking, roughly $270 a year on one unit at one booking a month. Two rules keep this clean: taxes collected on behalf of a jurisdiction never enter anyone's fee base, and pass-through costs you reimburse at cost — cleaner pay, consumables — are excluded unless you intend to pay a margin on them. If your cleaning fee does not cover your cleaner, the split is not your first problem; see the guest fee versus cleaner pay math.
Contractor or employee: the control test decides for you
Calling someone a contractor in a document does not make them one. The IRS says the classification turns on the degree of control and independence, grouped into behavioral control, financial control, and the type of relationship — and it states plainly that a person working remotely for you is an employee under the common-law rules if you can control what will be done and how it will be done, even when the worker chose to work remotely (IRS: independent contractor or employee).
Read that against a typical co-host arrangement. A co-host who must answer within 15 minutes, use your scripts, work your assigned hours, use your accounts and tools, and take no other clients is not describing independence. That is the arrangement most owners write when they are nervous about quality.
Terms that support contractor status, if they are true:
The co-host sets their own hours and methods against an outcome standard, not a script.
The co-host serves other properties or clients and is free to.
The co-host supplies their own tools and absorbs their own overhead.
The engagement is project- or term-based with defined deliverables, not open-ended supervision.
Pay is per unit or per outcome, not an hourly wage with your approval on the timesheet.
If you need the control, hire the role instead of mislabeling it. The comparison of when to hire versus contract is covered in DIY versus hiring out property management, and the sequencing question — coordinator first or operations lead first — in VA versus operations lead.
When collecting rent for someone else needs a license
This is the clause most co-host templates skip. In California, a person who, for compensation, "leases or rents or offers to lease or rent, or places for rent… or collects rents from real property" for another is acting as a real estate broker under Business and Professions Code §10131(b) (California B&P §10131). Statutes differ by state, and several carve out on-site managers or specific short-term arrangements, so check your state's statute instead of assuming a rule of thumb.
Practical effect on the agreement: if the co-host receives guest funds into an account they control and takes a cut, they look like a manager collecting rent for another. If guest payouts land in the owner's account and the co-host is paid separately for services, the arrangement looks like a service contract. Same work, different regulatory shape. Check your state's real estate commission language, and put the answer in the agreement as a representation the co-host makes about their own licensing status.
Money movement, access, and what gets reported
Decide the payout path first, because everything downstream — bookkeeping, liability, tax forms — follows it.
Owner-receives model. Airbnb payouts go to the owner's account; the co-host invoices monthly. Cleanest for classification and licensing, requires the owner to fund reimbursements promptly.
Co-host-receives model. Payouts land with the co-host, who remits net to the owner. Convenient, and it puts the co-host in the position of holding other people's money — the position licensing statutes and trust-account rules care most about.
On reporting: rental income and expenses are generally reported on Schedule E, but the IRS notes that when you provide substantial services primarily for the tenant's convenience, the income belongs on Schedule C instead (IRS Topic 414). Short-term hospitality operations frequently sit closer to the services end of that line than owners assume, which changes self-employment tax exposure. If the co-host is a contractor, their pay is nonemployee compensation reported on Form 1099-NEC (IRS: About Form 1099-NEC) — confirm the current filing threshold in that year's instructions rather than assuming last year's number. This is a bookkeeping-and-tax-professional question, not legal or tax advice from me.
Access terms belong in the same section: named accounts rather than shared passwords, no co-host on the payout method, immediate credential rotation on exit, and a written answer on whose insurance responds to guest damage and to a liability claim. If the co-host carries their own general liability coverage, name the policy and the limit in the agreement instead of assuming it exists.
Building the agreement: a six-step process
Step 1 — Write the scope as a task list with standards
List every recurring task, the response-time standard, and the hours it applies. Anything not on the list is the owner's job by default. This single page prevents most co-hosting arguments.
Step 2 — Pick the structure, then define the base line by line
Choose percent, flat, or hybrid. Then write the base as an itemized inclusion list, using the table above as the template: room revenue, cleaning fee, platform fees, taxes, reimbursed pass-throughs — each marked in or out.
Step 3 — Set authority limits in dollars
A spend ceiling without approval, a discount ceiling, a refund ceiling, and a rule for after-hours emergencies where the co-host may exceed the ceiling and document within 24 hours.
Step 4 — Choose the classification and make the terms match
Decide contractor or employee, then read the control terms back against the IRS factors above and delete any clause that contradicts the choice. If you cannot delete them, you chose wrong.
Step 5 — Fix the money path and the licensing representation
Name the receiving account, the invoice date, the payment date, the reimbursement mechanism, and the co-host's representation about their licensing status in the property's state.
Step 6 — Write the exit before you sign
Notice period both directions, credential handover checklist, final reconciliation window, treatment of bookings already on the calendar, and a statement that guest data and reviews stay with the listing owner.
Failure modes and the exit terms that cover them
Failure mode | What it costs | Clause that prevents it |
|---|
Co-host discounts to fill a low-margin night | Occupancy up, net down | Discount ceiling; profit-share instead of gross share |
Payouts sit in the co-host's account at separation | Cash held hostage, weeks of reconciliation | Owner-receives payout model; final reconciliation window |
Shared login, no rotation on exit | Ongoing access to guest data and pricing | Named accounts; rotation checklist in exit clause |
"Contractor" who works assigned hours to a script | Back payroll tax and penalty exposure | Classification review against the control factors |
Co-host collects rent in a licensing state without status checked | Fee agreement potentially unenforceable | Licensing representation and warranty |
Bookings on the calendar past the notice date | Guest-facing cancellations, review damage | Named handover of forward bookings |
The pattern across all six: the money and the authority were defined, and the transition never was. Write the exit clause on the same day you write the pay clause.
If you want a second read on your own arrangement before it goes to a professional, book a complimentary one-on-one diagnostic call and bring the current draft plus one month of actuals.
Frequently Asked Questions
Is 20% too high for an Airbnb co-host?
It depends entirely on the base and the scope. Twenty percent of room revenue for full guest communication, pricing, cleaner scheduling, and maintenance triage can be cheaper than 12% of gross collected on a narrow scope where the owner still handles vendors. Compare the dollar amount per unit per month, not the percentage.
Does Airbnb's co-host feature create a legal agreement?
No. It grants listing permissions. Your rights and obligations come from the separate written agreement between you and the co-host, which is why the permissions setting should be the last step, not the first.
Should the co-host receive the payouts?
Prefer the owner-receives model unless there is a specific reason otherwise. It keeps the co-host out of the position of holding someone else's money, which is what licensing and trust-account rules police.
Can I pay a co-host a percentage and still call them a contractor?
Payment method is only one factor. The IRS weighs behavioral control, financial control, and the type of relationship together, so a percentage arrangement wrapped in assigned hours, required scripts, and exclusive service can still look like employment.
What happens to reviews and guest data if we split?
Nothing, unless you wrote it down. State in the agreement that reviews, guest records, and messaging history belong to the listing owner, and require deletion of exported guest data on exit.
How long should the notice period be?
Long enough to cover the booking window already on the calendar — commonly 30 days for a short-stay portfolio and longer where mid-term stays are booked months out.
Sources
