When Does the 15-Day Clock Actually Start?

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

This scenario plays out more often than it should. The 15-day reporting timeline under MDR Article 87 seems straightforward until you face a real incident with unclear causality, evolving information, and internal delays. Then the question becomes urgent: when exactly does the clock start?

Understanding the trigger is not academic. It determines whether your organization is compliant or facing enforcement action. It shapes how your quality team documents awareness. And it defines how your vigilance process must operate under pressure.

What Article 87 Actually Says

MDR Article 87 requires manufacturers to report serious incidents without delay. For incidents occurring in the EU, the deadline is 15 days from the date of awareness.

The critical term is awareness. Not confirmation. Not investigation completion. Not root cause analysis. Awareness.

MDCG 2020-10-1 clarifies this further. Awareness means the moment the manufacturer has sufficient information to establish that a device is linked to an event that meets the definition of a serious incident. Sufficient does not mean complete. It does not mean causality is proven. It means you have enough to reasonably suspect the link.

This is where manufacturers often misjudge the obligation.

What Establishes Awareness?

Awareness is triggered when the manufacturer receives information that meets two conditions:

First, an incident occurred involving their device. This could come from a customer complaint, a field report, a social media post, a clinical partner, or internal testing. The source does not matter. What matters is that the manufacturer receives the information.

Second, the incident meets the definition of a serious incident under MDR Article 2(65). This means it directly or indirectly led to death, serious deterioration in health, serious public health threat, or could lead to these outcomes if it recurred.

When both conditions are met, the clock starts. Even if the manufacturer does not yet know why it happened. Even if they need more investigation. Even if they are not sure the device caused it.

The standard is reasonable suspicion, not proof.

The Role of Causality

Here is where confusion enters. Manufacturers ask: if causality is unclear, how can I be aware of an incident?

The answer lies in how the regulation treats causality. You do not need to prove the device caused the outcome. You need to establish that the device is implicated. If the device was involved in a procedure where a serious outcome occurred, and there is no immediate alternative explanation, that is sufficient.

Consider a surgical instrument that breaks during use. The patient suffers a serious complication. The manufacturer receives the complaint on Monday. By Wednesday, they know the instrument broke and the complication occurred. They do not yet know if the break caused the complication. But the device is implicated. Awareness exists.

Causality will be assessed during the investigation. The report can be updated. But the initial report is due within 15 days of Wednesday, not 15 days after the investigation concludes.

What Delays the Clock?

Manufacturers sometimes argue that the clock should start later because critical information was missing. This rarely succeeds.

The regulation does not allow you to delay awareness by choosing not to gather information. If you receive a complaint that describes a serious outcome, you cannot delay the clock by waiting weeks to request the device back or to interview the user.

Competent Authorities and Notified Bodies expect proactive information gathering. If you become aware of a potential serious incident, you should immediately seek the details needed to assess it. The clock starts when you receive the initial report, not when you finally obtain the device or the medical records.

There is one exception. If the initial report is so vague that it does not establish an incident occurred, awareness does not yet exist. For example, a user reports discomfort but no outcome. Later, you learn the discomfort was linked to a device malfunction causing tissue damage. The clock starts when you learn about the tissue damage, not when you first heard about discomfort.

But this exception is narrow. If the initial report describes an outcome that could be serious, awareness begins there.

Internal Routing Delays

Another common issue: the information reaches the company, but not the right person. A complaint is logged by customer service, but vigilance is not notified until days later. When does the clock start?

From the regulator’s perspective, the clock starts when the company receives the information, not when the vigilance team sees it. The expectation is that your quality system ensures timely routing. If your internal processes delay awareness by the responsible person, that is a system deficiency, not a reason to adjust the timeline.

This has direct implications for how you design complaint handling and escalation procedures. Information about serious outcomes must reach vigilance immediately, not through weekly review meetings.

What Happens When You Miscalculate?

Late reporting is not treated lightly. Competent Authorities view it as a failure to protect public health. The consequence ranges from warning letters to suspension of certificates, depending on severity and pattern.

But beyond the immediate enforcement risk, late reporting creates deeper problems. It undermines trust with the Competent Authority. It signals weak quality systems. And it often leads to more scrutiny across your entire portfolio.

I have seen manufacturers lose months of progress on new submissions because a Notified Body flagged systematic delays in incident reporting. The issue was not the incidents themselves. It was the failure to recognize when the clock started.

The regulatory logic is simple: if you cannot correctly identify when awareness begins, how can you be trusted to manage post-market obligations?

How to Implement This in Practice

The solution is not complex, but it requires discipline. Your vigilance procedure must define awareness in the terms the regulation uses, not in the terms your team prefers.

First, train everyone who receives complaints or field reports to recognize language that suggests a serious outcome. Death, hospitalization, surgery, permanent impairment, public health risk. These terms should trigger immediate escalation, even if causality is unclear.

Second, establish a same-day routing protocol. When potential serious incident language appears, vigilance must be notified within hours, not days. The assessment of whether it meets the definition happens quickly, with documented reasoning.

Third, adopt a low threshold for awareness. If you are debating whether the clock has started, it probably has. Report within the timeline and update later if the investigation shows the incident did not meet the definition. That is acceptable. Late reporting because you waited for certainty is not.

Fourth, document the awareness date explicitly in every incident file. Not the date you completed the investigation. Not the date you confirmed causality. The date you received sufficient information to reasonably suspect a serious incident.

This documentation is what the Competent Authority or Notified Body will review during audit. If the dates do not align with the complaint records, you will be challenged.

Why This Matters Beyond Compliance

The 15-day timeline is not arbitrary. It reflects the public health urgency of serious incidents. Delays mean other users remain at risk longer. Competent Authorities need timely information to decide whether broader action is needed.

But there is also a strategic reason to get this right. Manufacturers who consistently report on time with clear awareness documentation build credibility. When a complex incident arises, when causality is genuinely uncertain, these manufacturers are more likely to be heard when they explain why an incident does not meet the definition.

The manufacturer who has a history of late reporting and stretched interpretations of awareness will not receive that benefit of the doubt.

Your vigilance system is not just about avoiding enforcement. It is about demonstrating that you take post-market obligations seriously, that your quality systems work under pressure, and that you understand the regulator’s perspective.

Getting the 15-day clock right is one of the simplest ways to demonstrate that competence.

What Comes Next

Understanding when the clock starts is only the beginning. The next challenge is knowing what to include in that initial report, how to structure follow-up updates, and how to manage incidents that span multiple jurisdictions.

These are not theoretical questions. They are the daily reality of vigilance under MDR. And each one has patterns that regulators recognize, deficiencies they flag, and solutions that work in practice.

The 15-day timeline is non-negotiable. The only variable is whether you recognize awareness when it happens.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.