Loading...
Loading...
Category: Multi-Property & Scaling
By: Tony Russo
Reply by Nolan Peters:
SOPs transformed my business from "everything runs through me" to "everything runs without me." Here's how I approached it. I use Notion (free tier) with one page per process. Each SOP has a title, a trigger (when does this happen?), an owner (who does it?), the steps, decision trees for when things go sideways, and an escalation path for when to call me. Keeping it this structured sounds overkill but when you hand something to a VA or a cleaner, they need zero ambiguity. The processes you need to document first: guest check-in (lock code setup, welcome message timing, what to do when something goes wrong with access), guest complaint handling (what the VA resolves vs what gets escalated to you vs what's a "call 911" situation), guest checkout process (automated messages, review request timing, damage inspection), and review response protocol (templates for 5-star, 4-star, 3-star, and negative reviews, and which ones your VA handles vs which need your eyes). For turnovers: a room-by-room cleaning checklist with photos showing what "done right" looks like (I use Google Slides for this), a quality control inspection protocol for your lead cleaner, and a supply restocking process covering when to reorder, minimum quantities, where to order, and budget limits. Maintenance: emergency response decision tree (water leak, no heat, lockout, broken appliance — who to call and when), routine maintenance schedules (HVAC filters, hot tub chemicals, pest control), and repair authorization (my handyman can approve anything under $200 without calling me; above $200 needs my OK). Business: a new property onboarding SOP (keys to first guest in 14 days, step by step), financial reconciliation (weekly booking vs payout review, monthly P&L, quarterly tax prep). How to actually create these without losing your mind: don't try to write them all at once. Record yourself doing each task using Loom (free for 25 videos/month), narrate what you're doing and why, send the video to your team AND write up the numbered steps. Then every time something goes wrong, update the relevant SOP. Every problem improves a process. The time investment is maybe 20 hours to write the initial core SOPs. But it saves you 100+ hours per year in explaining things, putting out fires, and redoing work that got done wrong. For guest-facing templates to build your SOPs around, the message library at https://strspecialist.com/tools/message-library and the house manual generator at https://strspecialist.com/tools/house-manual-generator are good starting points.
Reply by Jake Anderson:
My SOP tip that saves the most time: **the "3-strike rule."** If a question or situation comes up 3 times, it becomes an SOP. I keep a running note on my phone of questions I get from my team. When anything hits 3 occurrences: 1. I write the SOP 2. I share it with the team 3. I add it to the Notion database 4. Next time it happens, I just send the link This prevents SOP bloat (you don't need 100 SOPs for edge cases) while ensuring the common stuff is documented. Also: **turn your best review responses into templates.** When you write a review response that gets a lot of compliments or resolves a situation well, drop it in your review response SOP. After 6 months, you'll have templates for every scenario. The review response generator at https://strspecialist.com/tools/review-response-generator is another great source for proven response templates.