MDRC logo
Explore
← Checklists

MDR Article 10(9) · Annex IX · ISO 13485 · Interactive review

MDR quality management system checklist

Check whether the QMS controls regulatory work in practice, not merely whether procedures exist.

Review 84 concrete checkpoints, record evidence and gaps, and issue a clean assessment report. Your draft stays in this browser and is not sent to MDRC.

Start the checklist ↓
mdr.qms.readiness Draft ready
0% reviewed
0Completed
84Open
0Not applicable

84 checkpoints · 12 controlled sections

Project details

Define the organisation and QMS scope before reviewing the system

Only completed fields are carried into the issued report. The organisation name is required.

Local draft

Entries are stored in this browser only. They are not uploaded or submitted.

Not yet saved

System review

Review the complete MDR quality-system chain

Use Completed, Open or Not applicable. Add a document reference, decision or short rationale only where it helps the review.

01.01

The legal manufacturer and every QMS site are identified

Confirm legal names, addresses, SRNs where available, activities performed at each site and consistency with certificates, registrations and labels.

01.02

The QMS scope covers all device families, risk classes and conformity routes

Map each device family to its intended purpose, MDR class, applicable Annex VIII rules and conformity assessment route.

01.03

All processes needed for MDR conformity are mapped with owners and interfaces

Include regulatory strategy, design, risk, clinical, suppliers, production, release, UDI, PMS, vigilance, CAPA and change control.

01.04

Outsourced processes remain inside the manufacturer’s controlled QMS

Identify external design, testing, software, sterilisation, warehousing, service and regulatory activities and the controls applied to each.

01.05

The quality manual or equivalent explains the system and its process sequence

A reviewer should be able to understand the scope, process interactions, governing procedures and controlled-document hierarchy without guessing.

01.06

Any exclusion or non-applicable process is justified against actual manufacturer responsibilities

Do not use an ISO 13485 exclusion to remove an obligation that the MDR places on the legal manufacturer.

01.07

The ISO 13485 certificate scope matches the activities and sites represented as certified

Where certification is used, verify the current edition, accredited certification body, products, activities, sites, expiry and exclusions.

02.01

A current regulatory compliance strategy exists for every device family

Record qualification, classification, conformity route, standards, clinical strategy, registration, PMS obligations and market-specific constraints.

02.02

Device qualification and MDR classification are documented and approved

State the intended purpose, applicable Annex VIII rules, rationale and resolution of borderline or combination-product questions.

02.03

The selected conformity assessment route is valid for the device and manufacturer

Distinguish Class I self-declaration from routes requiring a Notified Body and define the assessment scope for Is, Im and Ir devices.

02.04

Applicable GSPRs are identified with methods and controlled evidence references

Each Annex I requirement should show applicability, method of conformity, standards or common specifications, and exact evidence location.

02.05

Standards, common specifications and MDCG guidance are monitored for change

Define owners, review frequency, transition decisions and actions when editions, harmonisation status or guidance change.

02.06

Intended purpose and claims are approved before external use

Control consistency across technical documentation, clinical evidence, labels, instructions, registrations, website and promotional material.

02.07

Regulatory impact assessment is mandatory for product and QMS changes

Define when the Notified Body, competent authority, authorised representative or other economic operators must be notified before implementation.

03.01

Management has approved a quality policy and measurable quality objectives

Objectives should address product conformity, regulatory performance and process effectiveness and be reviewed using defined indicators.

03.02

Responsibilities, authority and reporting lines are documented

Define who can approve designs, release product, stop production, report incidents, initiate field action and accept residual risk.

03.03

Management provides resources based on QMS and product risk

Link staffing, competence, facilities, equipment, digital systems and external expertise to planned work and unresolved quality risks.

03.04

Process owners monitor performance and escalate missed requirements

Owners should know their criteria, data sources, review frequency, thresholds and escalation route.

03.05

A qualified PRRC is continuously and permanently available

Verify Article 15 qualification evidence, employment or contractual arrangement, availability and deputy or continuity arrangements.

03.06

PRRC responsibilities are integrated into release, documentation, PMS and vigilance

The process should let the PRRC verify conformity before release, technical-documentation maintenance, PMS obligations and required reporting.

03.07

Quality and regulatory personnel can escalate concerns without disadvantage

Document independence, access to management, conflict handling and the MDR protection against disadvantage for the PRRC.

04.01

Competence requirements are defined for work affecting quality or regulatory compliance

Specify education, training, skills and experience for design, clinical, risk, production, release, audit, complaint and vigilance roles.

04.02

Training records show competence and effectiveness, not attendance alone

Use observed work, tests, supervised performance, record review or outcome data appropriate to the role and risk.

04.03

Role changes, temporary staff and external experts are controlled

Define induction, supervision, access, authorisation and competence verification before independent work.

04.04

Infrastructure and work environment requirements are specified and maintained

Cover premises, utilities, environmental conditions, cleanliness, contamination control, IT, security and maintenance as applicable.

04.05

Monitoring and measuring equipment is calibrated or verified and traceable

Define intervals, standards, status identification, out-of-tolerance assessment and impact on previously accepted product.

04.06

Software used in the QMS or production is validated for its intended use

Use a risk-based plan covering requirements, testing, access, configuration, data integrity, backup, changes and periodic review.

04.07

Business continuity protects critical QMS records and regulated operations

Address backup restoration, cyber incidents, utility or supplier failure, facility loss and continuity of vigilance and field-action communication.

05.01

Controlled documents have an identifier, version, owner, approval and effective date

Procedures, forms, specifications, work instructions and templates should be unambiguous at every point of use.

05.02

Document changes state the reason, impact and required implementation actions

Link changes to training, validation, regulatory assessment, affected product and withdrawal of obsolete copies.

05.03

External documents and standards are identified and kept current

Control legislation, guidance, standards, customer specifications, supplier documents and translated information used in regulated work.

05.04

Obsolete documents cannot be used unintentionally

Remove superseded versions from points of use while preserving clearly identified archive copies where retention is required.

05.05

Records are legible, attributable, contemporaneous, original and accurate

Define correction rules, audit trails, signatures, access rights, protection, retrieval and backup for paper and electronic records.

05.06

Retention periods meet MDR requirements and other applicable obligations

Keep required documentation for at least 10 years after the last device is placed on the market and 15 years for implantable devices.

05.07

Technical documentation, declarations and certificates are current and readily available

Control Annex II and III files, EU declarations of conformity, certificates and records needed by authorities, the PRRC and the Notified Body.

06.01

A lifecycle risk management process is applied to every device

The plan should define scope, responsibilities, criteria, reviews and production and post-production information sources.

06.02

Hazards and foreseeable misuse are systematically identified and evaluated

Include device, software, usability, cybersecurity, biological, electrical, mechanical and information-related risks as applicable.

06.03

Risk controls follow the required priority and are verified for effectiveness

Prefer safe design, then protective measures and finally information for safety, with traceable implementation and test evidence.

06.04

Residual risk and overall benefit-risk conclusions are documented and current

Connect conclusions to clinical evidence, state of the art, supplied information and new production or post-market data.

06.05

The clinical evaluation plan and report support the current intended purpose and claims

Define the evidence strategy, appraisal, gaps, conclusions, update frequency and traceability to risk and GSPRs.

06.06

PMCF is planned and performed or a device-specific justification explains why it is not applicable

State objectives, methods, timelines, acceptance criteria, findings and the decisions each activity informs.

06.07

Risk, clinical, PMCF and PMS outputs remain mutually consistent

A change in one record should trigger review of the others, including labels, claims, benefit-risk conclusions and technical documentation.

07.01

Design plans define stages, responsibilities, reviews and interfaces

Keep the plan current as development changes and identify required verification, validation, transfer and regulatory deliverables.

07.02

Design inputs are complete, measurable, approved and free of unresolved conflict

Include intended use, user needs, GSPRs, risk controls, clinical requirements, standards, usability and cybersecurity where applicable.

07.03

Design outputs define the product and support production and acceptance

Control drawings, specifications, software, formulations, labels, packaging, instructions and acceptance criteria for the released configuration.

07.04

Formal design reviews resolve actions before the next stage

Use independent expertise where appropriate and record participants, evidence reviewed, decisions, actions and closure.

07.05

Verification demonstrates that outputs meet approved inputs

Protocols should define methods, samples, acceptance criteria and deviations, with traceability to the exact released configuration.

07.06

Validation demonstrates that the device meets user needs and intended use

Use representative product and intended users and environments, including clinical, usability, software and packaging validation as applicable.

07.07

Transfer and design changes preserve the validated state

Confirm production readiness and apply risk, verification, validation, regression and regulatory assessments before change approval.

08.01

Suppliers are classified and qualified using risk-based criteria

Consider criticality, substitutability, process validation, regulatory status, performance history and the consequence of failure.

08.02

Critical suppliers and outsourced processes are explicitly identified

Include design, software, testing, sterilisation, special processes, packaging, warehousing, calibration and regulatory services as applicable.

08.03

Quality agreements define responsibilities and change notification

Cover specifications, records, deviations, complaints, audits, traceability, retention, subcontracting and access for authorities or the Notified Body.

08.04

Purchasing information states complete and approved requirements

Use current specifications, drawings, acceptance criteria, process requirements and regulatory or traceability conditions.

08.05

Incoming product and supplied services are verified before acceptance

Match inspection, testing, certificates and sampling to risk and retain objective evidence of acceptance or authorised concession.

08.06

Supplier performance is monitored and re-evaluated using defined thresholds

Use quality, delivery, audit, complaint, deviation and change data with escalation, development or disqualification rules.

08.07

Supplier changes and failures trigger product and regulatory impact assessment

Connect notifications, nonconformities and CAPA to risk management, validation, technical documentation and Notified Body communication.

09.01

Current specifications and work instructions control production and service

Operators should have approved requirements for materials, equipment, parameters, environment, workmanship, inspection and records.

09.02

Product identity and acceptance status remain clear throughout processing

Prevent mix-up and unauthorised use through lot, serial, software, configuration, inspection and quarantine controls.

09.03

Processes whose output cannot be fully verified later are validated

Include sterilisation, sealing, welding, cleaning, moulding, software deployment or other special processes as applicable.

09.04

Equipment, utilities and environmental controls are maintained within limits

Define qualification, preventive maintenance, monitoring, alarm, excursion assessment and requalification requirements.

09.05

In-process and final acceptance criteria are applied and recorded

Use authorised methods, sampling plans, trained personnel and traceable results, with deviations resolved before release.

09.06

Release records identify the approved product and authorised releaser

Confirm all required records, tests, deviations, labels and PRRC-related conformity checks are complete before release.

09.07

Packaging, storage, transport, installation and service preserve conformity

Control environmental limits, shelf life, handling, shipping qualification, field records and feedback into complaints and PMS.

10.01

Basic UDI-DI and UDI-DI assignment follows controlled grouping rules

Document the issuing entity, device-family rationale, packaging hierarchy and triggers requiring a new identifier.

10.02

UDI production identifiers are applied at the required levels

Control lot, serial, manufacture or expiry data as applicable and verify human-readable and automatic-identification carriers.

10.03

UDI, label, certificate and registration data are consistent

Cross-check names, models, risk class, intended purpose, status, manufacturer and authorised representative details.

10.04

EUDAMED and other required registrations are created and updated on time

Assign owners for actor, device, certificate, vigilance and market-status data and retain evidence of verification and changes.

10.05

Economic operators are verified and linked to the correct devices

Control authorised representative, importer and distributor information, agreements, complaints, cooperation and registration obligations.

10.06

Distribution records support rapid and complete recall scope

Trace suppliers, lots or serials, customers, dates, quantities and destinations for the legally required period.

10.07

Implant cards, SSCP and other class-specific information are controlled where required

Verify applicability, content, translations, publication, updates and consistency with the technical documentation and registrations.

11.01

A device-specific PMS plan defines proactive and reactive data sources

Cover complaints, incidents, trends, literature, registries, user feedback, distributor data, competitor signals and PMCF.

11.02

Exposure and denominator data support meaningful signal evaluation

Collect sales, distribution, installed base, procedure or patient-use data appropriate to complaint, incident and trend rates.

11.03

Complaints are logged, assessed, investigated and trended consistently

Define intake, duplication checks, reportability, investigation depth, root cause, communication, closure and escalation.

11.04

Serious incidents and FSCAs are reported within applicable timelines

Document decision trees, awareness dates, MIR and FSCA workflows, authority interaction, follow-up and final reporting.

11.05

Statistically significant increases are assessed for trend reporting

Define reportable events, methods, observation periods, thresholds, expected levels and documented decisions.

11.06

The PMS report or PSUR is current, approved and distributed as required

Use the correct class-based output and frequency and ensure conclusions update benefit-risk, PMCF and preventive or corrective actions.

11.07

Regulatory communication and supply-interruption processes are controlled

Cover authorities, Notified Body, economic operators and customers, including Article 10a notifications where interruption may cause serious harm.

12.01

Nonconforming product and process outputs are identified and controlled

Prevent unintended use or release and document evaluation, segregation, concession, correction, rework, scrap and regulatory impact.

12.02

CAPA distinguishes immediate correction from systemic root-cause action

Use proportionate investigation, containment, root-cause analysis, action plans, responsibilities, deadlines and escalation.

12.03

CAPA effectiveness criteria are defined before closure

Verify that recurrence and risk were reduced using suitable data over a justified period rather than closing on implementation alone.

12.04

Quality data are analysed for adverse trends and improvement opportunities

Combine supplier, production, nonconformity, complaint, vigilance, audit, service and process-performance data.

12.05

Internal audits cover the full QMS using independent and competent auditors

Base frequency on process and product risk, audit complete process trails and verify effective closure of findings.

12.06

Management review evaluates required inputs and makes recorded decisions

Include objectives, audits, feedback, PMS, CAPA, suppliers, regulatory change, resources and process and product performance.

12.07

Management review outputs assign actions, owners, resources and deadlines

Track decisions on QMS effectiveness, product improvement, regulatory needs and resources to verified completion.

Issue the review

Create a clean PDF or printed checklist

The report excludes website navigation, guidance text, controls, empty project fields and empty comment boxes. In the print dialog, choose Save as PDF or select a printer.

0 completed 84 open 0 not applicable

Regulatory basis

Built around MDR Article 10(9) and Annex IX

Every manufacturer needs a QMS proportionate to the risk class and type of device. ISO 13485 is a recognised implementation framework, but the MDR does not make ISO 13485 certification universally mandatory.

↑

Discuss your regulatory pathway

Whether you are developing medical software, an AI-enabled healthcare solution, a digital health platform or a software-driven medical device, we can help define the regulatory strategy, evidence requirements and next steps.

→

Where companies need support

Regulatory strategy
Technical documentation
Clinical and performance evidence
Software lifecycle and cybersecurity
Notified Body readiness

Start a discussion

 

Regulatory support for software medical devices, AI health technologies and digital healthcare solutions.


©2026 MDRC - Medical Devices Regulatory Compliance

Useful information

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

Read more >>


Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.

Send us an email:
info@mdrc-services.com

Or use the contact form below

 

Solutions

EU Authorised Representative (EC REP)

EU PRRC

Technical documentation

Risk management

Clinical evaluation

Notified Bodies

Quality management system

Post-market surveillance

Resources

Medical Device Regulation (MDR) - basics

CE-marking process for medical devices

CE-marking process for in vitro diagnostic medical devices

MDR technical documentation checklist

IVDR technical documentation checklist

Technical documentation checklist for medical device software (MDSW)

MDR-compliant quality system documentation checklist

MDR-compliant quality system documentation checklist for medical device software

Clinical Evaluation Plan checklist

Clinical Evaluation Report checklist

PRRC under MDR or IVDR

Articles

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

More articles >>

Devices

General medical devices and equipment

In vitro diagnostics (IVD)

Medical software

Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.