Skip to content
Field Notes

Field Notes

The maintenance request isn't the problem. The triage is.

Every maintenance request arrives marked urgent. Inside the property management companies we built for, the real job was never the repair. It was triage: deciding which requests are real, who owns them, and in what order.

Mainvale · · 9 min read
Many identical-looking signal lines arriving from the left, converging at a single triage node, then leaving sorted into prioritized channels of different weights: undifferentiated requests being triaged and routed.

A message lands on a Tuesday morning: the air conditioning in a unit has stopped working. No photo. No model number. No note about whether anyone is home, whether there is a dog inside, whether it is the whole unit or one warm room. Three words and an implied exclamation point. By the afternoon the queue is full of messages just like it, each one sent by a person for whom theirs is the only one that matters. Not one of them is a repair yet. Every one of them is a decision waiting to be made. Spend a week watching this and you stop seeing a maintenance business. You see a business about decisions.

”Urgent” means nothing until someone triages it

Every request arrives urgent. That is not a complaint about tenants, it is simply the only vantage point a tenant has. A flickering hallway light and a flooding bathroom come through the same channel, in the same tone, both expecting the same response. The word stops carrying information the moment it is attached to everything.

So the first real act of the job is to take a pile of items that all claim priority and decide which ones actually have it. What is an emergency. What is same-day. What is this-week. What is not the company’s responsibility at all. Until that call is made, nothing downstream can happen, and it is invisible work: no tenant ever sees the triage that decided where their request landed.

The request is never complete

Almost nothing arrives ready to act on. The AC message has no access instructions. A reported “leak” says nothing about whether it is a drip or a ceiling. The unit is identified by a first name. Before anyone can move, a person has to finish the request the tenant started: establish what is actually wrong, how serious it is, where exactly, and how a technician gets in.

We watched managers spend more of the day completing requests than dispatching them. This is the part that is consistently underestimated. The ticket, as it arrives, is not the work. Turning a vague message into something a vendor can act on is the work, and it happens before the repair is even on the table.

The owner, vendor, tenant triangle

A central hub node with incoming lines on the left fanning out to several distinct destination clusters on the right: a single request routed to the right place among many.

A repair looks like a two-party event: something breaks, someone fixes it. In practice every request sits inside a triangle. The tenant wants it solved now. The owner is paying for it and usually has rules about how their money gets spent, a spending threshold, a preferred vendor, a standing “call me before you send anyone.” The vendor needs a clean, approved, scheduled job before they can lift a tool. The property manager stands in the middle of those three corners, translating between parties who rarely talk to each other directly and frequently want different things.

Most of what a manager does is not the repair. It is moving the right piece of information to the right corner of that triangle in the right order: confirming the problem with the tenant, checking it against the owner’s rules, packaging it for the vendor. Get the order wrong and the same request can bounce around the triangle for days without anyone doing anything wrong.

Why requests stall before a vendor ever sees them

Ask a firm where maintenance delays come from and they point at vendors: slow trades, booked calendars, no-shows. Watch the requests themselves and the picture moves upstream. The stall usually happens before any vendor is contacted at all.

A request holds because a detail is missing and no one chased it. It holds because no one is sure who owns the next move. It holds because it needs an owner’s approval that no one has asked for. It holds because its real priority was never decided, so it quietly lost out to whatever was louder that hour. And mostly it holds because it is invisible, sitting in one manager’s inbox where no one else can see that it is stuck. The vendors were rarely the problem. Once a job reached them clean and approved, it moved. The delay lived in the triage, in the part of the process nobody was looking at.

What structured intake changed

A tangled bundle of lines on the left resolving into a few clean, ordered, parallel priority lanes on the right: requests categorized, prioritized, visible, and owned.

The improvement did not come from a cleverer dispatcher. It came from forcing every request through the same front door. When intake captures the unit, the access details, the severity, and a photo before anything else moves, the request arrives actionable instead of half-formed. Once categorized, it can be prioritized by something other than who shouted loudest. On a shared board, it has an owner and a status the whole team can see at a glance. Carrying each owner’s rules, it routes and clears approval without anyone reciting the rule from memory.

The repair did not get faster. The decision did. Triage stopped being something that happened privately inside a dozen separate inboxes and became a structured, owned step that anyone on the team could watch in motion.

The line we kept human

Structure is excellent at routing and useless with people, so that is exactly where we drew the line. The system categorizes, prioritizes, attaches context, applies the owner’s standing rules, and puts the right request in front of the right person. It does not handle the resident who is angry and a little scared. It does not mediate a dispute between a tenant and an owner, make the call on a borderline expense, or tend the relationship that keeps an owner with the firm year after year.

Those stayed human on purpose. Clearing the routine routing was never about replacing those moments. It was about removing enough noise that there was room left for them.

Property management is a prioritization business

Spend enough time inside these firms and the job stops looking like maintenance and starts looking like sorting. The best-run companies were not the ones with the most vendors or the fastest trades. They were the ones that could take a flood of identical-looking requests and reliably get the right one to the right person at the right time, with the information already attached. The repair was never the hard part. Every request arrives urgent. Triage decides what is real, and the firms that understood that were quietly running a prioritization business that happened to involve buildings.

Related: how we approach AI for property management companies: structure the triage, then let the routing run itself.

Book a free AI audit.

30 minutes with senior builders. Leave with a prioritized plan, yours to keep.

  • Free, no obligation
  • A plan you keep
  • Senior people, not sales