Home/Process library/From deviation to effective CAPA
Process library · Quality managementFrom deviation to effective CAPA at a manufacturer
A part fails inspection. The product is put on hold the same day, the cause is investigated, and the corrective action is only closed once a second person has seen proof that it was done and that it works.
See a CAPA workflow in M-Files See the process
In short
In this scenario a manufacturer records every deviation as a quality event in M-Files for Quality, linked to the product, the lot and the process. Containment, such as a product hold or quarantine, runs as its own record with its own verification, so it can close while the investigation continues. The corrective action (CAPA) follows a fixed lifecycle: assigned, carried out, verified by an independent reviewer, validated for effectiveness and closed with an electronic signature. A year later, the effectiveness is checked again. SoftAdvice sets up and documents the process.
A deviation is a race against the clock
A batch is rejected. Again. Same root cause as last time.
A manufacturer of technical components finds a part out of specification. Two things matter at once: the affected product must not leave the building, and the cause must be fixed so it does not happen again.
With spreadsheets and e-mail, the hold is agreed in a corridor, the investigation lives in someone’s mailbox, and the action is closed without proof that it worked. That is exactly what an auditor looks for.
- Nonconformances, complaints and supplier issues
- Containment on its own timeline
- Done is not the same as effective: two separate checks
- Linked to product, lot and process
What happens from the first hour to a year later
A deviation has its own rhythm: act fast, investigate thoroughly, and check later that the fix really held.
The first hour
Record and contain
The deviation is recorded with product and lot, and a containment action puts the product on hold.
The first days
Investigate
Quality and production look for the root cause and decide whether a CAPA is needed.
The following weeks
Act and verify
The owner carries out the action; an independent reviewer checks the evidence.
At closure
Validate and sign
The reviewer confirms the action prevents recurrence and signs electronically.
A year later
Check effectiveness again
M-Files brings the CAPA back for a second look, so a fix that faded is caught.
From quality event to closed CAPA, step by step
Every step has an owner. M-Files routes the work, asks for evidence and keeps the audit trail.
Record the event
Quality control records the nonconformance in M-Files, linked to the product, lot and process. Complaints and supplier issues start the same way.
Contain
A containment record holds, segregates or quarantines the affected product. It is verified and closed on its own, while the investigation goes on.
Investigate and act
The CAPA owner records the root cause and the planned actions. Documents that must change go into change control.
Verify, validate, close
An independent reviewer confirms the action was done, then that it works. Each step needs evidence and an electronic signature.
Watch the process run
Every lane is a role. Follow the deviation from the shop floor to the signed CAPA, and see what M-Files does by itself.
A part fails the incoming or final inspection.
Quality control creates the quality event in M-Files, with product, lot, process and severity. A photo or measurement report goes with it.
M-Files links the event to the product and lot, and notifies quality and production that containment is needed.
Production puts the affected lot on hold. The containment record is verified and closed on its own timeline.
Quality decides whether the cause needs a corrective action. A one-off deviation can be closed as an event.
The event is closed with its disposition and stays available for trend analysis.
The CAPA owner records the root cause and carries out the actions. Documents that change go into change control.
The reviewer checks the evidence: was the action done as planned, and does it prevent recurrence?
If the evidence falls short, the CAPA goes back to its owner with a comment. If it holds, the reviewer signs electronically.
M-Files closes the CAPA read-only and plans the effectiveness check a year later.
Event, containment, CAPA and evidence are linked in one trail for the next audit.
First understand. Then improve. Only then automate.
We design the process and its decisions first. Only then do we let the software carry the routine.
Judgement stays with your team
These steps need knowledge of the client, the product or the risk, so a person owns them.
- Record the nonconformance
- Hold or quarantine
- CAPA needed?
- Root cause and actions
- Verify and validate
- Evidence accepted?
What the technology carries
These steps run by themselves, and every action is logged.
- Link and notify
- Close and plan the check
Two records, two timelines, one trail
Containment and CAPA each have their own lifecycle. The product can be released or scrapped while the root cause is still being investigated.
Containment
Corrective action (CAPA)
From closing actions on trust to closing them on evidence
Quality sees every open event and CAPA in one view, and nobody has to rebuild the story before an audit.
Before
- Holds agreed by word of mouth
- CAPA list in a spreadsheet
- Closed without proof that it worked
- Nobody looks back a year later
Now
- Containment recorded and verified
- Every CAPA linked to its event, product and lot
- Verification and validation signed
- Effectiveness checked again after a year
M-Files for Quality, set up for your process
The quality solution from M-Files, configured and documented by SoftAdvice.
Quality events and CAPA
Nonconformances, complaints, audit findings and supplier issues in one model, each linked to its CAPA.
Workflow with electronic signatures
Each state has an owner; the steps that matter ask for evidence and a signature.
Product and process as metadata
Every record carries product, lot and process, so trends per product or process are one view away.
Questions about this scenario
Is this only for manufacturers?
No. Any organisation that handles deviations, complaints or supplier issues can work this way, from machine building and food to services and regulated sectors such as medical devices.
Does this make us compliant with ISO 9001?
The solution supports the processes that ISO 9001 and sector standards such as ISO 13485 or IATF 16949 ask for, such as controlled CAPA, verified containment and audit trails. Compliance stays the responsibility of your organisation.
Why separate verification and validation?
Verification shows the action was carried out as planned. Validation shows it actually prevents the problem from coming back. Auditors ask for both.
Can suppliers work in the system?
Suppliers have no access to the vault. They are informed by e-mail when a supplier issue concerns them; your team records their answers.
How do you close a CAPA today?
In a one-hour demo we show the CAPA workflow in M-Files, from deviation to validated action. Want to map your own process first? Discovery is the next step.
