Step 2: Triage and Prioritisation

Not all repairs are equal; ultimately, you decide which jobs need priority..

Best practice:

• Let the tenant describe what’s wrong through structured categories. Not “how urgent” it is. Category and sub-category can drive an automated priority suggestion, but the property manager should have the final say before assigning a job. Urgency is an accountability judgement, not a self-declared field.
• Route true emergencies. Suspected gas leak, fire, uncontrolled flooding, etc straight to an emergency process the moment they’re reported, bypassing the normal triage queue entirely. These categories are unambiguous at the point of report. The priority is getting the right emergency number or contractor engaged immediately, not confirming details first.
• When a photo and description are enough to confirm a category, the genuinely ambiguous cases apply to a different set of triage. Structural concerns, the extent of damp or mould, an electrical fault that may or may not be live. These often need an inspection before you can commit to a compliant response window. A workflow that assumes you can definitively categorise each of these at first contact doesn’t account for how they actually play out.
• Some categories need context to prioritise properly, not more inspection. No heating in January is a different severity than no heating in July for an average healthy adult, and it’s even more serious when a vulnerable tenant flag is present. This is a good example of how category and sub-category, combined with a couple of contextual signals like season and vulnerability, can drive a strong automated priority suggestion, with the property manager confirming rather than starting from scratch.
• Review repeat issues and compliance-sensitive categories:  damp, mould, electrical faults etc for manager review rather than letting automation route them straight through.

Regulatory note: Awaab’s Law’s extension to the private rented sector doesn’t yet have a confirmed commencement date, but it’s worth treating as a matter of when, not if. Getting response-time tracking, evidence capture, and a defined escalation path in place now, ahead of a hard deadline, means it’s a smaller lift when the timeframes are confirmed rather than a scramble against the clock. HHSRS assessment is a hazard-by-hazard judgement rather than a fixed set of time bands, so a workflow that can flex as your categories mature will serve you better long-term than one built around today’s best guess.

Step 3: Contractor Assignment: Match the Job, Manage the Context

Assigning the wrong contractor, or the right contractor without the right context, leads to delays and repeat visits.

Best practice:

• Maintain a vetted contractor base with skill and compliance tags. Gas Safe, NICEIC, etc alongside coverage area and current availability, so jobs go to someone who’s qualified, local, and actually free to take it on. Treat the compliance tags as something that needs keeping current, not set-and-forget. A job routed to a contractor whose registration has lapsed is a compliance gap you’ve created, not avoided.
• Where a job needs sign-off before spending, above a cost threshold, or where the landlord holds approval rights. Build the quote and approval step into the workflow itself, rather than routing straight to assignment. This is normal practice for agents without full delegated authority, and skipping it is a common source of landlord disputes.
• Where a tenant record is flagged as vulnerable, that flag should travel with the job to the contractor automatically, so they can adjust how they approach the visit. It doesn’t need to expose personal details to do that. A flag sometimes is enough. But specific context genuinely matters for the visit and the relevant people should be made aware to ensure appropriate considerations are taken.

Step 4: Communication: Keep Everyone in the Loop, Not Just Notified

Silence breeds frustration. But “automated updates” isn’t the whole answer.

Best practice:

• Automated updates at each meaningful milestone:  accepted, scheduled and completed, remove the single biggest driver of complaints: tenants chasing because they don’t know what’s happening.
• Don’t assume every tenant is equally reachable through a digital-only channel. A status link works well for most, but the process should still allow for a phone call or manual update where needed.
• Keep a comment thread against the job itself, separate from tenant-facing updates. Whoever’s responsible for the repair needs somewhere to record context. Access arrangements, a tenant’s specific circumstances, anything a contractor should know. Things that aren’t necessarily suitable for an automated tenant-facing message.

Step 5: Completion and Verification — Close the Loop Properly

A job isn’t complete until it’s confirmed complete, ideally by anyone who the repair directly impacts.

Best practice:

• Ask the tenant two direct questions: was the repair completed? & Are they happy with the outcome? You can also offer an open comment option for anything else. Separating those two gives a clearer signal than a single satisfaction score, because “the visit happened” and “the problem’s actually gone” aren’t always the same answer.
• If the answer is no, don’t close the job and raise a new one. Keep the original job open and reopen it as a remedial job. This preserves the full history against the original issue, which matters both for spotting a contractor’s true first-time fix rate and for evidencing what actually happened if the repair is later disputed.
• Require photo evidence of completed work as standard. It’s the cheapest evidence you’ll ever collect, and the most likely to matter later.
• For higher-value or higher-risk jobs, consider an independent quality check. Have someone other than the contractor confirm the work meets the standard, rather than relying solely on the tenant’s read of it. Tenants are well placed to say whether a repair addressed what they reported; they’re not always the right judge of workmanship itself.

Step 6: Reporting and Analysis: Learn From Real Patterns, Not Just Volume

Every repair is a data point. Over time, patterns emerge, but only some of them are new information.

Best practice:

• Track resolution time, cost per repair, and tenant satisfaction. But be careful not to treat first-time fix rate and repeat-repair rate as two independent signals. They largely measure the same underlying failure. A job that didn’t actually fix the problem. They are just captured at different points: one at the visit, one weeks later when the fault reappears. Track both if useful, but don’t present them side by side as if they’re telling you two different things.
• Segment by property, not just contractor. A property generating three or four times the average repair volume of similar assets usually isn’t a maintenance problem; it’s a capital investment case. Reporting that stops at “which contractor is expensive” misses the more strategic insight sitting in the same data.
• Use the data to change a decision, not just to describe one. A dashboard that shows rising costs is only useful if it feeds a budget review, a contractor conversation, or a capital works plan.

The Payoff: From Chaos to Control

No workflow removes every failure point. Contractors will still miss appointments, tenants will still be hard to reach, and some faults will still need eyes on them before anyone can say for certain what they are. A well-built process gives you a place to capture all of that properly: who decided what, when, and on what basis.

That’s the difference between an operation that can explain itself when it’s asked to, and one that’s reconstructing the story after the fact from emails and memory.