eQMS
Electronic Quality Management System
An eQMS is the system of record for the quality processes an organisation runs, rather than for the product it makes. It holds the deviation that was raised, the investigation that followed, the CAPA that was committed to, the change that was controlled, the complaint that was received, the audit that was performed, and the training that qualified the person who signed. ICH Q10 describes a pharmaceutical quality system in terms of exactly these elements — process performance and product quality monitoring, a corrective and preventive action system, a change management system, and management review — and an eQMS is where most organisations operationalise them.
What this page does not claim
A system class is not a product. SPEQ describes what a CTMS or a LIMS is; the vendor directory at /tools lists the products that implement one, and a GAMP category is a property of an implementation, not of a class.
What a eQMS actually is
An eQMS is the system of record for the quality processes an organisation runs, rather than for the product it makes. It holds the deviation that was raised, the investigation that followed, the CAPA that was committed to, the change that was controlled, the complaint that was received, the audit that was performed, and the training that qualified the person who signed. ICH Q10 describes a pharmaceutical quality system in terms of exactly these elements — process performance and product quality monitoring, a corrective and preventive action system, a change management system, and management review — and an eQMS is where most organisations operationalise them.
The distinction that matters is between the quality *record* and the manufacturing *record*. A batch record proves that a specific batch was made as intended; a deviation record proves what the organisation did when it was not. An eQMS is the second thing. It is the reason a firm can answer "show me every open CAPA older than ninety days" or "show me every change that touched this product since the last inspection" without assembling the answer by hand from paper files — and the reason a regulator can test whether the quality system is actually operating rather than merely documented.
Because an eQMS holds the record that decides whether product is released and whether a problem was closed, it is squarely a Part 11 and Annex 11 system: electronic signatures carry regulatory weight, audit trails must be secure and computer-generated, and access must be controlled to the individual. The workflow engine is usually the point of highest configuration risk — an escalation rule, a due-date calculation, or an approval matrix configured incorrectly does not throw an error, it silently produces a compliant-looking record with the wrong approver on it.
The commercial market is mature, so most implementations are configured commercial platforms rather than bespoke builds. That shapes the validation approach: the supplier can be leveraged for the platform, but the configured workflows, the escalation logic, the report definitions, and any integration are the implementing organisation's to verify. This is the pattern GAMP 5 Second Edition (2022) describes as Category 4, and it is where inspection findings concentrate.
WHERE THE BOUNDARY ACTUALLY SITS
Not the batch record. The eQMS holds the deviation raised against a batch; the electronic batch record holds what was actually done to make it.
MES / EBR owns it →Not the document management system in every deployment. Many organisations run a separate controlled-document/SOP repository, and the eQMS references it rather than owning it.
Not the regulatory submission system. A change control may conclude that a variation is required, but the variation itself is planned and tracked in RIM.
RIM owns it →Not the laboratory system of record. An out-of-specification result originates in the LIMS or the chromatography data system; the eQMS holds the investigation of it.
LIMS owns it →WHAT IT HOLDS, AND WHAT CROSSES ITS BOUNDARY
CORE RECORDS
- Deviation and nonconformance records, with investigation and root-cause analysis
- CAPA records, with effectiveness checks and closure evidence
- Change control records, with impact assessment and implementation verification
- Complaint records, and the reportability decision made against each
- Internal and supplier audit records, findings, and responses
- Training records and role-based curricula that evidence qualification to perform a task
- Management review inputs and outputs (ICH Q10 §4)
DATA FLOWS OUT
Deviations raised from an in-process exception, and the change control that authorises a master batch record revision
Out-of-specification and out-of-trend results escalated into a laboratory investigation
Approved changes whose impact assessment concludes a regulatory variation or notification is required
Quality holds, batch status decisions, and approved-supplier status that gate material movement
Complaints that meet the adverse-event criteria and must be handled as safety cases
HOW THIS CLASS IS USUALLY VALIDATED
- SPEQ synthesis: most eQMS deployments are commercial platforms configured to the organisation's procedures, which GAMP 5 Second Edition treats as Category 4 — the platform can lean on supplier assessment, the configuration cannot.
- The highest-risk configuration is the workflow engine: approval matrices, escalation and due-date rules, and role-to-permission mapping produce a plausible record when set up wrongly, so they warrant scripted testing even under a CSA-leaned approach.
- Electronic signature manifestations, signature/record linking, and the inability of an ordinary user to disable or alter the audit trail are Part 11 §11.10 and Annex 11 controls that are verified directly, not inherited from the supplier.
- Reports and queries used to make quality decisions (open-CAPA ageing, overdue-training listings) are part of the validated scope — a report that silently filters out a category of record is a data-integrity failure, not a cosmetic one.
SPEQ synthesis, not a rating. This is SPEQ’s reading of how this system class is commonly approached, offered to help you scope your own work. A GAMP category is a property of a specific implementation, not of a product class, and one deployment routinely spans several. It is not a classification service and does not replace your own documented risk assessment.
- Stage 1 · Reactive
Quality events are logged after the fact in spreadsheets or a document system. Ageing is unknown until someone compiles it, and the same failure recurs because nothing links a deviation to the change that should have prevented it.
- Stage 2 · Defined
Deviation, CAPA, and change processes are defined and executed in a single system with role-based approval. Records are complete and on time, but each process is an island and trending is a manual quarterly exercise.
- Stage 3 · Controlled
Workflows are configured to the procedure, escalation and due dates are enforced by the system, and records are linked — a deviation carries its CAPA, the CAPA carries its effectiveness check, the change carries its verification. Audit-trail review is scheduled and evidenced.
- Stage 4 · Predictive
Quality data is analysed rather than reported: recurring root causes, CAPA effectiveness rates, and change-failure rates are tracked and drive where the organisation invests. Risk from ICH Q9 assessments is visible in the same system that holds the events.
- Stage 5 · Adaptive
The eQMS is a live sensor for the quality system. Signals from complaints, deviations, supplier performance, and process monitoring converge, management review acts on leading indicators rather than closed counts, and the system adapts its own control strategy as risk moves.
SPEQ’s shared five-stage progression, labelled synthesis. It is not the FDA QMM rating scale and not the scored maturity-assessment domains — assess your quality system for those.
WHAT AN INSPECTION PROBES, AND WHERE IT GOES WRONG
INSPECTION SIGNALS
- Whether CAPA effectiveness checks are real verification or a restated closure statement — the single most-cited weakness in this system class.
- Deviation and investigation timeliness, and whether extensions are justified or routine.
- Whether the audit trail can be disabled or edited by an ordinary user, and whether audit-trail review is evidenced against specific records rather than described in an SOP.
- Whether recurring events were recognised as recurring: the same root cause across multiple deviations with no escalation is a quality-system finding, not a record-keeping one.
- Whether training records actually evidence qualification for the task performed, including for changed procedures.
COMMON RISKS
- Configuring the workflow to the software's default rather than to the approved procedure, so the record and the SOP describe different processes.
- Root-cause analysis that stops at human error, producing retraining as a CAPA and guaranteeing recurrence.
- Migrating legacy quality records without verifying completeness or preserving the original audit trail and metadata.
- Treating reports and dashboards as outside the validated scope, then making release and escalation decisions on them.
- Shared or role-based logins that make an electronic signature unattributable to an individual.
WHO WORKS IN IT, AND WHERE IT IS SHAPED
ROLES
- Quality Assurance Associate / Specialist
- CAPA and deviation owner
- Change control coordinator
- QMS system administrator / business owner
- CSV analyst
- Head of Quality
DELIVERY-LIFECYCLE PHASES
[ POSITION IN THE FRAMEWORK ]
6 OF 7 DIMENSIONS · 29 LINKSThe system of record for the quality processes themselves — deviations, CAPA, change control, complaints, audits, and training — where ICH Q10's PQS elements are operationalised; not the batch record but the exception to it.
06 · QUALITY MATURITY — EQMS, REACTIVE TO ADAPTIVE
Quality events are logged after the fact in spreadsheets or a document system. Ageing is unknown until someone compiles it, and the same failure recurs because nothing links a deviation to the change that should have prevented it.
Deviation, CAPA, and change processes are defined and executed in a single system with role-based approval. Records are complete and on time, but each process is an island and trending is a manual quarterly exercise.
Workflows are configured to the procedure, escalation and due dates are enforced by the system, and records are linked — a deviation carries its CAPA, the CAPA carries its effectiveness check, the change carries its verification. Audit-trail review is scheduled and evidenced.
Quality data is analysed rather than reported: recurring root causes, CAPA effectiveness rates, and change-failure rates are tracked and drive where the organisation invests. Risk from ICH Q9 assessments is visible in the same system that holds the events.
The eQMS is a live sensor for the quality system. Signals from complaints, deviations, supplier performance, and process monitoring converge, management review acts on leading indicators rather than closed counts, and the system adapts its own control strategy as risk moves.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 10
Derived from the 10 standards SPEQ maps to this subject, across 6 regulatory bodies: FDA, EMA, ICH, ISO, ISPE, MHRA.
RECORDS & OBJECTIVE EVIDENCE
- Deviation and nonconformance records, with investigation and root-cause analysis
- CAPA records, with effectiveness checks and closure evidence
- Change control records, with impact assessment and implementation verification
- Complaint records, and the reportability decision made against each
- Audit-trail review evidence and role-based training records proving qualification to a task
COMMON INSPECTION FINDINGS
- CAPA effectiveness checks that restate closure rather than verify it
- Root-cause analysis stopping at "human error", producing retraining as the corrective action
- The same root cause across multiple deviations, never escalated as a systemic problem
- An audit trail an ordinary user can disable or edit, or review described in an SOP but not evidenced
- Shared or role-based logins that make an electronic signature unattributable to an individual
Choosing, validating, and living with eQMS
SPEQ curates the software directory and does not endorse, certify, or rank any vendor. Listing is not a recommendation, and this catalog describes the system class, not the product.
FREQUENTLY ASKED
What is the difference between an eQMS and a document management system?
A document management system controls documents — SOPs, specifications, and forms — through versioning, approval, and periodic review. An eQMS controls quality *processes*: the deviation, the investigation, the CAPA, the change, the complaint, the audit. Many platforms bundle both, but the obligations differ: the document system evidences that people worked to the current approved instruction, while the eQMS evidences what happened when they could not, and what the organisation did about it.
Is an eQMS a 21 CFR Part 11 system?
In practice, yes. An eQMS holds electronic records that predicate rules require — deviation and CAPA records under 21 CFR 211.192 and the quality-system requirements of 21 CFR Part 820 — and it applies electronic signatures to decisions such as investigation closure and change approval. That brings 21 CFR Part 11 controls into scope: secure, computer-generated, time-stamped audit trails; access limited to authorised individuals; and signature manifestations linked to their records. EU GMP Annex 11 sets the equivalent expectations in Europe.
What GAMP 5 category does an eQMS fall into?
Most commercial eQMS deployments are approached as GAMP 5 Category 4 — configured commercial software — because the organisation configures workflows, roles, and forms without writing code. Custom extensions, bespoke integrations, or scripted business rules push those specific elements toward Category 5. The category is a property of the implementation, not of the product: GAMP 5 Second Edition (2022) is explicit that a single system commonly spans categories, and it retired the former Category 2 entirely. This framing is SPEQ synthesis to aid scoping, not a classification service.
Does an eQMS replace the batch record?
No. The electronic batch record is the evidence that a specific batch was manufactured as intended and is the record a batch-release decision rests on. The eQMS holds the exception: the deviation raised against that batch, the investigation, and the CAPA. The two are connected — a deviation must be traceable to the batch it affects, and an approved change must be traceable to the master batch record it revised — but they are separate systems of record with separate retention and review obligations.