A Framework for Triaging Maintenance Requests (Without Being On Call)
The reason self-managing landlords end up permanently on call isn't the volume of repairs. It's that every request arrives through the same channel, in the same tone, with no way to tell in advance which one matters.
"The sink is leaking" could be a dripping tap or water running down inside a cabinet. Both texts look identical at 11pm. So you either treat everything as urgent, which is exhausting and expensive, or you treat nothing as urgent and eventually get the one that was.
The fix is a sorting rule you apply before you decide anything else.
Three buckets, and only three
Emergency — deal with it now, whatever time it is. The test is whether waiting causes harm to a person or fast-compounding damage to the building. No heat in freezing weather. No water. Gas smell. Sewage backing up. Active water ingress. Anything electrical that's sparking, smoking or hot. A door or window that won't lock.
Urgent — this week, in daylight. Nobody is in danger and nothing is getting rapidly worse, but the unit isn't functioning properly. One of two bathrooms out. Fridge failed. Slow leak that's contained. Heating unreliable but working. Appliance breakdowns generally sit here.
Routine — schedule it. Cosmetic, minor, or annoying but harmless. A running toilet, a sticking door, a cracked tile, a light fitting.
The value isn't the categories — most landlords could produce a similar list. It's deciding them in advance and telling your tenant, so that "emergency" means the same thing to both of you. A tenant who knows a dripping tap gets a Tuesday appointment stops texting you about it at 11pm, and — more importantly — knows that a burst pipe should be a phone call.
Put it in the welcome letter and in the lease: this is what an emergency is, this is the number for it, everything else goes to the maintenance form.
Why photos change the sorting
Text descriptions are unreliable because tenants aren't diagnosticians and aren't trying to be. "Small leak under the sink" is a genuine, good-faith description of both a dripping washer and a supply line that's been weeping for a fortnight into a cabinet base that's now swollen and growing mould.
A photo settles it in a second. So the single highest-leverage change to a maintenance process is: always ask for a photo, before you ask anything else.
SmartLeaseFlow reads those photos when they come in and turns them into triage signal — what's actually visible, which category it supports, whether the image alone justifies a higher priority, any visible hazard like water damage or exposed wiring, and what to ask the tenant before sending anyone out. "Sink leaking" becomes "sink leaking, active drip, cabinet base already swollen — same day."
Everything it produces is advisory. It adjusts a priority suggestion and adds notes. It never dispatches anyone, never charges anything, and never overrides you.
Two things it deliberately won't do
Worth stating, because both were asked for and both were cut:
It won't identify parts or materials. A vision model looking at a dim phone photo under a sink cannot reliably tell PVC from ABS from chrome-plated brass — and it will answer confidently anyway. A wrong material on a work order sends a plumber out with the wrong fittings, you pay for the trip, and the software gets the blame. It describes what's visible and stops.
It won't recommend a contractor. There's no vendor directory behind it, and building one means either licensing business data or scraping it. Recommending a specific contractor also carries liability there's no good reason to take on. You pick the vendor; it prepares the brief.
That second one is the general principle: the useful part of automation here is removing the retyping and the back-and-forth, not making the judgement calls.
What the vendor actually receives
The other half of the chaos is the dispatch conversation — four texts establishing what's broken, where, who has a key, and when they can get in.
Once you choose a vendor, the brief goes out with the problem, the address, the access notes, any hazard flagged from the photos, and the photos themselves. The tenant's phone number is included only if you choose to share it, which is the right default for a number you don't own.
It's written to be read on a phone, in a van, by someone deciding whether to take the job.
Doing this without any software at all
Most of the benefit is process rather than product:
- Publish the three buckets to your tenants, with what counts as an emergency and how to reach you for one.
- One intake channel. A form, an email address, anything — as long as it isn't four different threads across text, WhatsApp and voicemail.
- Always require a photo. This alone removes most of the ambiguity.
- Batch the routine work. Three small jobs on one visit costs a fraction of three separate call-outs, and vendors prefer it.
- Write down what was done. At move-out, "we replaced that in March" is worth having in writing — and if you're deducting anything from a deposit, in California it's not optional.
The part worth keeping for yourself
Triage is a judgement about risk, and you're the one carrying it. Software can tell you a cabinet base looks swollen and that this usually means it's been leaking a while. Deciding whether that's a plumber tonight or Thursday depends on things it doesn't know: the building, the tenant, the last three times something went wrong in that unit.
Aim for a system that gets you the right information fast, then leaves the call to you.
Repair spend also has to land somewhere at tax time — the Schedule E categories cover where repairs go and how they differ from improvements.