Our regulatory affairs lead and I keep returning to the same unglamorous conclusion: fewer handoffs and a defensible revision history reduce QMS risk more than another AI feature.
A recent supplier corrective-action review made that concrete.
A sub-tier supplier had revised an incoming-inspection method for a component used in one of our OEM programmes. The new method was technically sound, but the effective revision was distributed across several places:
- The revised procedure lived in a controlled folder.
- Approval appeared in an email.
- The effective date was communicated in chat.
- The supplier’s certificate of analysis still referenced the previous method.
- Our inspection record showed the old revision without explaining whether that was intentional.
During the review, I needed to establish which method applied on the day two lots were received. We could retrieve the current document, but reconstructing the decision took time and exposed a familiar weakness: every handoff required a person to preserve context.
That is where I think much of the AI-in-QMS conversation becomes detached from operational reality.
Handoffs multiply risk quietly
I count a handoff whenever a record changes location or ownership and someone must carry its context forward.
At a contract manufacturer, that chain can include:
- The OEM.
- Our quality and regulatory teams.
- The direct supplier.
- A sub-tier supplier.
- Production, stores, or incoming inspection.
This does not mean every review should disappear. A supplier process change may still need engineering assessment, regulatory impact review, risk evaluation, and quality approval. Removing those review points would be reckless.
Fewer handoffs should mean fewer opportunities for context to be lost between those review points.
If an approved supplier change requires a new inspection method, the useful workflow should connect the supplier notification, impact assessment, approval, effective revision, downstream implementation, and objective evidence. It should not rely on someone remembering to update six records manually.
That is process automation with a regulatory purpose, not automation for its own sake.
Revision history is more than “Rev C”
A filename containing “Rev C” is not controlled revision history.
For me, a reviewable revision history needs to preserve the decision around the document:
- What changed and why?
- Who reviewed and approved it?
- When did it become effective?
- Which earlier revision does it supersede?
- What risk, CAPA, supplier, or training records were affected?
- Where is the evidence that downstream users implemented it?
ISO 13485:2016 clause 4.2.4 expects controls for document approval, revision, identification of changes, and the current revision. Clause 4.2.5 addresses record control, including retrieval. EU MDR Article 10(9) also expects processes for controlling documents and records throughout their lifecycle.
None of those provisions mandates a particular software product or workflow. That distinction matters. “Fewer handoffs” is not the regulated requirement; it is one way to demonstrate that the required controls are connected and effective.
Clear revision history reduces risk because it preserves the logic of the decision. It does not merely prove that somebody eventually uploaded a new PDF.
AI cannot repair disconnected workflow
AI-driven CAPA assistance can help a CAPA owner find similar non-conformances, draft a clearer investigation plan, or identify missing evidence. But a polished root-cause paragraph is not an advantage if it cannot be traced back to the relevant lot records, supplier correspondence, inspection revision, and effectiveness check.
The value is in controlled assistance: source evidence remains visible, outputs can be reviewed, and a human remains accountable for the decision.
This is also where I remain sceptical of broad AI-in-QMS claims. If an assistant can generate content faster while records remain disconnected, it can help reproduce stale information at greater speed. Process automation, traceability, and reviewability are not optional extras around the AI feature; they are the conditions that make the feature safe assistance for CAPAs.
For CAPAs that change an inspection or production control, the workflow should also carry the CAPA-driven risk assessment into the effective document revision. Otherwise the CAPA closes, but the operational system continues using the old assumption.
A manufacturer-centric QMS still needs a CMO lens
qmsWrapper is publicly positioned for device makers and SaMD teams. That is a sensible place for connected change, CAPA, risk, and document-control workflows.
Our CMO-side supplier work has a different centre of gravity: supplier COA verification, incoming inspection, sub-tier audits, quality agreements, and routing changes through customer-specific requirements. A manufacturer-centric workflow may assume that the organisation owns the full device record graph. I cannot assume that assumption will absorb supplier-quality work cleanly.
For us, native workflow integration matters more than an impressive standalone assistant. The incoming-inspection plan, supplier corrective action, risk assessment, effective revision, and OEM-facing evidence need to remain connected. Any beta AI capability should be treated as beta when it touches an audit-critical trail.
What I would test before trusting the workflow
I would not start with a demo. I would start with one controlled supplier change and ask the system to reconstruct it end to end:
- Can I identify the exact effective revision for a given date?
- Can I see who approved it and what evidence they considered?
- Are affected risk files, CAPAs, training records, and inspection plans linked?
- Can I distinguish drafts from approved and superseded revisions?
- Can an auditor follow the trail without asking us to interpret email or chat history?
If those answers require a human to carry a document revision from one silo to another, the workflow has not solved the problem.
I work on qmsWrapper and am giving my honest read of where it does not fit our CMO-side supplier workflow.
Where does your QMS still make someone carry a revision by hand—and which handoff would you redesign first?
Top comments (0)