Triage Maintenance Requests by Evidence, Not Adjectives
Replace urgency words with a triage record that separates safety, habitability, access, and routine repair decisions.
By PortfolioRental Editorial Team · · Updated 2026-10-22
In this article
A resident writes "urgent" in the subject line. Another writes "no rush" about a leaking fixture. If the coordinator triages by the adjective, the queue inverts: the loudest request gets dispatched first, while a quiet habitability issue waits until it becomes expensive.
Quick Overview
Triage works when it records conditions and consequences instead of adjectives. Capture the same facts for every request, sort by consequence, and close only when the repair is verified and the resident is informed.
Evidence-based triage replaces adjectives with a short set of recorded facts. The coordinator does not diagnose the repair. The coordinator establishes what is happening, where, since when, what is affected, and who can provide access.
Ask the Same Questions Every Time
A consistent intake form is the backbone. For each request, capture:
- Property, unit, and the person reporting
- The observable condition, in the resident's words
- When it started and whether it is worsening
- What is affected: water, heat, power, security, access, or a single fixture
- Whether anyone is at risk or the unit is uninhabitable
- Access availability and any pets or restrictions
- Photos or video, where the resident can provide them safely
- Prior related requests and their outcomes
The form should allow "unknown" as an answer. Forcing a resident to guess produces false precision.
Sort by Consequence, Not Volume
A practical triage scale:
- Immediate safety or habitability risk. No heat in freezing weather, sewage backup, active water intrusion, exposed wiring, or a lock that does not secure the unit. Escalate to the responsible manager now.
- Damage that grows while waiting. Active leaks, roof openings, or a failure that will affect other units. Dispatch or mitigate the same day.
- Loss of a normal function. No hot water, a broken appliance, or a non-securing window in a low-risk context. Schedule within the service standard.
- Cosmetic or convenience. A dripping tap, a scuff, or a request for an upgrade. Batch with the next routine visit unless it worsens.
The scale is a routing tool. Only the qualified decision maker determines legal habitability obligations and repair responsibilities.
Record the Decision and Its Basis
Every triage decision should show the category, the reason, the next action, and the owner. If the decision is "routine", say why: the condition is contained, the resident has an alternative, and the service standard allows the date. If the decision is "emergency", say what fact triggered it.
This matters when the same resident calls again after a shift change. The next coordinator should not re-interview the resident to reach the same conclusion.
Use Vendors According to Scope, Not Habit
Match the trade and the authority. A general handyman should not be sent to diagnose a gas smell. A vendor without the required insurance or license should not be dispatched to work that requires either, regardless of availability.
Where the lease or management agreement sets a spending threshold, record the approval before work begins. Emergency mitigation may allow a lower threshold with a retrospective review, but that path must be written down in advance, not invented during the call.
Keep the Resident Informed Without Overpromising
A useful update has four parts: what we recorded, what happens next, who will contact them, and when. Avoid predicting a completion date before the vendor confirms a window. If the situation is unsafe, give the approved interim guidance rather than improvised repair instructions.
When a resident reports a condition that could affect neighboring units, tell them what to expect: a vendor visit, a possible water shutoff, or an inspection. Surprise access attempts create complaints even when the repair is correct.
Close on the Outcome
An item is not complete because a vendor visited. It is complete when the repair is verified, the resident confirms the result or a follow-up is scheduled, the invoice is linked, and any warranty or recurrence note is recorded.
Track repeat requests on the same fixture or system. A second call about the same leak within a short period is a signal that the first repair did not address the cause. Route it to review rather than dispatching the same scope again.
Review the Queue for Balance
Once a week, sample the open queue and check three things: every urgent item has an owner and a next date, no routine item has aged past the service standard without a reason, and no resident has an open request with no recorded communication. These checks catch the failures that a status count hides.
Adjectives are how people express frustration. Evidence is how an operation decides what to do. When the triage record captures the condition, the consequence, the access, and the decision, the queue becomes defensible and the residents get consistent answers.
Common Mistakes
- Dispatching by the word 'urgent' instead of the condition. The loudest message is not always the highest consequence.
- Marking a request complete because a vendor visited. Completion requires verification and a resident update.
- Sending the same vendor back for a repeat failure without reviewing the first visit. A recurrence is a scope or diagnosis question.
Common Questions Answered
Can a coordinator decide whether a unit is habitable?
No. Record the facts and escalate to the responsible manager or qualified reviewer. The coordinator's role is routing and evidence.
What if the resident cannot provide photos?
Record that the images are unavailable and rely on the described condition plus the vendor's on-site findings. Do not imply the photo exists.
When should an emergency approval be used?
Only within the written emergency path, with the reason, the amount, and the retrospective review recorded.
Ready to Put This Into Practice
Connect intake to the vendor certificate register before dispatch, and use the shared inbox guide to keep requests from being lost across channels. For housing program context, see HUD.