Maintenance enquiries: the day the boiler breaks

It's 8:15 on a Tuesday and the phone has already gone twice: the boiler at one of your flats has packed up. The tenant is cold and wants a time. The landlord wants three quotes before he'll approve anything. The plumber needs the access code. One repair, and the morning is now being spent passing messages between four people from memory.

The repair is one job. The admin around it is six: log the enquiry, chase the landlord's yes, text the contractor, update the tenant, confirm the appointment, report back once it's done. Every one of those relayed by hand, every one waiting on somebody. That is the loop this post is about, and businesses like yours meet the same shape in any urgent work, whatever the trade: the emergency lands, and someone's morning disappears into passing messages between people who all need an answer now.

The tenant's side is worth naming. From their side of the door, the day has no shape: they reported it, heard nothing, chased, heard nothing again. The office was never ignoring them. It was relaying, by hand, in between everything else.

The maths (a sketch, not a client figure)

Sketch one urgent maintenance job:

• 6 admin steps (log, chase the yes, text the contractor, update the tenant, confirm, report back) at about 8 minutes each = 48 minutes of relay per job
• × 3 urgent jobs a week on an average week (a bad week runs higher) = 144 minutes, about 2 hours 25
• × £30 an hour = £72 a week
• × 46 weeks = £3,312 a year of passing messages between people.

None of that includes the tenant's silence between steps, the part that turns into a bad review. On the worst days the relay is done by the owner, so the real rate is an hour of yours. Swap in your own numbers. (A sketch, not a client figure.)

Score it: the three checks

Score the loop, relaying the urgent job, on the three checks:

• Hours. 2 hours 25 a week in the sketch, concentrated on the days you can least afford it (3).
• Repeat. Each message is a template with fields: address, name, time, access arrangement. A new starter could follow it from one page (4).
• Risk-if-wrong. Updates are drafted and approved before sending, so a wrong text never reaches a tenant, and the log keeps every step in one place (4).

Two checks at 4 or more, so the verdict is start narrow. Log every enquiry in one place first; drafting comes after the log exists, because a draft is only trustworthy when written from one clean record instead of from memory.

Try one thing this week (free)

Take the last urgent job you handled and write down every message it took: who it went to, what it said, roughly how long it took. Count the minutes. That count is the case for the first thing worth handing over, because it shows the difference between the one decision (which contractor, what priority) and the six relays around it. Judge it by Friday: one page, no purchase, no new software.

Where a person stays

The office decides which job is urgent, which contractor goes, and what the landlord is told. The software drafts each update from the log: the tenant's message, the contractor's instructions, the landlord's summary. A person approves before anything sends. Nothing texts a tenant on its own, and the judgement calls, like whether a no-heating job counts as an emergency, stay with a human name on them. The software carries the passing. The people carry the deciding.

FAQ