To handle a maintenance request cleanly, move it through five fixed stages: intake, triage, dispatch, repair, and closeout. The repair work itself belongs to whoever is qualified to do it. Your part is capturing the request accurately, routing it at the right urgency, confirming it was actually finished, and leaving behind a record that still makes sense a year from now.
This article is general information for residential landlords, not legal advice. Landlord-tenant law — including habitability obligations, entry into an occupied unit, and what a landlord must do when a unit needs repair — varies by state and locality. Those questions belong with a qualified attorney licensed where the property sits.
What It Means to Handle a Maintenance Request Properly
A request is handled when four things are true: you know exactly what was reported and by whom, the right person looked at it, the condition is fixed or formally deferred with a reason, and there is a dated record tying all of that together.
Most maintenance problems are not repair problems. They are handoff problems. A tenant mentions a leak in passing, nobody writes it down, a vendor gets a vague phone description, shows up without the right part, and three weeks later the same leak is a bigger repair with no paper trail explaining the delay.
The fix is boring and it works: one intake channel, one triage rule, one written record per request.
Intake: Capture Every Request in One Place
Pick a single place requests live and route everything into it. Phone calls, texts, emails and in-person mentions all get transcribed into the same log. A request that only exists in a text thread does not exist.
Capture these fields every time:
- Date and time reported, and the channel it came in on.
- Property and unit identifier, written the same way every time.
- Who reported it and the best number or address to reach them.
- What they actually said, in their words, not summarized into your guess at the cause.
- When it started and whether it is getting worse.
- Photos or video, requested at intake rather than after the vendor visit.
- Access notes — pets, parking, gate codes, work schedules, who can let a vendor in.
- Request number, assigned at intake so every later note can hang off it.
Ask one clarifying question at intake instead of three later. "No hot water" splits immediately into no hot water anywhere versus one fixture, and that single answer changes which trade you call.
Write down what you observe, not what you conclude
"Brown stain on ceiling drywall below upstairs bathroom, roughly eight inches across, damp to the touch" is useful. "Upstairs toilet leaking" is a diagnosis you have not earned yet, and if it turns out to be a supply line or a tub surround, your record now contradicts the invoice.
Triage: How to Handle a Maintenance Request by Urgency
Triage is where you decide speed, who goes, and whether anyone needs to stop using something. Set your own tiers in writing and apply them the same way to every unit, rather than deciding case by case based on who asked loudest.
| Tier | Typical conditions | What it drives |
|---|---|---|
| Emergency | Active water intrusion, no heat in cold weather, gas odor, sewage backup, exposed wiring, no working lock | Immediate dispatch, after-hours vendor, tenant given interim safety instructions |
| Urgent | No hot water, refrigerator failure, single-bathroom plumbing out, failing smoke or CO alarm, pest activity | Next available skilled visit, tenant updated once scheduled |
| Routine | Dripping faucet, running toilet, loose fixture, slow drain, cosmetic damage, appliance quirk | Grouped with other work at the property, scheduled normally |
| Planned | Worn flooring, aging water heater, cabinet or counter replacement, repaint | Added to the capital list with a date and a condition note |
Two judgment calls sit inside triage.
Is this habitability, cosmetic, or damage? The three go down different paths. Habitability items move first, regardless of who caused them. Damage items still get repaired on the same timeline you would use otherwise, with the cost question handled separately and in writing.
Does this need a licensed trade? Gas, electrical and anything structural go to licensed trades. So does anything where a wrong guess compounds. Permit requirements and licensing rules differ by jurisdiction, so confirm locally rather than assuming.
Never instruct a tenant to attempt a repair themselves on a system you would hire a trade for.
Dispatch: Get the Right Person There Once
A dispatch that produces a second trip costs twice. Give the vendor everything in one message: request number, address and unit, the tenant's description verbatim, your photos, the access instructions, the age and model of the appliance or system if you know it, and what you want them to do versus what you want them to quote.
Say explicitly whether they are authorized to repair on the spot up to an approval threshold you set, or whether they diagnose and come back to you first. Vendors left guessing will either overstep or stall.
Coordinate access rather than assuming it. Give the tenant the scheduling window and who is coming, and ask them to confirm. Entry rules for occupied units are set by law and by the lease, and you need to know yours before anyone knocks.
Log the dispatch under the same request number: who was assigned, when, what they were authorized to do.
The Repair: What to Require Back From the Vendor
Decide what "done" looks like before the work starts, then require proof of it.
- A written description of the cause, not just the fix
- Parts replaced, with model numbers where applicable
- Photos of the condition before and after
- Any adjacent problem they noticed and did not touch
- Whether the repair is permanent or an interim measure
- An invoice that references your request number
That last item is small and saves hours. An invoice with no request number is a line item you will never match to a unit.
If the vendor recommends more work than you authorized, that becomes its own request with its own number — not an expanded version of the original. Scope creep inside one work order destroys your ability to see what anything actually cost.
Closeout: Verify, Communicate, File
Closeout has three parts and skipping any one of them is what turns a finished repair into a repeat call.
- Verify with the tenant. Ask them to confirm the condition is resolved, not just that someone came. Get the confirmation in writing, even one line.
- Check the work yourself on anything you would be embarrassed to have missed — water, heat, locks, alarms, and anything behind a wall.
- File it. Invoice, photos, vendor notes, tenant confirmation and dates all attached to the request number, in the unit's folder.
Then mark the request closed with an outcome, not just a date. "Resolved — supply line replaced," "Deferred — scheduled with flooring work," "No fault found — monitored." A closed request with no outcome tells you nothing when the same symptom returns.
Read your log, not just write it
Once a quarter, scan the closed requests per unit. The same fixture appearing three times is not three small repairs; it is one replacement you keep postponing. The same vendor needing two trips repeatedly is a dispatch quality problem. This review is the only way a maintenance log pays you back.
The value is not in any single stage. It is in running all five the same way on every request, in every unit, so that a year later you can reconstruct what happened without remembering it. One intake form, one tier chart, one dispatch template, one closeout rule.
Tax treatment of repairs and improvements is a separate question with real consequences, and it belongs with a CPA rather than a maintenance log.
To put the intake fields, tier chart, dispatch template and closeout checklist into one working packet, see the Maintenance & Vendor Management Handbook page.