The remedial-action call sets the clock

Two device malfunctions can look identical on paper — same failure mode, same product code, same number of units affected — and still land on different FDA reporting clocks. One becomes a routine 30-day report. The other has to reach FDA within five working days. The difference isn’t the malfunction. It’s a judgment call the manufacturer makes about itself, on a schedule that starts running the moment the right person inside the company learns of it.

Two clocks, two different questions

Under 21 CFR 803.50, a manufacturer reports within 30 calendar days after becoming aware of information that reasonably suggests one of its marketed devices malfunctioned, and that the device or a similar one would be likely to cause or contribute to death or serious injury if the malfunction recurred. That’s the routine track, and most MDR-reportable malfunctions travel it.

Under 21 CFR 803.53, the same manufacturer reports within five working days instead, if the reportable event necessitates remedial action to prevent an unreasonable risk of substantial harm to the public health — or if FDA has asked, in writing, for 5-day reports on that class of event. The trigger for the faster clock isn’t how severe the injury was. It’s whether the manufacturer’s own review concluded the device needs a remedial action, right now, to keep the same thing from happening again at scale.

The clock starts on a narrower kind of knowing

The two tracks don’t even share the same definition of when a manufacturer “knows.” 21 CFR 803.3 defines becoming aware, for the 30-day standard, as any employee acquiring information that reasonably suggests a reportable event occurred. For the five-day trigger, the definition narrows: a manufacturer becomes aware only when an employee with management or supervisory responsibility over regulatory, scientific, or technical staff — or whose duties relate to collecting and reporting adverse events — learns, from any information including trend analysis, that an event necessitates remedial action. A field engineer hearing about a malfunction starts one clock. That same fact reaching a quality director doing trend analysis can start the other, on a different date, from the same underlying event.

The regulation doesn’t ask how bad the malfunction was. It asks who inside the company knew, in what role, and what they concluded about fixing it.

What a public record can and can’t show

FDA Radar doesn’t ingest MAUDE reports today — per what we monitor and how often, adverse-event data is deferred pending the statistical care per-product analysis needs, not silently skipped. That gap matters here specifically: piecing together why a given malfunction report moved fast isn’t a matter of reading a field that says so. It means reading the outcome of an internal determination — who inside the company learned what, when, and what that person concluded about remedial action — that happened before the report existed at all.

The practice

For a small RA or quality team building its own MDR discipline, the operative question isn’t “how serious was this malfunction.” It’s whether the review that reaches a remedial-action conclusion is actually reaching the right desk — a supervisor over regulatory, scientific, or technical staff, doing real trend analysis — on a cadence fast enough that a five-day clock that should have started already has. Whether a specific event triggers 803.50 or 803.53 for your own device is a determination for your own regulatory and quality team, made against your own facts; this is a description of how the two clocks and their awareness standards are defined, per FDA Radar’s editorial standards, regulatory intelligence and method, never regulatory advice about any specific event’s reportability.