One Wrong Drawing, One Expensive Lesson

01 · WHAT HAPPENED

The drawing on the screen looked like authorised production information.

Each CNC operator had a monitor at the machine and used it to access the engineering drawing for the job. That arrangement removed paper from the shop floor and made information easy to retrieve. It also created a hidden dependency: production had to be able to trust that every drawing available through the normal server route was current.

On this job, an earlier drawing revision had been placed on the server and remained accessible. The operator selected it and machined the component shown on the screen. Final quality inspection later identified that the finished part did not match the current revision.

The impact extended beyond one incorrect dimension. The part required rework, the specified metal was not readily available in sufficient quantity and the project faced additional material and delivery pressure.

“My immediate reaction was that the machining operator had made a mistake. The NCR review showed that the system had made an obsolete drawing appear usable.”Shafi Abdulla · Quality Assurance Manager at the time of the incident

02 · WHAT THE NCR REVEALED

Following the evidence backwards changed the problem.

Engineering and production reviewed the event through the nonconformity process. Starting at final inspection, the team traced the information backwards: completed component, CNC operation, drawing selected at the machine, server location and engineering release.

The operator had used the information made available by the organisation. Training the operator again or adding an instruction to “check the revision” would still have left obsolete information in the normal production route. Another competent employee could have repeated the same error.

03 · WHAT CHANGED

The control made the wrong action harder.

Access to obsolete drawings was restricted. Older revisions could be retained for traceability, but they were removed from the routine path used to manufacture current work. ERP controls were also strengthened so drawing status and operational release were connected more clearly.

This was stronger than relying on attention alone. The revised procedure described a process that now existed; it was not being used as a substitute for a missing technical control.

04 · HOW PEOPLE PARTICIPATED

NCR reviews stopped being automatic blame meetings.

Regular orientation and post-project reviews brought the relevant functions together to analyse NCRs. The discussion covered where each problem originated, which handover allowed it to travel and what could prevent recurrence on the next project.

Good performance was highlighted alongside failures. Recognition included appreciation during meetings, certificates, small rewards, positive performance points and management acknowledgement. This preserved accountability while making it safer for employees to raise risks and improvement ideas.

The visible outcome was fewer recurring NCRs and better on-time delivery. No percentage is published because the anonymised evidence available for this case does not support a defensible numerical claim.

05 · WHAT TO APPLY

Stick to the basics before writing more documents.

1. Follow one real order.Trace it from customer enquiry through engineering, procurement, production, inspection, testing and dispatch.
2. Inspect every handover.Ask what information crosses the boundary, who confirms it is current and what evidence proves the control worked.
3. Use NCRs as a trail.Move backwards from detection to creation instead of stopping with the person nearest the problem.
4. Change working conditions.Remove confusing options or build a system barrier before adding reminders and training.
5. Document the working control.Write only what people need to operate, verify and sustain the process.