Here is a diagnostic. If you were unreachable for two weeks — not checking messages, genuinely away — could someone else keep your portfolio running? Not grow it, not handle a crisis brilliantly. Just keep rent collected, maintenance dispatched, tenants answered and owners informed.
For most small property management operations the honest answer is no. Not because the work is difficult, but because the knowledge of how it is done lives in one person’s head, and that person is on a beach.
What Is Actually in Your Head
The gap is rarely the big things. It is the accumulated small knowledge that nobody has ever written down.
Which plumber to call for which building, and which one not to call for the property on Union Street. Which owner wants to approve every expense over two hundred dollars and which one does not want to be contacted unless something is on fire. Where the spare keys are and what the labelling scheme means. Which tenant has an informal arrangement to pay on the third. What the access code is for the back entrance. Which supplier has the account and which requires payment on delivery.
None of it is complicated. All of it is load-bearing, and none of it is recoverable by a colleague under time pressure.
Start With Frequency and Consequence
The instinct is to write everything, which produces a project that is abandoned in week two. Instead, write down the things that happen often, and the things that happen rarely but go badly wrong when handled incorrectly.
The first list is short and predictable: taking a maintenance request, dispatching a vendor, processing rent, following up arrears, responding to a tenant complaint, showing a unit, screening an application, running an inspection, producing owner statements, paying invoices.
The second list is shorter still and is where the real risk sits: an emergency after hours, a serious tenant complaint, a suspected illegal activity, a death in a unit, a serious water or fire event, serving notice to end a tenancy. These go wrong expensively when improvised, and they are precisely the ones a substitute will face without preparation.
Write Them Properly
A usable procedure is short, specific and testable. A page. Numbered steps. Names, numbers, thresholds and actual system locations, not general descriptions.
“Contact an appropriate vendor and arrange attendance” is useless to someone who does not already know the answer. “Heating, Unit 1 to 12: call Harding Mechanical first. If no answer within thirty minutes, call the second contact on the vendor list. Authority to proceed up to five hundred dollars without approval” is a procedure.
Include, for each one: when it applies, the steps in order, who to contact, the decision thresholds, where the record goes, and what to do if the normal path fails. That last element is what separates a procedure that survives contact with reality from one that does not.
Write Them While Doing the Work
This is the technique that makes the project finishable. Do not sit down to write procedures. The next time you handle a maintenance request, write down what you did as you do it. Next time you run a showing, same. Over a month of ordinary work you will have captured most of the common list at almost no marginal cost.
Procedures written from memory are consistently wrong in the same way: they omit the steps that have become automatic, which are exactly the steps a newcomer needs.
The Reference Material Beside Them
Procedures describe how. A handful of reference documents hold what, and they matter just as much.
- Property sheets. One page per property: address, units, owner and their contact preferences, key access, utility accounts, shutoff and panel locations, system ages, known quirks.
- Vendor list. By trade, with two names each, rates, after-hours terms, spending authority, and insurance expiry dates.
- Owner preferences. Approval thresholds, reporting expectations, how they want to be contacted, and anything standing you have agreed to.
- Tenant notes. Factual and professional only — arrangements, accessibility requirements, communication preferences. Nothing you would not want read aloud, because it may be.
- Access and credentials. Where keys and codes are held, and how someone authorized would reach the systems. Handled securely, through a password manager with emergency access rather than a document.
Test It, Because Untested Procedures Are Fiction
Give a procedure to someone who has not done the task and have them follow it exactly. They will stop within three steps at something you did not think needed explaining. That gap is the value of the exercise, and you will not find it by rereading your own writing.
The stronger test is a real handover. Have a colleague run one function for a week while you are available but not involved. What they have to ask you is your list of missing procedures.
Why This Is Worth the Effort
The vacation framing is real but it is the smallest benefit.
Written procedures make the work consistent, which is the foundation of everything from tribunal defensibility to owner confidence. They let you delegate, which is the only way a portfolio grows past one person. They dramatically shorten the time it takes a new hire to be useful. They protect the business against your own unavailability, planned or otherwise, which is not a hypothetical concern.
And they make the business saleable. A property management operation that exists only in the owner’s head is worth very little to a buyer. One that runs on documented process is worth a multiple of its earnings.
Keep Them Alive
A procedure manual written once and never revised becomes actively harmful, because people follow instructions that are no longer correct. Review quarterly. Update whenever something changes. Delete what is obsolete rather than leaving it in.
Two hours a quarter maintains the entire thing. The alternative is a business that cannot function without you being reachable, which is not a business you own so much as one that owns you.