Triaging reported issues: building a facilities helpdesk that works

It's tempting to focus improvement effort on the engineers doing the actual repair work, since that's the visible, technical part of maintenance. In practice, a lot of the delay in reactive maintenance happens earlier — in how an issue gets reported, categorised and routed before anyone technical even sees it. Fixing triage often does more for overall speed than anything downstream of it.

What good triage actually captures

A report that just says "there's a problem in the kitchen" forces whoever picks it up to spend time working out what's actually wrong before they can even decide who should fix it. Good triage captures location, a clear description of the symptom, and an honest urgency assessment at the point of intake — not after a follow-up call that could have been avoided with a slightly better initial form.

Who's allowed to set urgency matters

There's a real tension in letting whoever reports an issue set its own urgency — everyone's own problem feels urgent to them, understandably, which can flood the urgent tier with issues that don't genuinely belong there. A workable middle ground gives the reporter a limited, honest set of urgency options with clear definitions, rather than an open text field or an unrestricted "mark as emergency" button that gets used defensively.

• –A short, structured intake form beats a free-text email or a verbal report passed along secondhand
• –Location and symptom captured clearly enough that the right trade can be identified without a follow-up call
• –A limited, well-defined set of urgency options, not an open field anyone can inflate
• –Automatic routing to the right team or contractor category based on what's actually been reported

Triage at scale, across multiple sites

Triage gets harder, not easier, as an estate grows — more reporters, more buildings, more variation in how issues get described. A multi-site facilities team needs triage that works consistently regardless of which building the report came from, which usually means a single shared intake process rather than each site handling reports its own way.

Good triage is really the first stage of the work order lifecycle, and it disproportionately determines how well the rest of that lifecycle runs — a well-triaged job moves faster through every stage that follows, while a vague one drags at every single one.