A snag list with two hundred items and no priorities is not a plan. It is a wall of noise that contractors skim and site managers dread. Prioritisation turns the list into a sequence: what gets fixed first, what can wait, and what genuinely blocks handover. Here is a framework that works on real projects.
Why prioritisation fails
Most teams either skip priorities entirely or mark everything high. Both fail for the same reason: if everything is urgent, nothing is. Contractors learn to ignore the labels, and the genuinely critical items drown in the noise.
Good prioritisation is honest and sparse. A list where ten percent of items are critical is useful. A list where eighty percent are is a cry for help.
The four-level framework
Use four levels, each with a plain definition everyone on the project can repeat:
- Critical: safety issues, water ingress, anything that blocks occupation or handover, and defects that will get worse or more expensive if left. Examples: a leaking shower waste, a failed fire door, no heating in December.
- High: functional defects that affect normal use and items the client will notice immediately. Examples: windows that do not lock, a kitchen tap with no hot water, damaged flooring in the entrance hall.
- Medium: visible cosmetic defects in main living areas and anything that must be fixed before handover but is not urgent today.
- Low: minor cosmetic issues in low-visibility areas and items that can be scheduled into a single return visit after the main push.
Three questions to set the level
When a snag is hard to place, ask three questions in order:
1. Does it affect safety, weather-tightness, or security? If yes, it is critical. 2. Does it stop the space being used as intended? If yes, it is high. 3. Will the client see it in the first five minutes? If yes, it is at least medium.
Everything else is low until circumstances change. Circumstances do change: a low item becomes critical the day before a client walkthrough if it is in the entrance hall.
Priorities drive sequencing, not just labels
The point of prioritising is to shape the work. Critical items get same-day assignment and daily chasing. High items go out in the first batch to each trade with agreed dates. Medium and low items get batched into efficient return visits, grouped by area and trade so one visit closes many items.
Review priorities weekly. As handover approaches, the threshold tightens: items that were comfortably medium in month two become high in the final fortnight because the programme no longer has room for them.
Make the priority visible
A priority hidden in a notebook helps nobody. Every snag should carry its level where the assignee can see it, so a contractor scanning their list knows where to start. In SnagCore every snag carries a priority from low to critical, and you can filter the whole project by it, which makes the weekly review a five-minute job instead of a morning. Try it free.
The discipline that matters most
Prioritisation only works if someone owns it. Nominate one person, usually the site or project manager, as the only one who sets and changes levels. Democratic prioritisation drifts upward until everything is critical again. One owner keeps the scale honest, and an honest scale is what makes contractors trust it.