Writing SOPs your property management team will actually use
Most property management SOPs fail because they're written at the wrong altitude. They describe what a process is in broad terms — 'respond to maintenance requests in a timely manner' — but leave the person reading them with no idea what to actually do. A good SOP answers one question: what does the person doing this task need to know to complete it correctly without asking anyone?
Start with the processes that cause the most errors or questions
You do not need SOPs for everything. You need them for the things that go wrong most often or that consume the most time when someone has to figure them out from scratch. Common candidates: move-in and move-out procedures, maintenance request intake and escalation, rent collection and late-payment follow-up, lease renewal, and notice of entry. These are high-frequency, high-stakes, and often handled differently by different people on the same team.
Write procedures at the right level of detail
An SOP should be specific enough that someone new to the role can follow it without asking questions, and short enough that an experienced person doesn't mind re-reading it. The practical test: hand it to someone who has never done the task before. If they can complete the task correctly without asking a single follow-up question, it's specific enough. If they set it down and don't finish reading, it's too long.
- State the outcome first: 'After completing this process, the unit file should have a signed move-in report, dated photos in the shared folder, and a completed key log.'
- Use numbered steps for sequences where order matters. Use bullet points for checklists where order doesn't.
- Name the specific tool, system, or form at each step — not 'record the information' but 'enter the move-in date in Kera under the lease record.'
- Include the common failure points: what to do when the tenant doesn't show up for move-in, or the vendor cancels.
The core SOPs every property management operation needs
While every business is different, most operations benefit most from documented procedures in five areas: move-in (from lease signing to key handover), move-out (from notice receipt to deposit return), maintenance intake (from request received to work order created to vendor dispatched), rent collection (what happens on day one, day five, day ten, and beyond), and lease renewal (who initiates, when, what the tenant receives, and what the deadline is).
Move-in SOP: the most common place for first impressions to go wrong
A move-in procedure should cover every step from lease signing through the first day of occupancy: when and how the tenant receives keys, what form the move-in inspection uses, who does the walkthrough with the tenant and what's covered, where photos are stored, and how the tenant confirms the condition in writing. The last step — written tenant acknowledgment of unit condition — is what protects you at move-out.
Maintenance intake SOP: preventing the black hole
Maintenance requests disappear when intake is inconsistent. Your SOP should define how requests arrive (portal only, or also phone?), what information must be captured at intake (unit, description, access permission, photos), how quickly the tenant receives an acknowledgment, and what escalation looks like for urgent versus routine issues. Without this, requests fall through and tenants follow up repeatedly — which doubles the contact volume.
Test each SOP before you publish it
Write the first draft of a procedure, then ask a team member or colleague to complete the task using only the document. Watch what they do. Every point where they pause, ask a question, or do something different from what you expected is a gap in the document. Fix those gaps before the SOP goes live. A procedure that passes this test once has actually been validated; one that hasn't has only been written.
Keep them current — stale SOPs are worse than none
An SOP that no longer reflects how the process actually works erodes trust in all your documentation. Set a review cadence — at minimum, annually — and update whenever a tool changes, a regulation changes, or you discover the procedure isn't being followed because it doesn't match reality. The date of last review should appear on every SOP so anyone reading it knows how current it is.
- Kera maintenance and work orders
- Kera lease management
- Scaling your portfolio without adding headcount
- More operations guides
How long should a property management SOP be?
Long enough to answer every practical question someone doing the task would have, short enough to be read in under five minutes. For most property management procedures, one to two pages is right. If you're writing more than that, the process either genuinely needs sub-procedures broken out separately, or you're including context that belongs in training rather than an SOP.
Should I use video SOPs or written ones?
Both are valid. Video works well for visually complex tasks like a physical inspection walkthrough. Written works better for anything that involves software steps, because readers can follow along without pausing and rewinding. For most property management procedures, written with screenshots of the relevant screens is the most practical format.
What's the difference between an SOP and a checklist?
An SOP explains a process: background, steps, decision points, and what to do when things go wrong. A checklist is a completion tool: a short list of steps to verify without explanatory text. SOPs are for training and reference. Checklists are for execution. Most property management processes benefit from both — an SOP to explain the process and a checklist to use when running it.
How do I get team members to actually follow SOPs?
Make the SOP the path of least resistance. If the documented procedure is faster and easier than improvising, people follow it. If it's harder, they work around it. Involve the people who do the work in writing the procedures — they'll catch gaps you missed and they're more likely to follow something they helped create.
What tools do I need to store and share SOPs?
Any shared, searchable document system works: Google Docs, Notion, or a dedicated operations wiki. The critical requirements are that it's searchable, that everyone has access, and that there's a clear place to check for the current version. Version control — knowing which SOP is current — matters more than the tool.
Build processes around a platform your team already lives in
When your SOPs are tied to a system that handles leases, maintenance, and tenant communication in one place, every documented step has a home — and new hires can be operational faster.
Run your whole business on Kera
Flat pricing, no per-door fees. Built for property managers.
