“What is the PMCF deadline for my device?” is one of the most common questions small manufacturers ask — and it is the wrong question. Post-Market Clinical Follow-up under EU MDR is not a dated milestone you hit once. It is a continuous process, and the only thing that varies by device class is how often you have to write it up and who reads it. This guide separates the two ideas that people conflate — the ongoing PMCF activity and the reporting cycle that drives it — and then gives you a class-by-class table of exactly what is due, how often, and where it goes.

First: There Is No Single “PMCF Deadline”

PMCF lives in Annex XIV, Part B of the MDR. It is defined there as a continuous process that proactively collects and evaluates clinical data from devices already on the market, in order to confirm safety and performance throughout the device’s lifetime and to keep the clinical evaluation up to date. Nothing in Part B sets a calendar date. The obligation is permanent, not periodic.

So why do people talk about PMCF “deadlines”? Because the continuous activity has to surface in documents that do have a cadence — and that cadence is set by your device class. There are two clocks to keep separate:

Practical consequence: if you only update your PMCF evaluation report the day before an audit, you have already failed the standard. The data collection should be live and dated continuously; the report is a periodic snapshot of an activity that never stops.

What PMCF Actually Requires (Every Class)

Two documents sit at the core of PMCF, and both are part of your technical documentation regardless of class:

PMCF applies to every device class — including Class I. There is no automatic exemption for low-risk devices. A manufacturer may conclude that PMCF is not appropriate for a specific device, but only if that conclusion is justified and documented in the PMS plan, with a rationale based on the device and its clinical data. “It’s only Class I” is not a justification; a reasoned argument that the existing clinical evidence is already sufficient and stable might be.

The Three Reporting Clocks

Your PMCF findings have to land in one of these reporting documents. Which one, and how often, is set entirely by your class:

1. PMS report — Class I (Article 85)

For Class I devices, the post-market surveillance data — including PMCF findings — is summarised in a post-market surveillance report. It is updated when necessary and made available to the competent authority on request. There is no fixed periodicity and no Notified Body involvement (Class I devices are self-declared, except the Is/Im/Ir sub-classes for the relevant aspect).

2. PSUR — Class IIa, IIb and III (Article 86)

For Class IIa and above, the equivalent document is the Periodic Safety Update Report (PSUR), and here the frequency is written into the regulation:

The PSUR summarises the results of the PMS plan, draws conclusions, and documents any preventive and corrective actions. Except for custom-made devices, it is part of the technical documentation.

3. PMCF evaluation report & CER updates (Annex XIV / Article 61)

The PMCF evaluation report and the clinical evaluation are updated throughout the device’s life cycle. For Class III devices and implantable devices, the MDR is specific: the PMCF evaluation report and, where indicated, the Summary of Safety and Clinical Performance must be updated at least annually with the new clinical data. For other classes there is no fixed annual rule — the report is updated as necessary, in practice aligned to the PSUR cycle above.

PMCF & Reporting Cadence by Device Class

Putting the three clocks together, here is what each class is actually on the hook for. “Continuous” in the first column is the PMCF activity itself; the deadlines live in the reporting columns:

Class Reporting document & minimum cadence PMCF evaluation report Reviewed by Notified Body?
Class I PMS report (Art. 85), updated when necessary Updated as necessary; feeds the PMS report and CER No — available to competent authority on request
Class IIa PSUR (Art. 86), at least every 2 years (and when necessary) Updated as necessary; aligned to the PSUR cycle No — on request to NB / competent authority
Class IIb (non-implantable) PSUR (Art. 86), at least annually Updated as necessary; aligned to the annual PSUR On request to NB / competent authority
Class IIb implantable & Class III PSUR (Art. 86), at least annually, submitted via EUDAMED Updated at least annually (with SSCP where applicable) Yes — NB reviews the PSUR and adds its evaluation

Note the two thresholds that matter most. The first is Class IIa → IIb, where the PSUR cadence tightens from two years to annual. The second is Class III / implantable, where the PSUR stops being a document you keep on file and becomes one you actively submit to your Notified Body through EUDAMED, and the PMCF evaluation report itself becomes an annual obligation.

Class III and Implantables: The Strict End

For implantable and Class III devices the regime is materially heavier, and three points are worth isolating because they are where audits find gaps:

Where Small Manufacturers Get Caught

The deadlines themselves are simple once you see the table. The findings almost always come from misunderstanding what the cadence requires:

If your device mixes classes across a product family, remember the PSUR can be written “for each device and where relevant for each category or group of devices” — but the cadence is set by the highest class in the group.

Keep every PMCF and PSUR deadline in one place

Our free Submission Tracker lets you log each device, its class, and its reporting cycle — so the annual PSUR, the PMCF evaluation report and the CER update never drift out of sync or sneak up on you.

Open the Submission Tracker
Share this article:

Sources and further reading