The Maintenance Triage Rulesheet: What Becomes a Job, What Gets Merged and What Waits

QR reporting is powerful because it makes the first report easy.

A cleaner spots a leaking tap. A hotel housekeeper photographs a damaged handle. A gym member reports a noisy treadmill. A teacher flags a loose fitting between lessons. A tenant scans a code in a communal hallway and sends a picture of a broken light.

That is exactly the kind of visibility facilities teams need. But there is a trap: if every report becomes a job immediately, the job list can turn messy fast.

Some reports are urgent. Some are duplicates. Some are useful but vague. Some should become planned maintenance rather than same-day reactive work. Some belong with a contractor. Some are observations that need a manager to check the risk before anyone is assigned.

The missing layer is triage.

A maintenance triage rulesheet gives managers a simple way to decide what happens after a report arrives. It keeps reporting easy for staff, guests, tenants, members and contractors, while making sure the team still has control over what becomes live work.

Start with the intake decision

The first decision is not "who should fix this?"

It is "what kind of thing has just arrived?"

That is why a review step matters. A public or staff-facing QR form should capture the issue quickly, but the manager should still decide whether it becomes an assigned job. In SnagDeck, incoming reports can land in an issue review inbox before they appear on the live job board.

That separation protects the workflow. Reporters do not need to understand the whole maintenance process. Managers do not have to accept every scan as work.

For triage, most reports fall into one of five lanes:

• Urgent job: needs action quickly because of safety, guest impact, operational disruption or risk of further damage.
• Normal job: valid maintenance work that should be assigned and tracked.
• Duplicate: already reported or already being handled.
• Planned task: real issue, but better handled through a routine check, scheduled visit or wider maintenance programme.
• No action or reject: not enough information, not relevant, spam, or already resolved.

The rulesheet does not need to be complex. It just needs to make the first decision consistent.

Lane 1: urgent job

An urgent job is not just a report with dramatic wording.

It is a report where delay may create risk, damage, service failure or serious operational disruption. Examples might include:

• water leak affecting a public area, room, classroom or equipment
• loose handrail, damaged step or trip hazard
• faulty gym equipment that should be taken out of use
• lighting failure in an access route
• damaged fire door, where the team needs competent advice and prompt action
• broken fixture affecting a hotel room that is due to be occupied

The triage question is simple: does this need immediate ownership?

If yes, convert the report into a job, set the priority, add the location and photos, and assign it to the right person. If the area or equipment should not be used, the physical site still needs clear signage, barriers or other controls decided by the competent person. The software record should show what was reported, who reviewed it, what action was taken and who owns the next step.

HSE guidance on maintaining work equipment is clear that damaged or unsafe equipment reports should not be ignored, and that faulty or damaged equipment should not be used. Software cannot make the safety decision for the team, but it can make the decision visible.

Lane 2: normal job

A normal job is valid work that does not need emergency handling.

This is the everyday maintenance queue: loose fittings, small leaks, broken locks, damaged furniture, faulty lighting, cleaning issues, scuffed fixtures, minor equipment defects, contractor follow-ups and routine repairs.

The goal is to turn the report into a job with enough context for the assignee to act without chasing the reporter. That usually means:

• site and area
• issue category
• clear title
• original description
• photos
• priority
• assignee
• due date, if useful

This is where job management earns its keep. A job should have a status, owner, location and history. Without those pieces, the team drifts back into messages and memory.

The triage rulesheet should define the minimum information required before a normal job is created. If a report says "broken" with no photo, no location context and no category, it may need clarification before assignment. If the QR code already identifies the area and the photo is clear, it may be ready in seconds.

Lane 3: duplicate

Duplicate reports are common in physical spaces.

That does not mean the reporting system is failing. It usually means the issue is visible enough for more than one person to notice. A broken locker, blocked toilet, faulty treadmill, flickering corridor light or damaged classroom chair may be reported by several people during the same day.

The problem is what happens next. If every duplicate becomes a separate job, managers waste time reviewing the same issue and assignees may think there are several different faults.

A triage rule for duplicates should answer three questions:

1. Is there already an open issue or active job for this location and category?
2. Does the new report add useful evidence, such as a better photo or safety context?
3. Should the reporter be told that the issue is already known?

SnagDeck's duplicate detection helps reduce repeated reports before they become noise. Managers can still decide whether a new report is genuinely different, but the system gives them a warning before the job list fills with near-identical work.

Do not treat every duplicate as useless. A second report may show that the issue is more visible, more disruptive or getting worse. The key is to merge the signal, not multiply the admin.

Lane 4: planned task

Some reports should not become one-off reactive jobs.

They are real, but they point to a pattern or routine that needs a planned response. A washroom that keeps generating blocked drain reports may need a scheduled check. A hotel floor with repeated lighting faults may need a contractor visit. A school playground issue may belong in a weekly site inspection. A gym machine that keeps returning after repair may need a deeper service call.

The triage rule is: if the same issue keeps coming back, stop treating every report as a fresh surprise.

Move the work into a planned route when:

• the same asset or area has repeated reports
• the fix requires a scheduled contractor visit
• the issue is better handled as part of a routine checklist
• the team needs several related checks rather than one repair
• the work has to wait for parts, access, budget or downtime

That does not mean ignoring the current report. It means acknowledging it, recording the context and creating the right kind of follow-up. For teams using recurring maintenance templates, a repeated reactive issue can become part of a planned inspection rhythm instead of another isolated task.

Lane 5: no action or reject

Not every report deserves a job.

That can feel uncomfortable if the team is trying to encourage reporting, but it matters. A review inbox is useful partly because it lets managers keep poor-quality or irrelevant reports out of the live work list.

Reasons to reject or close without action might include:

• obvious spam or misuse
• report sent to the wrong site or area
• issue already fixed before review
• not enough information to identify the problem
• observation that does not require work
• request outside the maintenance team's responsibility

The rule should still be calm and traceable. If the report is genuine but unclear, the manager may add a comment explaining why it was not converted into a job. If the reporter is identifiable, the team may ask for more information. If the issue is outside scope, the manager may route it to the correct team.

The point is not to block reporting. It is to stop the job board becoming a dumping ground.

Use AI as a starting point, not the decision-maker

Messy reports are normal.

People write quickly when they are standing in a corridor, room, gym floor, classroom or stockroom. They may describe symptoms rather than causes. They may use local names for areas or equipment. They may upload a helpful photo but write a weak title.

AI can help at this stage by suggesting a clearer title, summary, category, priority and next action. That can make review faster, especially when several reports arrive during a shift.

But AI should not be the final operational authority.

The rulesheet should be explicit: suggestions are a starting point. A person still decides whether the report is urgent, duplicate, planned, assigned, rejected or needs more information. That is especially important for safety-sensitive work, contractor decisions and anything that affects whether an area or item should stay in use.

Write the rulesheet in plain language

A triage rulesheet only works if managers can use it under pressure.

Avoid legalistic wording and giant decision trees. The rule should be easy to apply during a normal shift. For example:

• If there is possible immediate risk, create an urgent job and alert the responsible manager.
• If the issue is valid and clear, create a normal job with a priority, owner and due date if needed.
• If the same issue is already open, merge the context or mark it as duplicate.
• If the issue is recurring or needs scheduled access, route it into planned maintenance.
• If the report is spam, unclear or outside scope, reject it with a short note.

Then add examples for your own environment. A school, hotel, gym, office, shop and managed property will not have exactly the same urgency rules. The value is in agreeing the judgement before the inbox is busy.

A practical triage workflow

Start with a simple routine:

1. Review new QR reports at defined points in the day, or immediately for areas where urgent issues are likely.
2. Check the location, category, description and photos.
3. Look for open jobs or recent reports from the same area.
4. Choose a lane: urgent job, normal job, duplicate, planned task, or no action.
5. Add or improve the title and priority.
6. Assign accepted jobs to a person or contractor.
7. Add comments where the decision needs explanation.
8. Review repeat reports weekly so patterns do not stay hidden.

This turns the review inbox into a control point rather than another place where work gets stuck.

The simple test

Take the last ten maintenance reports your team received and ask what should have happened to each one.

Were they all real jobs? Were two actually duplicates? Did one need urgent action? Did one belong in a planned inspection? Was one too vague to assign? Did a contractor need a better brief before attending?

If the answer depends entirely on who happened to review the inbox that day, the process is too fragile.

A maintenance triage rulesheet gives the team a shared way to make the first decision. Reports still come in quickly from the physical space. Managers still keep control. Jobs stay clearer. Duplicates create less noise. Recurring issues are easier to spot.

That is the SnagDeck approach: report the issue, review it properly, assign the right work and keep the proof with the job.

Further reading

• HSE: Maintenance of work equipment
• HSE: Inspection of work equipment
• School estate management standards