A written gap report against Annexes I, II and III
We read your technical documentation against Annexes I, II and III of the MDR or IVDR and give you a written gap report, section by section. You see what is missing, what is inconsistent and what each gap is based on, before a notified body, a competent authority or a registration authority sees it. To start, send us the device list and the documentation index.
Who this is for
Manufacturers of self-declared Class I and Class A devices, where no notified body reads the file before the device reaches the market.
Manufacturers preparing a file for a notified body, who want an independent read before submission.
Manufacturers outside the EU appointing an authorised representative, who has to verify the documentation before accepting the mandate.
Manufacturers registering devices in Türkiye, where the documents in the registration file have to agree with the technical documentation behind them.
What the Regulation requires
The obligation to draw up and maintain the documentation sits with the manufacturer:
"Manufacturers of devices other than custom-made devices shall draw up and keep up to date technical documentation for those devices. The technical documentation shall be such as to allow the conformity of the device with the requirements of this Regulation to be assessed. The technical documentation shall include the elements set out in Annexes II and III." (MDR Article 10(4))
Annex II also sets the standard for how the documentation is presented:
"The technical documentation and, if applicable, the summary thereof to be drawn up by the manufacturer shall be presented in a clear, organised, readily searchable and unambiguous manner and shall include in particular the elements listed in this Annex." (MDR Annex II)
Annex III adds the post-market part of the file:
"The technical documentation on post-market surveillance to be drawn up by the manufacturer in accordance with Articles 83 to 86 shall be presented in a clear, organised, readily searchable and unambiguous manner and shall include in particular the elements described in this Annex." (MDR Annex III)
The IVDR follows the same structure in its own Annexes II and III.
What we review
We go through the file in the order of Annex II, then Annex III.
Device description and specification, including variants and accessories: intended purpose, intended users, Basic UDI-DI, classification and the rule applied.
Information to be supplied by the manufacturer: the label and the instructions for use, in the languages required.
Design and manufacturing information: whether the design stages and manufacturing sites are identified.
General safety and performance requirements: whether each applicable requirement of Annex I is matched to evidence.
Benefit-risk analysis and risk management: whether the risk file is complete and linked to the rest of the documentation.
Product verification and validation: whether the reports you hold are referenced and match the device, including clinical evaluation.
Post-market surveillance: whether the plan, and the report or PSUR for your class, are in place.
The GSPR mapping
The core of the review is a table built on Annex I. For each general safety and performance requirement we record whether it applies to your device, which document gives the evidence, which standard or common specification is used, and whether the evidence is in the file. A requirement that applies but has no evidence becomes a gap. A requirement marked as not applicable without a reason becomes a gap. A standard cited in one document in one edition and in another document in a different edition becomes a gap. Our guide to the GSPR checklist explains how the table works.
How deep the review goes, by class
For a self-declared Class I or Class A device, the review covers the whole file, because no notified body will read it before the device reaches the market. For Class I devices that are sterile, have a measuring function or are reusable surgical instruments, we also flag the parts the notified body will look at. For devices in higher classes the review is a read before the notified body submission or before a renewal, with the same table and the same report.
Process
You send the device list and the documentation index. We confirm the scope and send a proposal per device family.
You share the documentation. We read it against Annexes I, II and III.
We send the gap report. Each gap has the section, what is missing or inconsistent, the requirement it is based on, and what would close it.
You or your team close the gaps. Where you ask us to, we compile the technical documentation from the documents you provide.
We read the updated file and close each gap in the report.
What you receive
A gap report, section by section, with the basis for each finding.
The GSPR table for the device family.
A summary showing which sections are complete, which have gaps and which are missing.
A list of the changes the gaps require in the EU declaration of conformity, the label or the instructions for use. Our EU declaration of conformity service covers the declaration itself.
What we need from you
The device list with risk class, intended purpose and Basic UDI-DI.
The technical documentation as it stands, or at least its index.
The label and the instructions for use.
The test and verification reports you already hold. We read them for their fit with the documentation. We do not assess the test results themselves.
The notified body certificate, where one applies.
Out of scope
Notified body conformity assessment and certification.
Testing and laboratory work, including choosing a laboratory or arranging tests.
Interpreting or changing your technical specifications.
Finding importers or distributors.
Related services
FAQs
Do you write the technical documentation or only review it?
Both. The review is the standard service. Where you ask us to, we compile the technical documentation from the documents you provide. The design, the tests and the data stay yours.
Can you tell me which tests my device needs?
No. Testing and laboratory work are outside our scope. We read the reports you already hold and check that they match the device and are referenced in the documentation.
Is a gap review useful for a Class I device?
It is where it matters most. A self-declared Class I device reaches the market without a notified body reading the file, so the first outside reader may be a competent authority.
Do you review IVDR files as well?
Yes. The IVDR uses the same structure in its Annexes II and III, and we review it against the IVDR's own Annex I.
Does the review include the post-market surveillance part?
Yes. Annex III is part of the technical documentation, so the plan and the report or PSUR for your class are in the review.
How is the review priced?
Per device family, after we see the device list. A family is the group of devices under one Basic UDI-DI.
