When an issue should become an NCR

Article Quality & accountability ~8 minutes

Not every site problem is a formal non-conformance. Not every “raise an issue” should stay forever in the lighter register either. Teams that treat both tools as the same stamp lose the plot — either drowning the NCR book in noise until nobody reads it, or leaving real contractual departures looking like chat that someone might clear with a shrug.

The skill is knowing when to escalate the form of the record. That is a judgement call, not a software toggle. Contracts, quality plans, and client rules set the rails. Culture decides whether people use them when Tuesday pressure is high.

This article sits next to the closed-loop overview: once you agree that findings must leave a trail, you still need to pick the vehicle that matches the risk.

What good practice looks like

Strong quality systems usually keep two related layers — sometimes with different names, always with different weight:

• Issues / observations — capture defects, incidents, and findings quickly so the team can discuss, assign, and close everyday problems without summoning a formal CAPA ceremony for every scuff.
• NCRs — record a formal departure from requirement and drive corrective and preventive action, verification, and often an effectiveness review after the dust settles.

Good practice looks like clear thresholds and judgement, not infinite forms for every scratch. The threshold may come from the contract, the quality plan, client rules, or the principal’s procedures — but it must be teachable on site by a supervisor who did not write the plan.

In practice:

• People know what “raise an issue” is for on a busy Tuesday afternoon — and they are not punished for using it.
• Escalation to NCR is a conscious decision, with a short reason, not a forgotten checkbox or a late rebadging after an audit scare.
• Evidence travels with both — photos, drawings, linked documents — so escalating form does not mean restarting the story from zero.
• Closure language matches the vehicle: fixed and accepted versus CAPA complete and verified.
• Contractors and principals can see each other’s proportionate use of the heavy path, not parallel books with incompatible definitions of “non-conformance.”

Standards talk about nonconformity and disposition. Site language should be simpler: when does this finding change how we prove we met the requirement — and when is it workable work still under informal ownership?

Good practice protects the NCR register as a serious instrument. Diluting it with every paint dab teaches people to ignore it. Hoarding serious departures in chat teaches auditors that the system is theatre.

Where projects slip

• Everything becomes an NCR; the register is unreadable, slow, and politically loaded, so people stop raising early.
• Nothing becomes an NCR; serious departures hide inside informal issue chat until the client names them in a letter.
• Issues close with “done” and no verification; NCRs close without effectiveness thought because the programme needed green numbers.
• Escalation happens only when a third party escalates first — meaning the project’s own threshold was never active.
• Two organisations on the same package keep incompatible books: one calls it an observation, the other calls the same fact an NCR, and neither map exists when commercial workshop season arrives.
• Fear of “opening an NCR” drives under-reporting, while fear of “looking soft” drives over-formalising every stubbed toe.

The cost is not mainly clerical. The cost is late visibility: the chance to stop cascade damage, change a method, or brief the next crew disappears while people argue about which stamp feels heavier.

How Cynilo supports the practice

Cynilo keeps Issues and NCR as related but distinct trails that share sensible patterns — conversation, evidence links, workflows — without forcing every finding into the heaviest process.

Your quality plan still decides the threshold. Cynilo makes the chosen form of record easy to follow, search, and hand over. When formality increases, the story and the proof can travel with the escalation rather than living as a separate archaeology project. Help How-tos cover the buttons. Learn’s reminder: pick the vehicle that matches the risk and the contract.

The product does not replace QA judgement. It stops the operational reality — raise early, escalate honestly, close in the language you promised the client — from depending only on whoever remembers the rule book that week.

What good looks like in a week

On a job that chooses form well:

• Site raises small defects without fear of bureaucracy, and those items are visible and owned.
• Real non-conformances are visible in the NCR register with corrective action that can be inspected.
• Escalation notes explain why the form changed — enough that a stranger understands the decision later.
• Auditors can see a proportionate system, not two ignored lists or one swollen NCR book.
• Weekly quality reviews start with open risk, not with arguing whether item 47 “should have been an NCR.”

The weekly test is simple. Ask a supervisor and a quality lead independently which kinds of findings must escalate. If they give the same answer without looking at a slide deck, the threshold is alive.

A short story from a concrete package

On a civil concrete package, a pour left honeycombing against a retaining face. The site engineer raised it as an issue with photos the same evening. The trade repaired outward-facing areas before the weekly meeting. Somebody marked the issue “closed.” A week later, during a hold-point review, the quality lead realised the defective zone sat against a waterproofing interface that the quality plan treated as a formal departure whenever approval geometry was at risk.

No malice sat behind the soft close. The everyday register had been used correctly on day one; the escalation never happened because nobody owned the threshold conversation with the same urgency as the patch. When the NCR finally opened, the work had moved, the commercial questions had grown teeth, and reconstructing “what we knew when” cost more than an honest escalate would have cost on the night of the pour.

After that package the project published a one-page escalation guide beside the site office kettle — examples, not theory — and trained supervisors that raising an issue early was praised, while burying a threshold event as chat was not. Volume of NCRs did not spike. Timeliness did. The register stayed readable because noise still lived in issues until it earned the heavier path.

Closing

The closed loop in From a site complaint to a closed loop needs a vehicle. Issues keep pace with site life. NCRs keep faith with the contract. Choosing well is how both remain trusted.

Previous: From a site complaint to a closed loop