"Touch up paint in hall." "Door not right in bedroom 3." "Bathroom issue." Every site manager has received snags like these, and every one of them triggers the same wasteful loop: a phone call, a site visit to find the actual problem, and a delayed fix. The solution is not more effort. It is a standard for how defects get described.
Why vague descriptions cost real money
A defect description is a work instruction. If the person receiving it cannot act on it without calling you, the description has failed. Each unclear snag adds a round trip of questions, and on a busy project with hundreds of snags, those round trips consume days of management time.
Worse, vague descriptions make disputes easy. "Fixed the door" means something different to the joiner who adjusted the hinge and the manager who expected the scratched face replaced.
The five-part standard
Train your team to write every snag with the same five elements:
1. Location: plot, floor, room, and position in the room. "Plot 14, first floor, bedroom 2, wall left of window." 2. Defect: what is wrong, stated plainly. "300mm horizontal crack at ceiling joint." 3. Measure or extent: size, quantity, or spread where relevant. "Two tiles cracked" beats "tiles cracked". 4. Expected outcome: what done looks like. "Fill, sand, and repaint to match surrounding finish." 5. Evidence: a photo, wide enough for context and close enough for detail.
With those five parts, a contractor can price, plan, and fix the item without contacting anyone.
Build a shared vocabulary
Teams describe the same defects in wildly different ways. One person's "scuffed" is another's "scratched" and a third's "damaged". Agree on standard terms for your most common defects and use them consistently. Many teams align on simple categories: cosmetic, functional, incomplete, and damage, plus a priority scale everyone applies the same way.
Categories and priorities only work if everyone shares the definitions. Write them down, keep them short, and pin them where the team actually works.
Use templates to enforce the standard
The fastest way to standardise is to make the right way the easy way. Digital snag tools let you capture location, description, photo, category, and priority in a fixed structure, so every entry is complete by default. In SnagCore, every snag carries the same fields and a photo, which means the standard holds even when a new starter logs their first defect. Try it free and see how much cleaner your list reads.
Review and coach
Standards slip without feedback. Spend ten minutes a week scanning new snags for the five parts. When you find a vague one, send it back with a better example rather than fixing it quietly. Teams learn fast when the feedback is specific.
The payoff
Standardised descriptions mean fewer phone calls, fewer repeat visits, faster fixes, and far fewer arguments about what was agreed. It is one of the cheapest quality improvements a construction team can make, and it starts with the next snag anyone on your team writes down.