Skip to main content

Checklist & compliance matrix

Regulatory basis

The UK MDR 2002 does not specify a mandatory format for the Essential Requirements checklist, but UKABs and MHRA expect all technical files to include a systematic demonstration of conformity with all applicable Essential Requirements in Schedule 1 (or Schedule 1A for IVDs). The checklist structure described here is consistent with best practice and UKAB expectations.


What is the ER checklist?

The Essential Requirements checklist (also called a compliance matrix or traceability matrix) is a document within the technical file that:

  1. Lists every Essential Requirement in Schedule 1 (or Schedule 1A)
  2. States whether each requirement is applicable to the device (and if not, why not)
  3. Identifies the method of demonstration — which standard, test, or evidence shows conformity
  4. Provides a technical file cross-reference — exactly where in the technical file the evidence can be found

The checklist is reviewed by UKABs during conformity assessment and by MHRA during audits. A well-structured checklist significantly reduces assessment time and demonstrates regulatory competence.


Structure of the checklist

ColumnContent
ER referenceSpecific ER number and title (e.g., "ER 2 — Risk reduction")
Applicable?Yes / No / Partially
Justification if N/AWhere not applicable, state the reason (e.g., "device has no measuring function")
Method of demonstrationStandard applied, test performed, or other evidence type
Document / section referenceExact location in the technical file (e.g., "Section 5 — Risk Management File, ISO 14971 Report, Rev 3")
StatusConformant / In progress / Gap identified

Worked example framework — Class IIb active general device

Below is an illustrative framework for a Class IIb active non-implantable device (e.g., a patient monitoring system with therapeutic alarming).

ERApplicable?MethodTF Reference
ER 1 — Safety in intended useYesRisk management per ISO 14971; clinical evaluation reportTF-05; TF-08
ER 2 — Risk reduction hierarchyYesISO 14971 risk management file; design FMEATF-05
ER 3 — Performance as intendedYesBench performance testing; clinical evaluationTF-06; TF-08
ER 4 — Long-term stabilityYesAccelerated ageing study; shelf-life dataTF-06.3
ER 5 — Transport and storageYesDistribution simulation testing (ASTM D4169); packaging validationTF-06.4
ER 6 — Acceptable side effectsYesClinical evaluation — benefit-risk assessmentTF-08
ER 7 — Chemical/biological propertiesYes — body contact surfacesISO 10993-1 biological evaluation; biocompatibility reportTF-06.1
ER 8 — Infection / contaminationPartial — device not sterile; cleaning validatedCleaning and disinfection validation report; reprocessing IFUTF-06.5
ER 9 — Measuring functionYes — displays physiological parametersAccuracy validation; comparison against reference standardTF-06.2
ER 10 — Energy source (electrical safety)Yes — mains powered active deviceIEC 60601-1 test report; IEC 60601-1-2 EMC test reportTF-07.1; TF-07.2
ER 11 — RadiationNot applicable — no ionising or non-ionising radiation emission intendedN/A
ER 12 — SoftwareYes — embedded softwareIEC 62304 software lifecycle documentation; software validationTF-09
ER 13 — Self-test/NPTNot applicable — professional use onlyN/A
ER 14 — Active implantable connectionNot applicable — no implanted componentsN/A
ER 15 — Human blood/plasmaNot applicable — no human blood/plasma derivativesN/A
ER 16 — Animal tissueNot applicable — no animal tissue componentsN/A
ER 17 — Administers medicinesNot applicable — does not administer medicinesN/A
ER 18 — Labelling and IFUYesLabelling per Schedule 1 ER 18; IFU reviewed against requirementsTF-04.1; TF-04.2

Worked example framework — General IVD (self-declaration)

ER (Schedule 1A)Applicable?MethodTF Reference
ER 1 — SafetyYesPerformance evaluation; risk management filePEV-01; RM-01
ER 2 — Risk managementYesISO 14971 risk management fileRM-01
ER 3 — PerformanceYesAnalytical performance studies (precision, accuracy, linearity)PEV-02
ER 4 — StabilityYesReagent stability studies; closed-vial/open-vial stabilityPEV-03
ER 5 — TransportYesFreeze-thaw stability; shipping validationPEV-04
ER 6 — Side effectsYesClinical performance evaluation; false rate analysisPEV-02
Schedule 1A — Analytical performanceYesEP studies per CLSI protocolsPEV-02
Schedule 1A — Clinical performanceYesClinical study / literature review; diagnostic sensitivity/specificityPEV-05
Schedule 1A — Calibration traceabilityYesISO 17511 traceability chain documentationCALIB-01
Schedule 1A — IFU requirementsYesIFU reviewed against Schedule 1A checklistLABEL-01
Schedule 1A — LabellingYesLabel design file; regulatory review checklistLABEL-02

Common pitfalls

1. Treating N/A as a get-out-of-jail card

Marking an ER as "not applicable" without justification is a red flag for UKABs. Every N/A must have a device-specific rationale. "Not applicable — device has no measuring function" is acceptable. "Not applicable" with no reason is not.

2. Generic evidence references

Citing "ISO 14971" without specifying the document reference in the technical file is insufficient. Reference the specific report, section, and revision: "Risk Management File v2.1, Section 4: Risk Control Measures."

3. Static checklists

The checklist must be kept current. If the technical file is updated (new test data, design changes, post-market surveillance trigger), the checklist must reflect the change. Outdated cross-references undermine the entire conformity demonstration.

4. Conflating UK MDR 2002 and EU MDR GSPR

EU MDR GSPR (Annex I) has different numbering and more sub-requirements than UK MDR 2002 Schedule 1. A checklist prepared for EU MDR GSPR is not automatically compliant with UK MDR 2002 Schedule 1 (though it will typically exceed it). Check the specific numbering of requirements against the correct legal text for the market.

5. Missing applicable standards

If a UK-designated standard addresses your device type but you are not applying it, you must explain in the checklist why your alternative approach provides at least equivalent conformity. Not applying a relevant designated standard without explanation is an automatic challenge point.


Maintaining the checklist through the device lifecycle

The ER checklist is part of the technical file and must be maintained as a living document. Triggers for checklist review:

  • Design change — any change that affects a device characteristic addressed by an ER
  • New post-market data — adverse events, complaints, or PMS findings that challenge any ER
  • Standard update — when a UK-designated standard is revised, the conformity method may need updating
  • UKAB surveillance audit — the UKAB will typically review the checklist at surveillance audits
  • MHRA inspection — MHRA may review the technical file and checklist during market surveillance


Official references

ReferenceDescription
UK MDR 2002, Schedule 1General device ERs
UK MDR 2002, Part III, Schedule 1AIVD ERs
MHRA: Designated standardsCurrent list of UK-designated standards
ISO 14971:2019Risk management
IEC 60601-1Electrical safety
IEC 62304Software lifecycle