Datacat

Insights

2026-11-13 · 6 min

When every site marks its repair urgent

When every site calls its repair urgent, the loudest request can go ahead. Set shared priority levels by consequence so the serious faults are fixed first.

Picture two repair requests arriving from different sites on the same morning. One is a flickering light in a storeroom. The other is a cool room running above its safe temperature. Both are marked urgent, and the contractor takes whichever arrived first.

Both requests carry the same word, but only one can spoil stock or put someone at risk. The label doesn’t tell anyone which job should go first.

Why “urgent” stops meaning anything

Priority labels wear out when there is no shared rule behind them. Reasons to look for include:

  • Each site defines urgency for itself. A busy manager calls anything that annoys customers urgent, while a quieter one under-reports a real hazard.
  • Urgent is the only way to get attention. If routine requests sit untouched, people learn to escalate everything.
  • The label describes the mood, not the impact. The request says how the reporter feels, not what happens if the fault stays as it is.
  • Nobody checks the label. Whatever the site picks goes straight to the contractor unchanged.

Your own request history will show whether these apply.

Grade each fault by what it puts at risk

Replace the single urgent flag with a short set of levels tied to consequence. A workable starting point:

  • Safety or security. Someone could be hurt, or the site can’t be secured. Make it safe immediately.
  • Stops trading or service. Customers can’t be served, stock is at risk or a critical system is down.
  • Degrades the site. Things still work, but comfort, appearance or efficiency is suffering.
  • Can wait for a scheduled visit. Minor defects that can be bundled with the next planned job.

Give each level a target attendance window that you agree with your contractors, and write two or three real examples under each one. Examples help a site manager choose a level at a glance.

Let the site describe it and operations decide the level

Ask the site to report what they see, with a photo and a plain answer to one question: what happens if this waits a day? Then have someone in operations confirm the level before the job reaches a contractor. Sites stay responsible for reporting quickly; operations stays responsible for the order work is done in.

When the answer is “someone could get hurt”, the site should not wait for operations at all. Write down the immediate steps, such as isolating the area or calling the nominated after-hours contractor, and log the job afterwards. After-hours callouts without the blank-cheque invoice covers how to keep those overnight jobs scoped.

Work the list from the top, across every site

Once levels mean the same thing everywhere, put every open job from every site into one view sorted by priority, then by how long it has been waiting. The contractor’s next job becomes the highest-risk fault in the network, not the one from the site that rang loudest. Multi-site maintenance in one queue explains why per-site lists hide this order in the first place.

Watch the bottom of the list too. Low-priority jobs that wait too long can come back as higher-priority faults, so set a point where an old job is reviewed and either booked or bundled with planned work.

Audit thirty requests against the new levels

Take the last thirty repair requests across your sites. For each one, note the label the site gave it, the level it would get under consequence-based rules, and how long it actually waited.

If high-risk faults waited longer than low-risk ones, or one site marks nearly everything urgent, you have found where to start: retrain that site with examples, or tighten who can confirm a level.

Serious faults first in OpsChase

OpsChase is one AI-powered platform for multi-site operators, with scheduling, jobs, assets and planned maintenance, and compliance available. Sites raise the fault with a photo and set its priority. Each site’s list of open jobs is sorted by priority and due date, and head office sees every site on one board. Jobs go to your own team or your regular contractors, and a job can’t close until the proof you require is attached, so you can see which level each fault was given and how long it took. Datacat’s OpsChase overview shows how it fits multi-site maintenance.

Datacat can set up priority levels, examples and work order templates in OpsChase as part of a preferred contractor and work order system built around your sites. See work we have delivered, or send us three requests your sites marked urgent and we’ll show how they would be graded. Remove names and other sensitive details before sharing.