What should I review with my co-host each month?
An owner-led monthly scorecard and 45-minute example agenda covering financial exceptions, guest incidents, vendor readiness, upcoming work and approvals.
Short answer: Review exceptions, unresolved risks and decisions—not every message. Use a defined scorecard, comparable reporting periods and an action register with one owner per item. Keep live emergencies and damage-claim deadlines out of the monthly waiting queue.
This is an owner governance workflow. It does not create a Vacohost review SLA or promise a particular occupancy, revenue or response result.
Ask for a decision packet, not a data dump
Request the previous action list, reconciled financial exceptions, available/blocked dates, refunds and claims, turnover/access incidents, repeat maintenance issues and proposed owner decisions. An example internal target is two business days before the meeting; that is an owner-set agreement, not a platform rule.
Airbnb’s earnings dashboard supports paid/upcoming views and reporting tools. Use those actual records rather than a projection screenshot. Airbnb earnings dashboard. Vrbo reporting separates payout and stay-date perspectives; agree the basis before comparing. Vrbo payout summary.
Define the denominators so the scorecard means something
| Measure | Definition to agree | Source and owner question |
|---|---|---|
| Occupancy | Booked nights ÷ defined available nights | Calendar; how are owner stays and maintenance blocks handled? |
| ADR | Room revenue ÷ booked nights | Reservation report; exclude unrelated fees consistently |
| RevPAR | Room revenue ÷ defined available nights | Same period/denominator as occupancy |
| Operating contribution | Agreed receipts less listed operating costs | Reconciliation; which costs remain outside the number? |
| Refunds/claims | Processed, pending and received amounts separately | Incident/transaction log; what is near a deadline? |
| Turnover/access incidents | Count and severity with evidence | Readiness/access log; what is recurring? |
| Owner interruptions | Defined decisions requiring owner involvement | Escalation log; are boundaries clear? |
Do not compare occupancy after removing blocked nights in one period with a full-calendar denominator in another. Treat owner use, closures and maintenance consistently and disclose the choice. There is no universal “good” occupancy threshold or automatic reason to cut prices.
Compare seasonally appropriate periods where data supports them, not only last month. Account for different booking windows and channel mix without claiming a causal explanation the evidence cannot establish.
A 45-minute example agenda
| Minutes | Topic | Required result |
|---|---|---|
| 0–5 | Prior actions | Close with evidence or reset owner/due date |
| 5–15 | Financial exceptions | Assign payout/refund variances and missing invoices |
| 15–25 | Guest, turnover, access and safety incidents | Fix repeated causes and deadline risks |
| 25–35 | Forward calendar and maintenance | Confirm owner stays, local readiness and approved work |
| 35–45 | Approvals and next actions | Named owner, budget, due date and closure proof |
This timing is illustrative. A consequential safety problem gets immediate attention rather than waiting for minute 15 next month.
Keep approval boundaries explicit
The owner approves refunds, repairs, rate strategy and consequential spending. The co-host organizes messages, vendor coordination and incident evidence within agreed permissions. A cleaner or handyman verifies physical readiness; a remote report cannot certify a repair by itself.
Review refund and emergency-spend limits, alternate approvers, local responder coverage and access permissions when staffing changes. Claim clocks need active escalation independent of the meeting. Airbnb Help and protection terms use different claim/evidence requirements; use the damage evidence playbook, not an assumed monthly deadline.
A simple action register that can be closed
| Decision/action | Evidence needed | Accountable person | Budget/authority | Due | Closure proof |
|---|---|---|---|---|---|
| Repair repeated lock failure | Device/local assessment | Owner-approved local provider | Written repair cap | Agreed date | Guest-access test and invoice |
| Resolve unexplained payout | Reservation/payout/bank references | Bookkeeper or financial reviewer | Owner financial access | Agreed date | Matched variance record |
| Improve turnover handoff | Missed-confirmation timeline | Coordinator and cleaner | Approved vendor agreement | Before next turn | Confirmed readiness checklist |
Name one accountable person per action even when several people help. Record the decision separately from the proposed idea; “consider a new lock” is not an approved purchase.
Leave with fewer owner interruptions
The useful output is a short decision record and a better next-month operating plan. Do not turn a monthly review into a requirement for the owner to retake daily management. Check whether repeated interruptions arise from unclear caps, missing local help, bad access or an unsupported task—not simply slow replies.
Use Airbnb Essentials or Airbnb + Vrbo Coverage when guest operations are the work to delegate. The owner retains listing and revenue control. Compare the costs after deciding what stays local and what decisions stay with you.
Last fact-checked: · Official sources linked beside the relevant facts. Recommendations are editorial guidance, not platform requirements.
Done-for-you service
Hand off guest messages, vendor coordination, and reviews to Vacohost.
Want this applied to your listing?
Email us with your property details and we'll tell you what we'd change first — whether or not you hire us.
go@vacohost.com