What it means
A deviation may concern a failed test, incorrect label, process setting, missing inspection or document error, and the team first contains potential harm and identifies affected batches or services. It then assesses cause, disposition and any corrective action.
A case should not close merely because a deadline has passed or the responsible person left. Define who can approve closure and what evidence that person must see.
The investigator may propose a finding, while a separate quality role checks whether actions were completed where risk warrants it. An empty sign-off field cannot substitute for test data or disposition.
The record should link original evidence, affected scope, immediate containment, root-cause findings, product or service disposition and approvals. Some deviations need a corrective-action plan and later effectiveness check, while others can close after a documented one-off correction with an explanation of why a wider action is not needed.
A corrective action addresses a cause to reduce recurrence and is not interchangeable with correcting the affected unit; if a cause is uncertain, record the uncertainty and the follow-up rather than filling in a plausible story, so the closure record shows what was tested and what remains under watch. Separate three milestones: investigation complete, affected stock dispositioned and preventive action verified.
A shipment may remain held after the investigation is written up, or a corrective action may stay open after stock is safely rejected. If the business uses one closed field for all three, managers may mistakenly assume every risk is gone.
Review recurring deviations and overdue records by severity, not just age, because a small typo and an untraced safety defect require different attention. Where external reporting or customer approval is required, check the applicable terms and rules before closing.
Document the next review date for any effectiveness check and its acceptance test, and if the evidence will not exist for weeks, show the corrective-action status honestly instead of declaring the entire issue finished. A dashboard can distinguish disposition complete from prevention still being tested, and it should.
For owners, a strong closure record turns errors into learning and prevents a dashboard from looking green while the same fault keeps returning.
In practice
Real-world examples.
Example
A batch labelling error is traced to a printer setting; affected units are reworked and checked before the deviation closes. The record links the original photographs, the corrected setting and the rework count. The quality manager signs only after seeing the check results.
Example
The investigation is complete but a supplier test remains pending, so product disposition stays open. The record shows the investigation milestone as done and disposition as outstanding. The held stock stays blocked and the dashboard does not count the deviation as closed.
Example
A process change is implemented, then three subsequent runs are reviewed before the preventive action is marked effective. The review date and acceptance test were written into the record at the start. If any run fails, the deviation is reopened rather than closed.
Formula
Calculation
On-time deviation closure rate = Deviations with all required closure steps completed by target date / Deviations due for closure x 100
Worked example. A fictional plant has 30 deviations due for closure in a month. Twenty-four have complete required evidence; four have open effectiveness checks and two lack disposition.
- On-time closure rate = 24 / 30 x 100 = 80%.
- Six remain open for distinct reasons and should not be marked complete to improve the rate.
Targets and steps should reflect risk and product requirements.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Harbour Pack, an invented packaging plant. Its quality dashboard showed almost every deviation closed on time. A customer found repeat barcode errors and asked how the earlier case had been verified. The file contained a root-cause note but no evidence of a printer change or trial run.
Harbour reopened the issue, quarantined suspect output and added separate status fields for investigation, stock disposition and effectiveness. A supervisor checked subsequent runs against the approved label file. The next customer report included the actual verification record. Closure became a statement about completed work, not a button pressed on a due date.
Harbour checks more than the next shift: it samples later production runs to see whether the printer setting remains stable. It keeps the effectiveness check distinct from the release of earlier held cartons. A repeat error would reopen the investigation even if the original action was documented on time.
Watch out
Common mistakes.
- Closing a deviation because a report was filed while affected stock remains undecided.
- Treating every one-off correction as a proven prevention of recurrence.
- Applying the same deadline and evidence standard to minor and high-risk deviations.
Questions
People also ask.
Can a deviation close while corrective action remains open?
Only if the system and policy clearly separate linked follow-up and the residual risk is managed.
Who should approve closure?
A role with authority and expertise for the affected product, process and risk.
Does closure release held inventory?
No. Product disposition and release need their own authorised decision and evidence.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%