When a checkpoint fails during an inspection, digiQC can turn that failure into an NCR (Non-Conformance Report) — a formal Issue that must be resolved and closed before the inspection can continue.
This option is available only if the digiQC team has given your organisation the right, and it works only when the Issue module is on for your organisation (the NCR is created as an Issue).
During the inspection, when a checkpoint fails, you're given a choice: Fail or NCR.
Choose NCR to raise a Non-Conformance.
An Issue is created automatically, with:
- the same location as the inspection - the checkpoint photo added automatically - type = NCR - description = the checkpoint's question, answer and remark
Assign the NCR (choose who it goes to) — this is done at the end.
The NCR gets a default deadline of exactly 2 days.
The inspection can be continued only after this NCR Issue is closed.
All failed checkpoints are grouped into a single NCR Issue. They're listed in the description in sequence, each with its checkpoint number for reference.
What details go into the NCR automatically? The inspection location, the checkpoint photo, type NCR, and the checkpoint's question, answer and remark as the description.
Who sets the deadline? A 2-day deadline is set automatically; you choose who the NCR is assigned to.
An NCR is a normal Issue of type NCR — it's responded to, verified and closed the same way as other issues.
Because the NCR blocks the inspection, close it promptly to keep work moving.
2.3.1 How does an issue work? (flow & cases)
2.2.17 Approver review — pending inspections
2.3.5 How to close an issue?
