Records · The complete guide

Technical File

TL;DR

The controlled evidence dossier — physical or electronic — that demonstrates a CE-marked product meets every applicable requirement of every applicable EU act and supports the manufacturer's EU Declaration of Conformity. For medical devices the contents are prescribed by MDR Annex II (general technical documentation) + Annex III (post-market surveillance documentation), and for IVDs by IVDR Annex II + III. For other CE-regulated categories (machinery, LVD, EMC, RED, PPE, pressure equipment) the analogous 'technical documentation' contents are defined by the applicable act. Notified Bodies sample the technical file during conformity assessment; market-surveillance authorities can demand the full file at any point during the retention period (10 years post-last-unit for most devices; 15 years for implantables).

Reviewed · By V5 Ultimate compliance team· 3,935 words · ~18 min read

01What a technical file actually is

A technical file (or, under MDR / IVDR, 'technical documentation') is the controlled, structured evidence dossier the manufacturer assembles, maintains and keeps available to demonstrate that a CE-marked product meets every applicable requirement of every applicable EU harmonisation act. It is the substantive basis of the EU Declaration of Conformity — the DoC is the legal statement; the technical file is the evidence behind that statement.

The file is not a one-shot deliverable produced for launch and put on a shelf. It is a living controlled record updated through the product's commercial life: design changes, supplier changes, manufacturing-process changes, harmonised-standard revisions, post-market surveillance data, vigilance reports, FSCAs, significant changes notified to the Notified Body. Inspectors and Notified Bodies expect to see the current state, with version history, change-control rationales, and links to the underlying controlled records (DHF, DMR, batch records, training records, QMS procedures).

The file may be electronic or physical. There is no required format — the requirement is that it be 'clear, organised, readily searchable, unambiguous' (MDR Annex II §1) and available to competent authorities on request. Most manufacturers maintain an electronic file structured exactly against the relevant annex with sectioned PDFs / documents and a master index. Notified Bodies routinely ask for the file in indexed PDF form for technical-documentation assessment.

02Who must hold the file and for how long

The manufacturer is the primary holder. For non-EU manufacturers, the authorised representative (per MDR / IVDR Article 11 or the sector analogue) must hold a copy or have permanent access to the file and produce it on request to a competent authority. Importers must hold the EU DoC and ensure the manufacturer holds the technical file; distributors do not need to hold the full file but must verify the DoC is in place.

Retention periods are set by the applicable act:

  • MDR Article 10(8) — at least 10 years after the last device covered by the DoC has been placed on the market; 15 years for implantable devices.
  • IVDR Article 10(7) — at least 10 years after the last IVD has been placed on the market.
  • Machinery Regulation (EU) 2023/1230 — at least 10 years from the date of manufacture (extends to 15 for safety components in some cases).
  • LVD / EMC / RED / PPE — typically 10 years from the date the product was placed on the market.
  • GPSR (EU) 2023/988 — 10 years for the relevant traceability records and internal documentation for consumer products covered.

Retention runs from the last unit placed on the market — not from initial launch. This makes the file lifecycle obligation extend years past commercial discontinuation. Many manufacturers under-scope retention and lose the ability to defend the device in market-surveillance enquiries arising from field issues 8-12 years after last sale.

03MDR Annex II — what must be in the technical documentation

Annex II prescribes six main sections for the general technical documentation. The structure is mandatory; the depth scales with risk class.

  1. 1. Device description and specification, including variants and accessories — intended purpose, intended user, intended patient population, principles of operation, list of variants / configurations / accessories, novelty claim, reference to predecessor / similar devices and prior generations, photo / drawing / schematic, list of raw materials, software (where applicable) with version / build identifiers.
  2. 2. Information to be supplied by the manufacturer — label, packaging, IFU, language requirements per Member State (every EU language for the markets supplied), training materials, accessory IFUs, summary of safety and clinical performance (SSCP) for Class III and implantable per Article 32.
  3. 3. Design and manufacturing information — design stages (linked to design controls), manufacturing process flow, identification of all manufacturing and design sites including critical suppliers / subcontractors, in-process and final acceptance criteria, packaging design, sterilisation method validation (where applicable) per ISO 11135 / 11137 / 17665.
  4. 4. General Safety and Performance Requirements (GSPR) — the GSPR matrix (Annex I requirements as rows, applicability with rationale, harmonised standards used, cited evidence documents). Inspectors sample rows; incomplete applicability rationale is the #1 opening finding.
  5. 5. Benefit-risk analysis and risk management — the ISO 14971 risk-management file (risk-management plan, risk analysis, risk evaluation, risk control, residual-risk evaluation, overall residual-risk acceptability, risk-management report) integrated with the clinical evaluation conclusions.
  6. 6. Product verification and validation — design verification + validation evidence per design controls, biocompatibility per ISO 10993, sterilisation validation, software lifecycle per IEC 62304, usability per IEC 62366-1, electrical safety + EMC per IEC 60601 series, performance testing, animal data (where applicable), clinical evaluation report per Article 61 + Annex XIV, PMCF plan + reports per Annex XIV Part B, stability / shelf-life data.

04MDR Annex III — post-market surveillance documentation

Annex III is the second compartment of the medical-device technical documentation — the post-market surveillance file. It is a separate annex deliberately, so post-market evidence is auditable independently from design / launch evidence.

  • PMS plan per Article 84 — proactive + reactive data sources, methods + processes for collection, indicators / threshold values for re-evaluation, methods for investigation of complaints + trends, methods for communication with authorities + Notified Bodies + economic operators, reference to procedures for vigilance + FSCA + trend reporting.
  • PMS report per Article 85 (Class I) — updated when necessary, available to the competent authority on request.
  • Periodic Safety Update Report (PSUR) per Article 86 (Class IIa, IIb, III) — updated at least every two years (IIa) or annually (IIb, III), reviewed by the Notified Body for Class IIb / III, submitted via EUDAMED when the relevant module is mandatory.
  • Trend reporting per Article 88 — methodology + thresholds for statistically significant trends in non-serious incidents.

Annex III is not a slimmed-down Annex II — it is its own annex, with its own audit scope, its own cadence, and its own finding pattern. Stale or template-only PSURs and PMS plans that contain no actual post-market data are the most-cited Annex III findings.

05IVDR Annex II + III — the IVD differences

IVDR Annex II + III mirror MDR Annex II + III structurally with IVD-specific adaptations. Key differences:

  • The performance evaluation report (PER) per Annex XIII Part A — integrating scientific validity + analytical performance + clinical performance — replaces the medical-device clinical evaluation report (CER). PER must include literature search methodology, traceability per ISO 17511, and lifecycle integration with PMPF data.
  • Annex III references PMPF (Post-Market Performance Follow-up) per Annex XIII Part B — analogous to PMCF — and PMPF is default mandatory (absence requires explicit justification).
  • PSUR cadence differs by IVD class: Class C every 2 years; Class D annually with submission via EUDAMED; Class A + B PMS report only.
  • Class D devices have additional documentation requirements relating to EU Reference Laboratory verification per Article 100 + Implementing Regulation (EU) 2022/944 (where designated for the device category).
  • Class IVDs with a measuring function or with self-test / lay-user intended use have additional human-factors deliverables under IEC 62366 and additional comprehension-study evidence under Annex I §20.

06The GSPR matrix — the most-audited single artefact

Annex I of MDR (and IVDR) contains the General Safety and Performance Requirements — 23 requirements (MDR) / 20 requirements (IVDR) covering safety, performance, design, manufacture and information supplied. The GSPR matrix is the controlled table that maps every requirement to (a) applicability (Yes / No / Not applicable) with rationale for any 'No' / 'NA'; (b) harmonised standards relied upon, cited with year + clause(s); (c) the controlled evidence document(s) in the technical file that demonstrate conformity; (d) verification of conformity status.

The GSPR matrix is the #1 sampled artefact during Notified Body technical-documentation assessment and the #1 source of opening findings. Common failure modes:

  • Applicability rationale missing for requirements marked 'NA'.
  • Harmonised standard cited without year — the OJ-listed version drives presumption of conformity, so the citation must be precise.
  • Standard cited but withdrawn from the OJ — the presumption no longer applies; evidence must be re-anchored.
  • Evidence reference points to an obsolete document version or to a document that does not actually demonstrate the requirement.
  • Requirement marked conformant by 'manufacturer's internal procedure' with no traceable evidence package.
  • Clinical / performance evidence claimed in the matrix but the underlying CER / PER is incomplete or stale.

07Lifecycle maintenance — the file is never 'done'

The technical file is a controlled record under the QMS. Every change that affects an item in the file must be processed through change control, the affected chapter(s) re-issued, the cross-references updated, and (where the change is significant per MDCG 2020-3 / 2022-14 or sector analogue) the Notified Body notified before implementation.

Triggers for technical-file update:

  • Design change — new variant, new accessory, new indication, new packaging configuration, new materials, software update.
  • Manufacturing-process change — new site, new critical supplier, new sterilisation cycle, new packaging line, contract-manufacturer change.
  • Harmonised-standard revision — when a referenced standard is updated and listed in the OJ, the citation + evidence must move to the new version within the OJ-defined transition.
  • Risk-management update — new hazard identified, residual-risk re-evaluation following PMS data, ISO 14971 §10 lifecycle activities.
  • PMS data — quarterly / annual aggregation; PSUR cycle; complaints + vigilance + FSCA + Article 88 trend reporting.
  • Clinical / performance evaluation update — new PMCF / PMPF data, new literature, new clinical study results, equivalence-relied-upon predicate withdrawn.
  • Regulatory update — MDR / IVDR amendment, MDCG guidance change, Commission Implementing Act, common-specification publication.
  • Significant-change notification accepted by NB — update the file to reflect the post-change state with the NB notification + acceptance correspondence as controlled records.

08Technical documentation for other CE-regulated categories

Outside medical devices, every CE-regulated category has its own technical-documentation requirements. The structure varies but the function is identical — evidence of conformity with the applicable act, lifecycle-maintained, produced on demand.

ActTechnical file annex / articleNotes
Machinery Regulation (EU) 2023/1230 (applies 14 Jan 2027)Annex IVDetailed contents: drawings, calculations, test reports, EN ISO 12100 risk-assessment, instructions, control diagrams, software description for safety-related functions.
Low Voltage Directive 2014/35/EUAnnex IIIDesign / manufacturing description, drawings, list of harmonised standards, test reports, risk analysis where appropriate.
EMC Directive 2014/30/EUAnnex IIApparatus description, harmonised standards applied / EMC assessment when not, test reports.
Radio Equipment Directive 2014/53/EUAnnex VRED applies essential requirements 3.1 + 3.2 + 3.3 (incl. cybersecurity per Delegated Reg 2022/30 from 1 Aug 2025). Detailed RF test reports, cybersecurity risk assessment for in-scope categories.
PPE Regulation (EU) 2016/425Annex IIIPPE category I/II/III drives module routing; categories II + III require NB involvement. Detailed risk analysis + ergonomic + heat / fire / chemical performance evidence per relevant EN standards.
Pressure Equipment Directive 2014/68/EUAnnex IIIModule-specific contents; design calculations, materials certificates per EN 764-5, NDE reports, weld procedure / welder qualifications, hydrostatic test records.
Toy Safety Directive 2009/48/ECArticle 21 + Annex IVSafety assessment per Annex II + EN 71 series, hazard / chemical assessments.

For multi-act products (e.g. a connected diagnostic device — IVDR + LVD + EMC + RED + RoHS), the manufacturer may maintain a single integrated technical file covering all acts, or separate files per act. Integrated files are more common and reduce duplication of common chapters (device description, manufacturing, risk management); the file index must clearly map each chapter to each applicable act.

09Common technical-file findings

  • Index missing or out of sync — chapters added / removed without index update.
  • Version control inconsistent across chapters — Annex II §1 device description at v4, IFU at v3, GSPR matrix referencing v2 evidence.
  • GSPR matrix incomplete applicability rationale.
  • Harmonised standards cited without year / clause, or cited with a withdrawn version.
  • Clinical / performance evaluation stale — last update >2 years, no PMCF / PMPF integration.
  • Risk-management file static — no §10 lifecycle activity, no integration of post-market data.
  • Software documentation incomplete — IEC 62304 deliverables thin, SOUP register absent, cybersecurity per MDCG 2019-16 not addressed.
  • Sterilisation validation tied to worst-case loading configuration not demonstrated, or transferred to a new site without re-validation.
  • Critical suppliers / subcontractors list incomplete — common after CMO change without file update.
  • Annex III PMS plan template-only — no actual post-market data sources, no thresholds, no methodology.
  • PSUR cadence not aligned to class — Class IIb annual cycle missed.
  • Significant changes implemented without Notified Body notification per MDCG 2020-3 / 2022-14 — invalidates the certificate.
  • EU authorised representative mandate or details missing / outdated for non-EU manufacturers.
  • Retention scope under-set — files removed when product commercially discontinued instead of from last-unit-placed-on-market date.
  • EUDAMED registration not maintained for new variants / significant changes / certificate revisions.

10Metrics worth tracking

  • Technical-file completeness score (sections present + signed + in-version).
  • GSPR matrix coverage % + evidence-link integrity %.
  • Harmonised-standards currency % vs OJ.
  • Days since last CER / PER update vs required cadence.
  • Risk-management file lifecycle-update cadence vs ISO 14971 §10 plan.
  • PSUR on-time submission rate per class.
  • Annex III PMS plan currency.
  • Significant-change notifications submitted vs NB acceptance turnaround.
  • Mean time from change-control approval to technical-file chapter re-issue.
  • Critical-supplier list completeness vs PO / receiving data.
  • Authorised representative mandate currency for non-EU manufacturers.
  • Retention scope compliance (last-unit-placed vs commercial-discontinuation date).

11How V5 Ultimate supports the technical file

V5 Ultimate treats the technical file as a controlled workspace structured exactly against the applicable annex — MDR Annex II + III, IVDR Annex II + III, or the relevant sector-specific annex. Each chapter is a versioned controlled document with linked evidence, change-control routing, and review / approval e-signatures (CFR Part 11 / Annex 11 compliant). The master index is auto-generated from the chapter manifest with version-state visibility and gap flagging — chapters out of version, missing approvals, or with broken evidence links are surfaced before the file is exported for NB submission.

The GSPR matrix is a live workspace — every applicable Annex I requirement is a row, every applicability marker carries a mandatory rationale, every harmonised standard is cited with year + clause from the standards register (which tracks OJ publication / withdrawal dates), and every evidence link resolves to a current controlled document. Standard withdrawals from the OJ trigger a re-anchoring workflow before the presumption of conformity lapses. The risk-management file, software lifecycle deliverables (IEC 62304), usability engineering file (IEC 62366), biocompatibility (ISO 10993), sterilisation validation, electrical-safety / EMC test reports, and clinical / performance evaluation reports are all controlled chapters with cross-references back into the GSPR matrix.

Annex III PMS documentation is a distinct workspace — PMS plan, PMS report, PSUR, trend-reporting methodology — with cadence enforcement per device class and EUDAMED export packaging for Class IIb / III / D PSURs. Significant-change decision-tree routing (per MDCG 2020-3 / 2022-14) is built in; any change that meets the significant-change criteria is auto-routed to the NB notification queue, blocking implementation until acceptance is recorded. Retention scope is anchored to last-unit-placed-on-market data (not commercial discontinuation), and authorised-representative mandate currency is tracked at the device-record level for every non-EU manufacturer relationship.

Frequently asked questions

Q.Is the technical file the same as the DHF?+

No, but they overlap. The DHF (Design History File) per 21 CFR 820.30(j) / QMSR is the design-controls record proving how the device was designed. The technical file per MDR Annex II + III is the broader CE evidence dossier — it includes design evidence (often pulled from the DHF) but also production / sterilisation / packaging / labelling / clinical evaluation / PMS / vigilance / authorised-representative / DoC content. In well-structured QMS systems the DHF feeds the design chapters of the technical file; the technical file is the superset.

Q.Can the technical file be entirely electronic?+

Yes. MDR / IVDR + the Blue Guide explicitly permit electronic technical files provided they are clear, organised, readily searchable, unambiguous, and produced on demand. Most modern manufacturers maintain electronic files. The Notified Body submission package is typically an indexed PDF export from the electronic system.

Q.How long must I keep the technical file?+

Per MDR Article 10(8): at least 10 years after the last device covered by the DoC has been placed on the market; 15 years for implantable devices. Per IVDR Article 10(7): 10 years for IVDs. Retention runs from last-unit-placed-on-market — not from commercial discontinuation. Many manufacturers under-scope this and lose the ability to defend devices in market-surveillance enquiries arising years post-discontinuation.

Q.Who can ask to see my technical file?+

Competent authorities (national market-surveillance authorities per Regulation (EU) 2019/1020), the Notified Body during conformity-assessment and surveillance activities, the European Commission in coordinated market-surveillance actions, and (for IVDs) the EU Reference Laboratory designated for Class D categories. Customers and competitors do not have a right to access — though the public-facing summary documents (SSCP for Class III / implantables, SSP for IVD Class C / D, IFU) are intentionally published.

Q.What happens if a referenced harmonised standard is withdrawn from the OJ?+

The presumption of conformity tied to that standard ends at the OJ-specified date. The manufacturer must move conformity evidence to (a) the updated version of the standard listed in the OJ, (b) an alternative harmonised standard, or (c) a direct demonstration against the GSPR / essential requirement using other technical means. The GSPR matrix must be updated with the new evidence anchor and the technical file re-issued. The Notified Body must be notified if the change is significant per the change-classification guidance.

Q.Do I need a separate technical file per Member State?+

No. The technical file is unified for the entire EEA. Language requirements apply to certain customer-facing documents (IFU, labelling, SSCP / SSP for medical devices) per the Member State where the product is placed on the market — but the technical file itself can be maintained in a single working language (typically English). The Notified Body works in the language agreed in the Article 53 written agreement (typically English).

Q.Does Class I medical device really need a technical file?+

Yes — Annex II + III apply to all classes. The depth scales with risk but the structural requirements (device description, IFU, GSPR matrix, risk-management file, performance evidence, PMS plan, PMS report) are mandatory for every Class I device. MDCG 2019-15 is the operational guidance specifically for Class I and is the single most under-applied piece of MDR guidance — Class I is not 'CE marking lite'.

Primary sources

Further reading

Explore this topic

Technical File sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.

Batch & device records
16 related entries

Master and executed records that prove a batch or device was made to spec.

See Technical File working on a real shop floor

V5 Ultimate ships with the Technical File controls already wired in — audit trail, e-signatures, validation evidence. Free trial, no credit card, onboard in days, not months.

Language