Maintenance Request Workflow: From Tenant Submission to Completion
December 30, 2023A maintenance request that disappears into an inbox with no tracking is how small issues turn into tenant frustration and, eventually, habitability disputes. A consistent workflow — the same steps every time, regardless of who's handling it — keeps requests visible from submission through completion.
The typical stages
A well-structured maintenance workflow generally moves through:
- • Submitted — the tenant reports the issue, ideally through a portal rather than a scattered mix of texts and calls
- • Triaged — the request is reviewed and categorized by urgency and type
- • Assigned — a vendor or the landlord is assigned to handle it
- • Scheduled — a specific date and time is set, and the tenant is notified
- • In progress — the work is underway
- • Completed — the work is done, and ideally confirmed with the tenant
Triage: not everything is equally urgent
Sort incoming requests by priority as soon as they arrive — a broken dishwasher and a gas leak should never be treated with the same urgency. Setting priority levels (routine, urgent, emergency) at the triage step keeps genuinely urgent issues from getting stuck behind a queue of minor ones.
Keeping the tenant informed
A tenant who submits a request and hears nothing assumes it was ignored, even if it's actually scheduled. A quick update at each stage — acknowledged, scheduled, completed — costs little and prevents a lot of frustration and follow-up calls.
Closing the loop
Mark a request complete only after the work is actually done and, where practical, confirmed with the tenant. A request that's technically finished but never marked complete in your system creates confusion the next time something comes up in that unit.
Frequently Asked Questions
Should tenants submit maintenance requests through a portal or by text?
A portal creates a searchable, timestamped record, which is far more reliable than a scattered mix of texts, calls, and emails — especially if a dispute comes up later.
How should I prioritize multiple maintenance requests at once?
Sort by urgency first — safety and habitability issues (no heat, active leaks, electrical hazards) ahead of cosmetic or convenience issues — rather than handling requests strictly in the order they arrived.
What happens if a maintenance request is never marked complete?
It creates confusion later — either you lose track of whether it was actually finished, or the next issue in that unit gets conflated with the old, unresolved request.