What Should the Co-Host Do? Defining Scope Before Authority

Why Scope Comes First

If you're an owner considering a co-host, the first question isn't "What permissions should I give them?" — it's "What do I want them to do?"

Scope defines what the co-host is responsible for. Authority and access follow from scope. If you define authority before scope, you'll give permissions that don't match the work. If you define access before scope, you'll grant tools that aren't needed — or miss tools that are.

This guide helps you define scope clearly, using two principles that experienced operators rely on: the service scope builder and the distinction between outcome ownership and task execution.

The Service Scope Builder

The service scope builder is a simple framework for defining what the co-host will do. It works by breaking the overall job into specific service areas and defining each one.

The Core Service Areas

Most co-hosting arrangements involve some combination of these service areas:

1. Guest communication: Responding to inquiries, booking requests, and messages before, during, and after stays.
2. Calendar and pricing management: Managing availability, adjusting prices, setting minimum stays.
3. Cleaning and turnover coordination: Scheduling cleaners, inspecting properties, restocking supplies.
4. Maintenance coordination: Handling repairs, coordinating with vendors, conducting property walks.
5. Guest experience: Managing check-ins, resolving issues during stays, handling complaints.
6. Listing management: Creating and updating listings, managing photos, optimizing descriptions.
7. Financial reporting: Tracking income and expenses, reporting to the owner.

How to Use the Builder

For each service area, answer three questions:

1. Is this part of the co-host's scope? (Yes / No / Partially)
2. If yes, what specifically does the co-host do? (Be specific — not just "guest communication" but "respond to messages within one hour during waking hours; handle check-in instructions; resolve issues during stays.")
3. If partially, what's included and what's excluded? (For example, "co-host handles routine messages but owner handles all refund decisions over $50.")

Example: A Defined Scope

Here's what a completed scope builder might look like for a co-host handling a single property:

| Service Area | In Scope? | Specific Responsibility | |---|---|---| | Guest communication | Yes | Respond to messages within 1 hour during waking hours; send check-in instructions; resolve issues during stays | | Calendar management | Yes | Manage availability; accept and decline booking requests | | Pricing | Partially | Adjust prices within ±10% of owner's baseline; owner approves larger changes | | Cleaning coordination | Yes | Schedule cleaner; inspect property after each turnover; restock supplies | | Maintenance | Partially | Handle repairs up to $150 per incident; owner approves above $150 | | Guest experience | Yes | Manage check-ins; resolve guest complaints; handle reviews | | Listing management | No | Owner manages listing content, photos, and description | | Financial reporting | Yes | Monthly report of bookings, revenue, and expenses |

This scope is specific, actionable, and ready to be matched with authority and access.

Outcome Ownership vs. Task Execution

Once you've defined the service areas, you need to decide for each one: is the co-host owning an outcome or executing a task?

Task Execution

The co-host does a specific thing. The owner manages the overall outcome.

• Example: "Respond to messages within one hour." The co-host is responsible for the task (responding). The owner is responsible for the outcome (guest satisfaction).
• The co-host is measured on whether they did the task.
• The owner supervises and manages the overall experience.

Outcome Ownership

The co-host owns a result. They have the authority and access to do whatever is needed to achieve it.

• Example: "Maintain a 4.9+ guest rating." The co-host is responsible for the outcome. They have the authority to make decisions and the access to execute them.
• The co-host is measured on the outcome.
• The owner reviews the outcome, not the individual tasks.

Why This Distinction Matters

If the owner expects outcome ownership but the co-host thinks they're doing tasks, the guest experience falls through the gap. The co-host does the tasks but doesn't take responsibility for the result. The owner is surprised when the rating drops.

If the owner expects task execution but the co-host thinks they own the outcome, the co-host may overstep their authority. They make decisions the owner wanted to keep. Conflict follows.

Define this explicitly for each service area. Some areas may be task execution (e.g., cleaning coordination — "schedule the cleaner and inspect the property"). Others may be outcome ownership (e.g., guest communication — "maintain a response time under one hour and a 4.9+ communication rating").

How Scope Connects to Authority and Access

Once scope is defined, authority and access follow naturally:

• For each service area in scope, the co-host needs the authority to make decisions related to that area.
• For each authority, the co-host needs the access to execute those decisions.

This is the R→A→A alignment principle: responsibility → authority → access.

For example:

• Scope: "Respond to messages within one hour."
• Authority: "Answer questions, approve standard requests, issue refunds up to $50."
• Access: "Airbnb messaging access for the listing."

If you define scope first, the authority and access become clear. If you try to define authority or access first, you'll end up guessing — and probably wrong.

Common Scope Definition Mistakes

Vague Scope

"The co-host will help with the Airbnb." This is not a scope. It's a hope. The co-host won't know what to do. The owner won't know what to expect. Conflict is inevitable.

Fix: Use the service scope builder. Define each service area specifically.

Assumed Scope

The owner assumes the co-host will handle something (e.g., pricing) because "that's what co-hosts do." The co-host assumes they won't because it wasn't mentioned. Both are wrong.

Fix: Don't assume. Define. If it's not in the scope builder, it's not in the scope.

Over-Broad Scope

The owner wants the co-host to do everything. The co-host agrees. Neither has thought about whether the co-host can actually do everything well.

Fix: Start with a defined scope the co-host can deliver reliably. Expand later if needed. (See "Understanding Co-Hosting" for the smallest reliable service principle.)

Confusing Scope with Authority

The owner says "the co-host is responsible for pricing" but doesn't give them the authority to change prices or the access to the pricing tools. The co-host is responsible for something they can't do.

Fix: Define scope first, then match authority and access. (See "Co-Host Authority and Access" for the R→A→A alignment principle.)

What to Do Next

1. Complete the service scope builder for your arrangement. Write down each service area, whether it's in scope, and the specific responsibility.
2. For each service area, decide: task execution or outcome ownership. Write it down.
3. Once scope is defined, read "Co-Host Authority and Access" to define the authority and access that matches this scope.
4. Document the scope before the arrangement begins. A written scope prevents most conflicts.

The Bottom Line

Scope comes first. Before you grant authority or access, know what the co-host is responsible for. Use the service scope builder to define each service area specifically. Decide whether each area is task execution or outcome ownership. Then — and only then — define the authority and access that matches.

This guide is educational. It does not constitute legal advice. For questions about contracts or formal agreements, consult a qualified attorney.