Fictional worked example · NCR-TRAIN-001
A missing inspection record.
A response that can be checked.
Follow a fictional dispatch-bay finding from containment to independent closure. Expand each stage to see the decisions and evidence a team might record.
Training illustration only. The company, people, procedure and evidence below are invented. This public walkthrough does not load or save client records.
The starting point
At fictional Northbank Engineering, an audit finds that three sampled dispatch-bay shifts have no retained inspection record. The internal training procedure, NB-TR-04, requires a recorded route inspection before each shift. The missing record establishes a gap in evidence; it does not by itself prove that an inspection never happened.
Owner
Alex Morgan, dispatch supervisor, owns containment and corrective delivery.
Independent reviewer
Sam Patel, assurance reviewer, checks the response independently. Alex and Sam are separate fictional accounts.
Linked records
Audit finding AF-TRAIN-001 → NCR-TRAIN-001 → Actions ACT-TRAIN-001 and ACT-TRAIN-002.
Follow the decisions
1 · Draft — establish the requirement and the facts
Requirement: retain the shift route-inspection record before dispatch starts, under the fictional local procedure.
Observed fact: three sampled shifts have no accessible record. Confirm the scope and examine other shifts before deciding how widespread the problem is.
Set up: name Alex as owner and Sam as reviewer; set a closure target and link the audit finding and affected route control.
2 · Submitted — contain the immediate concern
Alex records a fresh route check before the next dispatch operation, confirms any immediate obstructions are addressed and retains the check record. The response explains what is contained and what remains uncertain.
The owner submits the NCR and moves it to In progress. Containment does not replace cause analysis or the longer-term response.
3 · In progress — correct the gap and change the process
Correction: recover any genuine available records and clearly identify the remaining gaps. Do not invent retrospective inspection results.
Cause analysis: in this fictional example, interviews and a process review show that the revised shift handover omitted responsibility for storing the record. Evidence of this explanation is retained.
Action 1: revise the handover checklist to name responsibility and the approved storage location.
Action 2: brief the affected supervisors and sample their use of the revised process.
Effectiveness plan: after a two-week observation period, sample ten consecutive shift records. The illustrative criterion is ten complete, retrievable records, with discrepancies investigated. Real teams must choose criteria appropriate to their risk and operation.
4 · Verification — did the agreed work happen?
After the linked actions and allocations are complete, Alex requests verification. Sam checks the revised checklist, briefing evidence and initial records against the corrective plan.
Sam records a dated independent decision. If evidence is incomplete, the NCR returns to In progress with a reason. Alex cannot provide the independent reviewer decision.
5 · Effectiveness review — did the response work?
After the planned review date, Sam checks the ten fictional shift records and records the sample, results and limitations. In this illustrative outcome, all ten records are complete and retrievable.
If the agreed criterion is not met, Sam records an unsuccessful result and returns the work for further delivery. A future review date or a completed action alone cannot justify closure.
6 · Closed — retain the conclusion and learning
Sam records an Effective result, review date, supporting evidence and lessons, then closes the NCR.
Lesson: when changing a handover, explicitly review the responsibility and location for retaining evidence. Continue routine assurance; the sample does not prove that every future shift will comply.
The closed NCR and revision history remain available. If new information changes the conclusion, an authorised user reopens with a reason before changing the verified work.
What would the shared queue show?
During delivery, the actions appear with their delivery dates. When the NCR awaits effectiveness, its planned effectiveness date drives its position. After closure, the NCR remains in its register rather than the outstanding-work queue.
Try this pattern in a separate training assessment using your own authorised test accounts. Keep fictional training records clearly labelled and separate from operational evidence.
Explore NCR →See the shared workflow →
Read the full operating guide · Explore the wider Northbank demonstration