Annex II fixes the technical file's index, not its content

A manufacturer assembling a technical file for the first time often treats Annex II as a content requirement in its own right — a list of things the Regulation wants written down, in whatever order the file's authors happen to produce them. Read the annex closely and it's doing a narrower job than that. MDR 2017/745 Annex II names six sections, in a fixed sequence, that every technical file has to present — but almost none of the substantive standard a reviewer checks that content against lives inside Annex II itself. It's an index: it fixes where each body of evidence has to sit and in what order a notified body will look for it, while the rules for what counts as adequate evidence come from other parts of the Regulation entirely. A file that gets the six sections in the right order but never checks each one against its own governing clause has organized a folder, not demonstrated conformity.

Six sections, not six standards

Annex II lists its six sections in order: device description and specification, including variants and accessories; information to be supplied by the manufacturer, covering labelling and instructions for use; information for the demonstration of conformity with the general safety and performance requirements; design and manufacturing information; benefit-risk analysis and risk management; and product verification and validation. Read on its own, that list looks like six independent asks. It isn't — each section is a placeholder for a body of evidence whose actual adequacy is judged against a different part of the Regulation, or a different harmonized standard entirely, and Annex II's own text never restates those underlying tests. A reviewer opens the file expecting to find each section's evidence exactly where the annex says it belongs; whether that evidence is any good is a question the annex hands off.

The GSPR section imports Annex I's own list, not a new one

Section 3's demonstration of conformity doesn't invent a fresh set of requirements to satisfy — it points straight at Annex I's general safety and performance requirements, the same list a GSPR checklist has to trace hazard by hazard. What Annex II adds is a place to put that demonstration inside the technical file's own structure; the standard the demonstration has to meet was set two annexes earlier. A section 3 that summarizes conformity in prose, without the evidence-by-evidence trace Annex I's own requirements demand, has filled the slot Annex II left open without answering what that slot was actually for.

Risk management gets a section; ISO 14971 supplies the method

Section 5 asks for a benefit-risk analysis and risk management documentation, but Annex II doesn't specify how a manufacturer should run that analysis — the harmonized standard for risk management, ISO 14971, is what governs the methodology, the acceptability criteria, and what a risk management file has to prove, hazard by hazard. A technical file that places a risk summary in Section 5 without the underlying file ISO 14971 requires has satisfied the annex's own placement rule while leaving the substantive question — is the residual risk actually acceptable, and on what basis — unanswered anywhere in the file.

Design and verification sections point straight at ISO 13485's own clauses

Sections 4 and 6 — design and manufacturing information, and product verification and validation — are where the design-control record set lives, but that record set's own content requirements come from ISO 13485 Clause 7.3, not from Annex II. The design file this blog has already covered is built to that clause's own structure precisely so it can be dropped into these two Annex II sections without a second reorganization. A file that builds its design records around Annex II's section headings alone, without checking them against Clause 7.3's own list, risks a design file that looks complete inside the technical file's table of contents and is missing pieces the clause actually requires.

Where this meets the file

Annex II's real value is structural: it's the fixed index that lets a notified body reviewer, working through six sections in a known order, find the GSPR trace where Annex I expects it, the risk file where ISO 14971 expects it, and the design records where Clause 7.3 expects them — without having to hunt for evidence a differently organized file might have buried somewhere else. A technical-file index worksheet built around Annex II's own six sections, cross-referenced to the clause or annex that actually governs each one's content, is previewed in the launch catalog. If your program orders its own file differently, the shelf takes that correction directly.