How to Handle Tenant Maintenance Requests Without Being On Call

A landlord with a small number of commercial units occupies an awkward position: too few tenants
to justify a managing agent, too many to run on memory, and no separation between the phone that
takes tenant calls and the phone that is next to the bed.

The result for most people is a state of low-grade permanent availability, where every request
feels urgent because it arrived directly and personally.

That is fixable, and the fix is mostly about setting expectations rather than about tooling.

One channel, stated in writing

Pick a single route for maintenance requests and tell every tenant what it is, in writing, at the
start of the tenancy and again whenever it changes.

A dedicated number, an email address, or a messaging thread all work. What does not work is
"contact me" with no further definition, which resolves in practice to whichever of your
contact details the tenant happens to have and whichever they think will get the fastest
response.

Requests scattered across a personal mobile, a work email and a social account cannot be
tracked, and the ones that go missing will be the ones you least want to miss.

Define the emergency route separately, and narrowly

Alongside the normal channel, define what constitutes an emergency and what to do about one.

Be specific about what qualifies: things that are unsafe, things causing active damage, things
that stop the tenant trading entirely. Give those a different route — a phone call rather than a
message — and make clear that the normal channel is not monitored outside working hours.

Tenants are overwhelmingly reasonable about this when it is stated in advance. What produces
out-of-hours contact about a dripping tap is the absence of any stated distinction, which leaves
each tenant to invent their own.

Acknowledge fast, act at your own pace

Acknowledgement and action are different commitments and it is worth separating them explicitly.

A same-working-day acknowledgement is achievable and it is what most tenants actually want. It
tells them the message arrived and is not sitting unread. It does not commit you to a repair
timescale.

Most tenant frustration is about silence rather than delay. A tenant told "received, I will get
a plumber this week" will wait quietly. The same tenant with no reply will chase on day two and
escalate on day four.

Record it the moment it arrives

Four fields: date, unit, what, who reported it. Then a fifth as it progresses: what happened.

With five units and a handful of requests a month, this can genuinely be a notebook or a single
spreadsheet. The discipline is writing it at the moment of receipt rather than at the end of the
week — retrospective logs have gaps, and the gaps are always on the busy days.

Triage on a rhythm, not continuously

Rather than deciding about each request as it lands, set a slot — the start of each day, or two
fixed points in the week — and go through everything new in one pass.

Batching is what makes this survivable for a person doing it alongside another job. It also
produces more consistent decisions, and duplicate reports become obvious because they are on the
same screen.

Decide responsibility once per issue type

Many requests raise the same underlying question: is this yours or the tenant's. Deciding it
afresh each time is slow and produces inconsistency the tenant will notice.

Work through the common categories once against your lease terms and write down the answer.
Then most requests are routine, and only the genuinely novel ones need thought.

Keep the history by unit

File everything against the unit rather than by date. It takes no extra effort and it answers the
question that actually matters at renewal: what has this unit cost me, and is anything recurring.

A unit that generates disproportionate requests is either a building problem or a tenant
problem, and you cannot tell which without the history in one place.

When the notebook strains

The point at which a notebook stops being adequate is recognisable: when someone else needs to
see it, when you are asked what is outstanding rather than what happened, or when you find
yourself unsure whether a request was dealt with.

A shared spreadsheet is usually the next step, and it is a bigger improvement than it sounds.
The columns do not change.