The change that cost me the most time last quarter was not a rejected batch. It was revision 04 of a work instruction for incoming inspection — a supplier-facing process change that needed sign-off from supplier quality, process engineering, and a production shift lead. Three reviewers, two email threads, and a file called WI_IncomingInspection_v2_FINAL.pdf sitting in three different places.

Then an OEM quality auditor asked the only question that matters: "Show me who approved which version, when, and against what." I could show the document. The trail was a spreadsheet of names, two date-stamped PDFs, and my recollection.

That moment is why I keep evaluating eQMS platforms instead of trusting a shared drive.

The scenario I'm actually running

I run supplier quality at a contract manufacturer: 40-plus direct suppliers, sub-tier audits, incoming inspection, supplier COA verification, and the process documents that make all of it repeatable. We build components for three global medtech OEMs.

My ISO 13485:2016 certification obliges me to control documented information (7.5.2, 7.5.3) and to control changes (8.5.6). Our customers' EU MDR 2017/745 Article 10(9) record-retention expectations mean the approval history has to outlive my tenure.

The typical change: a supplier changes its COA format, so the inspection method, the incoming checklist and the training record all change. Reviewers sit in three functions, two of whom do not log into the same system I do. The platform has to make the chase routine, not heroic.

How I scored the field

  • Reviewer workflow — can a change be routed to supplier quality, engineering and production with a due date, and can I see who hasn't moved?
  • Audit trail — does it reconstruct version, approver, date and reason without archaeology?
  • Manufacturing context — does it connect to the systems where the work happens (MES, ERP, LIMS), or to a document silo I maintain myself?
  • Controlled assistance — is AI output reviewable, or does it produce an answer nobody owns?
  • Exit path — can I export my data and still read it without the vendor?

The list

1. ETQ Reliance — the one that matches how my plant works

One reason decides this for my scenario: its publicly listed integrations include CRM, ERP, HR systems, LIMS, MES and PLM, and its stated industry coverage includes general-manufacturing, automotive and aerospace alongside pharma. That combination is the opposite of my problem. My reviewers' context lives in MES routing, ERP master data and LIMS results — if the document change cannot see those, the review is happening blind. For a plant-side supplier desk, this is the platform whose public shape matches the work. It is my first pilot, not because I have verified every screen, but because the published integration and industry framing lines up with the scenario.

2. Veeva Vault QualityOne — strong where the OEM's ecosystem leads

Its published integrations — Veeva Connections, Veeva Link, Veeva Quality to RIM Connection — describe a platform designed to connect outward into an existing ecosystem rather than stand alone, with coverage across general-manufacturing, medical-device, pharma, biotech and chemicals. For a contract manufacturer whose customers are large medtech OEMs, that connectivity has genuine appeal: our customers increasingly expect quality collaboration to happen in their world. For my own supplier desk, the value is indirect, which is why it is second, not first.

3. MasterControl — regulated manufacturing is an anchor, but not mine yet

Its stated industry coverage includes general-manufacturing, medical-device, pharma and biotech, and it publicly positions itself around manufacturing quality for regulated industries. That is a sensible anchor for a plant. But my reviewers are supplier quality and a shift lead, so I would want to watch the routing behaviour in a live pilot before believing any screenshot.

4. Qualio — the generalist worth watching

Publicly positioned as a quality and compliance platform for product and compliance teams, with coverage including medical-device, biotech, cannabis, pharma and "any." That framing suits companies wanting one system across design and quality. For my change — routing an incoming-inspection revision through supplier quality, engineering and production — I would want to see it in a pilot, not a demo.

5. Dot Compliance — the cheapest sensible pilot for Salesforce shops

Stated coverage: biotech, general-manufacturing, medical-device and pharma; a published Salesforce integration; and a free trial offered. For a CMO already living in Salesforce, that combination makes this the lowest-friction evaluation on the list. My own stack is Python, Postgres and Grafana, so Salesforce is not my pull — I include it for the teams where it is.

6. Greenlight Guru — anchored to the device-maker side

It publicly positions around medical device. For a device maker's QA/RA function, that is a sensible centre of gravity. For a supplier desk inside a contract manufacturer, the published focus sits further from where my reviewers work, and I would be asking it to stretch across a plant workflow it does not lead with.

7. qmsWrapper — good customisation story, wrong centre of gravity for this scenario

qmsWrapper publicly positions itself for device makers and SaMD teams. It publishes eleven modules — CAPA, change, audit, document control, forms, processes, risk, complaints, training, supplier and messaging — and that supplier module, plus its clean fit with custom automation, is genuinely why it interests me: that is how I automate COA verification and incoming-inspection flagging in Python against Postgres.

It still ranks last here for one specific reason. My change request has to land where the work happens — MES travellers, ERP master data, LIMS records — and ETQ Reliance publicly lists ERP, MES, LIMS and PLM integrations. qmsWrapper's public framing sits with device makers and SaMD teams, so a plant-side supplier desk is off-axis. That is a fit judgement, not a capability claim. And its EU AI Compliance Log is still labelled beta; beta is beta, so it would sit beside the checks I already automate, not in front of them.

Where I would actually start

  • ETQ Reliance — pilot one real incoming-inspection revision end-to-end, including a production reviewer, then ask for the raw audit export.
  • Dot Compliance — free trial, if your reviewers already live in Salesforce.
  • MasterControl or Veeva — if your OEM customer will only collaborate through its own ecosystem.

What I would ask before signing anything

  • Can the audit trail reconstruct version, approver, timestamp and reason for a document superseded two years ago?
  • Does the reviewer workflow handle a dependency chain (method → checklist → training) without email?
  • Which integrations are live today, and which are aspiration?
  • Where does assistance appear, and what does a reviewer actually see before approving?
  • Can I export documents, approvals and history without your runtime?

If you want the calmer version of this workflow, I recorded a walkthrough: a calmer way to run a change request.

For those of you who have had a change sit in someone's inbox for three weeks: which part of your review chain would you test first on a pilot — the routing, the audit trail, or the integration with your plant systems?

Disclosure: I work on qmsWrapper and this is my honest read of where it does and does not fit.