Useful before
the next shift.
Six short checklists. Open the one that matches the work in front of you.
PROPERTY KNOWLEDGEBefore anyone answers a guest
Keep one approved record. Store arrival instructions, house rules, appliance guidance, local contacts and approval limits in the agreed PMS or playbook. Record who checked it and when.
Test the recovery steps. A lock code is not a fallback plan. Identify the person who can provide lawful backup access and how the operator reaches them.
Make changes traceable. When an instruction changes, update the source record and the next shift. Do not let the latest answer live only in a chat.
See how this fits the serviceCOVERAGEGive the overnight team enough authority
Define the shift. Write down hours, time zone, covered channels and the person accepting each handoff. Name a fallback if the normal route fails.
Set decision limits. Separate routine replies from refunds, cancellations, access exceptions and spend approvals. Give each exception a named client approver.
Review the actual work. Measure unresolved issues and repeated interruptions as well as response times. Read the records before concluding that a fast reply resolved the problem.
See how this fits the serviceARRIVAL READINESSReady means checked, not assumed
Check the dependencies. Confirm housekeeping, inspection, access and open maintenance against the next arrival. Missing evidence should remain an open item.
Assign a recovery owner. A delayed cleaner needs an accepted backup task or a documented guest plan. Record the owner, due time and approval.
Close with evidence. Use the agreed confirmation or inspection record. Keep sensitive access details out of broadly shared task channels.
See how this fits the serviceRESPONSIBLE ALERTSA signal starts a review
Confirm the boundary. Only use approved, properly disclosed exterior devices and permitted noise or access signals. Aunbnb does not support indoor cameras or continuous surveillance.
Review before acting. Check the property context and written response plan before contacting a guest. Do not assume an alert proves misconduct.
Keep local responsibility clear. Remote coordination does not replace emergency services or physical response. Preserve a concise decision record and follow agreed retention rules.
See how this fits the servicePROPERTY RESEARCHA promising listing is not a business case
Date the assumptions. Compare relevant properties and seasonality using permitted market data. Record the source and treat projected revenue as an estimate.
Cost the whole operation. Include setup, channel fees, cleaning, supplies, utilities, repairs, management, financing and reserves. Test a weaker season rather than one attractive month.
Verify locally. Rental permission, licensing, tax and purchase decisions need qualified local review. Data sources do not endorse a particular purchase.
See how this fits the serviceOWNER REPORTINGExplain what the owner actually receives
Separate the measures. Revenue less operating expenses gives an operating result. Debt service and reserve allocations then change owner cash flow. Neither alone is a full tax calculation.
Show missing records. Reconcile reservation statements, fees, receipts and approved adjustments. Mark incomplete periods instead of presenting false precision.
Use AI for explanation, not invented arithmetic. A future assistant can summarize verified changes. Calculations should remain reproducible and traceable to reviewed records.
See how this fits the serviceGeneral operating guidance. Client procedures and qualified local advice take precedence where relevant.
Turn an open question into a clear operating standard.
Discuss your properties. Agree the scope and coverage before any paid work.