Building Standard Operating Procedures

A standard operating procedure, or SOP, is simply a written-down version of how you already handle a recurring task, turned into a checklist someone else, including a future version of you, can follow without having to ask. For a landlord running two properties, most of this lives in your head and that is fine. Once you are running five, ten or more, or sharing the workload with a business partner, letting agent or virtual assistant, the gap between "I know how to do this" and "it is written down clearly enough for someone else to do it" becomes the difference between a portfolio that runs smoothly and one that depends entirely on you being available.

This guide covers what an SOP actually needs to contain, which recurring tasks are worth documenting first, and how to build one without turning it into a project that never gets finished.

What an SOP should cover

A useful SOP is a checklist, not an essay. For each recurring task, it should set out the trigger that starts the process, the steps in order, who does each step if more than one person is involved, and what "done" looks like. The best SOPs are written from an actual example, not from memory of how the task is supposed to go in theory, because the real version usually has two or three steps that only become obvious once you have done it and hit a snag.

The recurring tasks most landlords benefit from documenting first, roughly in order of how often they come up:

• Rent arrears escalation, from the first missed payment to a formal letter, matching the structure in our rent arrears guide so nothing depends on remembering the right sequence under pressure.
• Void and re-let turnaround, covering marketing, viewings, referencing and the handover to a new tenant, so a gap between tenancies is as short as it can be every time, not just when you happen to be paying close attention.
• Maintenance and repair triage, setting out which issues are genuine emergencies, which contractor to call for what, and the response time you are committing to for each category.
• Compliance renewal, covering gas safety, EICR, EPC and any HMO or selective licence, so renewal dates are chased proactively rather than discovered when a deadline has already passed.
• New property onboarding, covering everything from completion to the first tenant moving in, which our onboarding a new property guide sets out in full.
• Move-out and deposit return, including the check-out inventory comparison and the timeline for returning or disputing a deposit.

You do not need all of these written on day one. Pick whichever task currently causes the most stress or the most repeated mistakes, and start there.

Who an SOP is actually for

It is easy to assume SOPs only matter once you have staff or a large portfolio, but the more common trigger is smaller than that: a business partner who needs to cover for you while you are away, a letting agent who needs to know exactly which contractor to call for a specific type of repair, or simply you, six months from now, having forgotten the details of a process you only run once or twice a year. Our guide to sharing a portfolio with a business partner covers why written processes matter even more once a second person is genuinely relying on them, rather than simply being kept informed after the fact.

A useful test is to imagine handing a single task to someone with no prior knowledge of your properties. If the instructions you would need to give them exist only in your head, that task is a good candidate for the next SOP you write.

How to actually build one

The mistake most landlords make when they decide to write SOPs is trying to document everything from a blank page, in one sitting, before any task has actually come up. That produces a document that reads well but misses the real steps, and it rarely gets finished. A more reliable approach:

1. Write it the next time you actually do the task. Keep a note open while you handle a rent arrears case or onboard a new property, and jot down each step as you go, including the parts that are not obvious, such as which specific document you need or which number you call first.
2. Turn the notes into a numbered checklist, cutting anything that was specific to that one situation rather than true every time.
3. Store it somewhere it will actually be found later, a shared document, a folder structure everyone involved uses, or software that keeps checklists attached to the relevant property or task. A brilliant SOP buried in an old email thread is no better than no SOP at all.
4. Use it, then correct it. The first time you or someone else follows a new SOP, something will be missing or slightly wrong. That is expected. Fix it immediately rather than working around it silently, or the gap will still be there the next time.
5. Review it when something changes, particularly after a change in the law, such as a shift in notice periods or deposit rules, or after a genuine near-miss that revealed a gap in the process.

A worked example shows how this plays out. A landlord with six properties keeps missing the point at which a gas safety renewal should be booked, twice arranging it only after the certificate has technically lapsed. After the second near-miss, they write a two-line SOP: check the compliance calendar every Monday, and book any certificate due within eight weeks. Nothing more complicated is needed. The problem was never the landlord's competence; it was that the trigger to act was not written down anywhere, so it depended on memory alone.

Common mistakes

The most common mistake is writing an SOP once and never updating it, so it slowly drifts out of step with how the law, your contractors or your own process have actually changed, and eventually becomes actively misleading rather than merely outdated. A second is making SOPs too long and formal, covering edge cases nobody actually hits, which puts people off using them at all. A third is keeping the only copy in one person's head or inbox rather than somewhere shared, which defeats the entire point once a business partner, agent or assistant needs to step in.

A less obvious mistake is treating SOP-writing as a one-off project rather than an ongoing habit. The landlords who get the most value from SOPs are the ones who add a line to an existing checklist the moment they notice a gap, rather than waiting for a dedicated afternoon that never quite arrives.

How Property HQ helps

Property HQ keeps compliance dates, maintenance records and tenancy milestones attached to each property in one place, so the checklists in your SOPs, renew this certificate, chase this deadline, follow this escalation step, have a single system to point to rather than depending on a separate document nobody remembers to open. Our compliance calendar guide covers how to keep the renewal side of this running automatically once the process itself is written down.

Disclaimer

This guide is general information for UK landlords, not legal or business advice. The right level of process depends on the size and structure of your portfolio. Check current legal requirements on GOV.UK or with a qualified adviser before relying on any SOP for a compliance-critical task.