How do you build a quality escalation ladder?
Write down the rungs, and write down the triggers that move an item between them. Observation, fixed and photo-verified. Repeated or ignored, it becomes a site instruction. Confirmed as non-compliance, it becomes an NCR. Unresolved at handover, it blocks completion. The triggers are the part everyone skips — and without them you are not running a ladder, you are running a mood.
Start by admitting the taxonomy is convention
Observation, snag, NCR — none of this is codified anywhere. The distinctions are convention, and they vary from project to project. That is worth saying out loud, because it is the reason the ladder has to be published rather than assumed.
Roughly: an observation is an early, minor or unclear issue, corrected quickly with no formal QA machinery. An NCR is confirmed non-compliance, carrying containment, root cause and verified closure. A snag is a minor defect at or near completion. But if your project has not written down its own version, two people on it are already using the words differently.
The triggers are the whole system
A rung is easy. A trigger is what makes the ladder work: the stated condition that moves an item up. Typically three of them — repetition, being ignored past a due date, or an investigation confirming actual non-compliance.
Publish them, and escalation becomes a rule anyone can predict and nobody can argue with. Leave them unstated, and escalation becomes a function of who is annoyed this week.
Escalating by mood fails in both directions at once
This is the part worth understanding, because the two failure modes look like opposites and are actually the same failure.
A project with no triggers produces paper wars — everything becomes an NCR, because raising one is how you make people take you seriously. And it produces buried problems — nothing becomes an NCR, because raising one is politically expensive. Both happen on the same site, in different corners of it, and both are symptoms of the same missing document.
References
- module: /modules/site-observations/ — observation/snag/NCR taxonomy and escalation triggers
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting