Every site manager knows the pattern: the snag list goes out, silence comes back, and two weeks later half the items are untouched. The problem is rarely bad contractors. It is a broken assignment loop. Here is how to assign snags so they actually get done.
Assign to a person, not a company
"Assign to the electrician" is not an assignment. Companies do not fix snags; people do. Every item needs a named individual who has accepted responsibility for it. When you only have a company contact, ask for the name of the person who will attend, and record that name against the snag.
This single change transforms follow-up. Chasing "the electrician" means ringing an office and hoping. Chasing a named person means a direct conversation with someone who knows they are accountable.
Give every assignment four things
A snag assignment that gets actioned contains:
- A complete description with photos, so no site visit is needed just to understand the job.
- A location precise enough to walk straight to.
- A due date, agreed rather than imposed where possible.
- A priority, so contractors can sequence their visit sensibly.
Batching matters too. Contractors respond far better to one organised list of twenty items in the same block than to twenty separate messages over two weeks. Group snags by trade and by area before you send them.
Make acceptance explicit
An assignment is not real until it is accepted. Whatever system you use, there should be a moment where the contractor confirms they have the item, understand it, and have committed to the date. That confirmation is what you refer back to when the date slips.
If a contractor goes quiet after assignment, treat it as not accepted and chase immediately, not at the due date.
Track status visibly
You cannot manage what you cannot see. Keep one live view of every snag and its state: open, in progress, or complete. Review it on a fixed rhythm, daily on a busy close-out, and chase anything that stalls.
Avoid tracking status in your head or in private notes. When the whole team can see the same list, contractors know their items are visible, and that visibility alone improves response times.
Verify before you close
A contractor saying "done" is a claim, not a completion. Every closed snag should be verified, ideally with a completion photo and, for significant items, a re-inspection. Closing items on trust is how the same defects reappear at the final walkthrough, when fixing them costs ten times more.
Keep the evidence. If a dispute surfaces months later during the defects liability period, the photo record of what was fixed and when is worth more than any email chain.
Escalate with facts, not frustration
Some items will still slip. When they do, escalate with the record: assigned date, agreed date, number of chases, current status. Facts move contracts and senior managers in a way that frustration never will.
SnagCore is built around this exact loop: assign to a named contractor, track status live, and collect completion photos and sign-offs in one place. Start a free trial and run your next close-out through it.
Assignment is not admin. Done properly, it is the mechanism that turns a list of problems into a finished building.