Triaging Building Issues by Priority
A defensible priority model for building issues: severity against urgency, four levels with response times, and a written reason for every single downgrade.
Key takeaways
- Issue triage property decisions rest on consequence and time, not on who complained loudest.
- Score severity against urgency, then set four levels with response times attached.
- Any downgrade needs one written line saying why, and a name beside it. That line is what makes triage defensible a year later.
- Four things never get triaged down: life safety, water near electrical equipment, a structural concern, and a gas smell.
- Audit your own triage monthly on a sample, and compare how two managers score the same three issues.
Why does issue triage need a model rather than instinct?
Because instinct is not reproducible, and a portfolio needs decisions that survive a change of manager, a complaint to the owner and an insurance review. Two experienced managers looking at the same leaking pipe should reach the same priority, and without a written model they often do not.
Issue triage in property management is the process of sorting incoming issues by how bad the outcome could be and how fast it will get worse, then assigning a response time. It is not the same as a work-order queue, which is sorted by who is available next. A queue is a schedule; triage is a judgement about consequence, made once, in writing, before the schedule takes over.
The cost of no model is predictable. Whoever calls three times gets service; the quiet tenant on level 2 waits. And the capital plan fills with problems that were someone's low priority for four years.
What questions does a priority model actually ask?
Three. How bad could this get, how fast is it getting worse, and how hard is it to reverse?
Severity is the worst credible outcome, not the most likely one. A small damp patch under a sink is minor until you notice it sits above a distribution board. Urgency is the rate of change: a seep stable for a month differs from a stain that grew overnight. Reversibility is the cost of waiting — the difference between a wet carpet and a replaced floor can be a few hours.
CCOHS frames risk assessment as risk equalling probability times severity, with priority set by ranking those scores. A building manager needs the same arithmetic with one adjustment: add rate of deterioration, because a burst pipe at 2 a.m. is not a probability question, it is a clock.
How do you build a four-level scale?
Four levels, each with a response time, a named responder and examples from your own buildings. Four sorts a portfolio and is easy to remember.
| Level | Definition | Response and attendance | Typical examples |
|---|---|---|---|
| P1 — critical | Risk to life, or damage escalating now | Acknowledge 15 minutes, attend within 1 hour — critical | Fire alarm, gas smell, water at electrical equipment, no heat below freezing, person trapped |
| P2 — urgent | Integrity at risk within 24 hours, or a service that stops occupancy | Acknowledge 1 hour, attend within 4 hours | Burst pipe in a service area, exterior door not securing, elevator entrapment, sewage backup |
| P3 — routine | Defect affecting comfort, appearance or one tenant's use | Acknowledge 1 business day, attend within 3 days | Failed light fitting, damaged ceiling tile away from services, door closer out of adjustment |
| P4 — planned | Cosmetic or preventive, no likely deterioration soon | Schedule in the next cycle, within 10 days | Scuffed paint, worn stair nosing, signage replacement |
Two rules keep the scale honest. Response time runs from when the issue was reported, not when someone read it. And P1 and P2 get a person, not a form; a ticket acknowledgement is not a response to a flood.
Why is severity different from urgency?
Because a high-severity issue can be stable, and a low-severity issue can be spreading. Severity decides who gets called; urgency decides how fast.
A cracked window in a storeroom is severity-low and urgency-low, until the wind changes. A slow drip into a tenant's ceiling is severity-medium but urgency-high, because the ceiling will fail before the leak is fixed. An accessible entrance that will not open is low by repair cost and high by impact, because some occupants cannot enter — impact on people belongs inside severity, not beside it.
This is why one number is not enough. Score severity and urgency separately and read the level off a small matrix. When they disagree, urgency wins the response time and severity wins the escalation.
How do you make triage defensible?
Three habits, all documentary.
- Criteria in writing, visible to whoever takes the call. A one-page rubric beats a philosophy, and it lets a new coordinator triage on day one.
- One line of reasoning for any change. If an issue drops from P2 to P3, the record says why — "tenant away two weeks, access arranged" — with a name and a date.
- No silent reclassification. The level can change as facts arrive; the change is logged, not overwritten. An issue that quietly moves from urgent to routine is the one that later looks ignored.
The purpose is not paperwork. It is that when an owner asks why the roof leak was handled in March and the paint in July, the answer sits in the record rather than in someone's recollection.
What should never be triaged down?
Four categories, named in the rubric as automatic top priority, whoever reports them and however minor they sound.
- Anything touching life safety — fire alarm faults, blocked exits, failed emergency lighting, damaged fire doors — critical.
- Water near electrical equipment, or anything that could energise a wet surface — critical.
- Structural signs — a new crack, a sagging ceiling, movement at a bearing point — critical, and a trigger for specialist assessment rather than a repair ticket.
- Any smell of gas, or a suspected refrigerant or combustion leak — critical.
Two more belong at P1 in practice: no heat in freezing weather, and a single working elevator where others serve an accessible route.
Scope note: Diagnosing structural movement, fire system faults, gas leaks and electrical faults is licensed work. Triage decides how fast someone qualified attends; it does not decide that the manager will assess it. Isolate, secure, call, record.
How do you triage a backlog when everything is urgent?
Re-score rather than re-prioritise, because a backlog of urgent items is usually a backlog of unscored ones. Apply the rubric to every open item, then sort by level and by age within the level.
The output is uncomfortable: a long P3 and P4 tail sitting behind two or three genuine P1s nobody noticed were old. Fix those first, then bulk-decide the tail — schedule it, defer it with a date, or cancel it with a reason.
Where the backlog is structural rather than clerical, the honest answer is a resource decision, not a re-sort. Operational risk registers are the right home for recurring items you are choosing to live with, because a risk accepted on purpose is a different thing from a request dropped.
How does triage interact with the rest of the workflow?
Triage sits between intake and assignment, and everything downstream inherits its decisions. A wrong level produces the wrong response time and the wrong closure target, which produces a metric that looks like a performance problem but is a scoring problem. That is why the intake fields in service request workflows need a priority at triage rather than at assignment.
It also interacts with safety reporting. An issue triaged as routine that later causes an incident should have been visible as a near miss — the pattern in incident reporting for buildings.
How do you audit your own triage?
Three checks, monthly, on a small sample.
Re-score ten closed issues from the record as though you had never seen them, and compare with the level assigned. A mismatch rate above 20% means the rubric is unclear, not that the team is careless. Next, ask two managers to score the same three live issues in a 20-minute calibration session; disagreement on severity is normal, disagreement on urgency usually means the rubric lacks examples. Finally, check the age of open P1 and P2 items — any P1 older than its response time is a process failure worth naming.
Do not watch the mix of levels. A portfolio with many P1s may simply be triaging honestly. The measure that matters is whether response times are met at each level, one of the metrics worth carrying into inspection metrics for managers.
Where does the manager's remit end?
Triage is a management judgement with a hard boundary. You decide how urgently a qualified person must attend. You do not decide whether the gas is leaking, whether the wall is structural, whether a panel is safe to reset, or whether water has reached the electrical room.
The same boundary applies to cost. A P1 decision at 3 a.m. is made by whoever is on call within a written authority limit, and reviewed the next morning. A triage model that needs a manager's approval before a plumber attends is not a model; it is a delay with a form attached. The wider operating context for both is set out in property management operations.
Frequently asked questions
What is the difference between priority and severity?
Severity is the worst credible outcome if nothing is done. Priority is the response level, which combines severity with urgency. A high-severity, stable issue can rank below a medium-severity issue that is deteriorating fast.
Who should assign priority?
The person who takes the report, using a written rubric, with P1 and P2 checked by a second person within the hour. Triage by committee is slower and no more accurate.
How many priority levels should we use?
Four: critical, urgent, routine and planned. Three lose the distinction between comfort and appearance; six produce arguments about the difference between level 4 and level 5.
What do we do when a tenant disagrees with our priority?
Explain the rubric, not the decision. Show the severity and urgency criteria, state the response time for the level assigned, and log the disagreement. If it repeats, the rubric needs another example, not an exception.
Can priority change after triage?
Yes, when facts change — a slow leak becoming visible, or access arranged for earlier attendance. The change is logged with a reason and a name rather than overwriting the original level.
Issue triage property model: a record, not a feeling
Triage holds for a year only if it is written down: two scores, four levels, response times, and one line of reasoning for every change. Once levels are recorded consistently across buildings, you can see which sites generate P1s and which describe everything as urgent — the start of an honest conversation about condition instead of noise. NeatScore gives a property manager consistent records across sites: checklist items with critical flags, a photo per item, offline inspections that sync later, branded PDF reports, deficiency tracking with owners and due dates, and dashboards that show whether the P1s close on time. Try it free for 14 days, or see pricing.
