Introduction
Ask most people outside the field what regulatory affairs looks like, and they will describe a submission writer working toward an approval. Far fewer picture the person on the other side of that approval: the specialist who keeps watching the product once it is on the market, deciding which complaints and adverse events have to be reported to regulators, and on what clock. That is the postmarket surveillance and vigilance specialist, and in medical devices it is one of the busiest, most judgment-heavy jobs in the regulatory function.
The role sits at the intersection of quality, clinical safety, and regulatory reporting. It rarely gets the visibility of a first-time approval, but it carries real consequences: get a reportability decision wrong, or miss a filing deadline, and the company is exposed to warning letters, recalls handled badly, or worse, a real patient harm that goes unaddressed. Understanding what this job actually involves day to day is useful both for people considering it as a next step and for anyone in adjacent roles who works with vigilance teams.
Where the Role Sits in the Organization
Postmarket surveillance and vigilance work is organized differently from company to company. In some organizations it lives inside quality, as an extension of the complaint-handling function under the quality management system. In others it sits inside regulatory affairs, closer to the people who manage relationships with FDA and other competent authorities. In larger device companies, it is often its own department — sometimes called Vigilance, sometimes Postmarket Safety, sometimes Complaint Management and Reporting — with dotted-line relationships into both quality and regulatory.
Wherever it sits organizationally, the job touches nearly every other function: clinical and safety teams for medical judgment on adverse events, quality for the underlying complaint investigation and CAPA process, manufacturing for root cause on device-related failures, and regulatory affairs proper for how a reportable event might affect an existing clearance or approval. A postmarket surveillance specialist who cannot work across those groups will struggle, no matter how strong their technical knowledge of the reporting rules is.
The Core Daily Work: Triage and Reportability
The heart of the job is deciding, event by event, whether a complaint meets the threshold for regulatory reporting. In the United States, that threshold is set by the Medical Device Reporting regulation (21 CFR Part 803), which requires manufacturers to report events involving death, serious injury, or malfunctions that could cause death or serious injury if they recurred. In the European Union, the vigilance system under the MDR (Articles 87 through 90) covers serious incidents and field safety corrective actions, reported to competent authorities and increasingly through EUDAMED as that system matures.
In practice, a specialist works through an intake queue of complaints that quality has logged, reviewing the clinical narrative, any device return and investigation findings, and prior similar events, then applying the regulatory definitions to decide: reportable or not, and if reportable, under what timeline. Some events are unambiguous. A large share are not — a malfunction with no injury today that plausibly could cause harm on a repeat occurrence requires a documented judgment call, not a lookup-table answer. Specialists build institutional muscle for this over time, and experienced reviewers develop a defensible, consistent rationale they can explain to an auditor or an inspector years later.
Once an event is determined reportable, the clock starts. US MDR reports are generally due within 30 calendar days of becoming aware of a reportable event, with a 5-day expedited timeline for events requiring remedial action to prevent unreasonable risk to public health. EU vigilance timelines are similarly tiered by severity, with serious public health threats reported within 2 days, deaths or serious deterioration in health within 10 days, and other serious incidents within 15 days. Missing these deadlines is one of the more common findings in FDA and notified body inspections, which is why much of the day-to-day rhythm of the job is built around tracking dates, not just making the reportability call itself.
Trending, Signal Detection, and CAPA Feed
Individual event reporting is only half the job. The other half is aggregate: watching complaint volume and event types over time to spot signals that a single case would never reveal. A postmarket surveillance specialist maintains or contributes to trending reports that quality and regulatory leadership review on a recurring cadence, looking for rate increases against a baseline, new failure modes, or geographic or lot-specific clusters.
When trending surfaces a signal, the specialist is usually the one who has to translate it into action: opening or feeding a CAPA, recommending whether a field safety corrective action or recall is warranted, and if so, drafting the field safety notice and coordinating its content with regulatory, legal, and communications. This is where the job stops being paperwork and becomes genuinely consequential — a well-run trending process catches problems while they are still a handful of complaints; a weak one lets them grow into a recall covered by trade press.
Writing and Submitting the Reports Themselves
Beyond deciding what to report, the specialist typically drafts the reports: MedWatch 3500A forms for the FDA, manufacturer incident reports for EU competent authorities, and equivalent filings for other markets a device is registered in — Health Canada, TGA in Australia, and others, each with its own form and timeline. Writing these well is a specific skill: a clear, factually precise clinical narrative that neither overstates causality the investigation has not established nor understates a plausible device contribution. Regulators read these reports at scale, and vague or evasive narratives draw follow-up questions that cost the company time.
Multi-market products add real complexity here. A single complaint can trigger separate reporting obligations in the US, EU, and several other jurisdictions simultaneously, each with different timelines, different required content, and sometimes different reportability thresholds for the same underlying event. Keeping a matrix of which markets a device is registered in, and what each requires, is unglamorous but essential groundwork for the role.
How This Differs From the Drug Side
Pharmaceutical companies have an analogous postmarket safety function, usually housed in pharmacovigilance rather than regulatory affairs, reporting adverse events under FDA's postmarketing safety reporting requirements and equivalent EU pharmacovigilance rules. The underlying logic — triage, reportability, aggregate signal detection — is similar, but the regulatory frameworks, forms, and organizational placement differ enough that the two disciplines are usually staffed and trained separately. Professionals considering a move between device vigilance and drug pharmacovigilance should expect a real learning curve on the specific regulations, even though the analytical mindset transfers well.
Skills That Actually Matter
Technical knowledge of the reporting regulations is necessary but not sufficient. The specialists who do this job well share a few traits: comfort making documented judgment calls under incomplete information, since complaint files are rarely as clean as a textbook example; disciplined project management, because a missed deadline is a compliance finding regardless of how sound the underlying analysis was; clear writing under time pressure; and enough clinical or engineering literacy to read an investigation report and understand what it is actually saying about the device and the patient.
Cross-functional credibility matters as much as any of that. A vigilance specialist frequently has to push back on a business unit that does not want an event classified as reportable, or ask a quality engineer to redo an incomplete investigation before a filing deadline. Doing that effectively without becoming the department everyone avoids is a real skill, and it is one interviewers for these roles often probe for directly.
A Realistic Day in the Life
A typical day starts with the intake queue: new complaints logged by customer service or field service overnight, each needing an initial read to flag anything that looks time-sensitive. From there, most specialists spend a meaningful chunk of the morning on active investigations — following up with a quality engineer on a device return that has not yet come back from analysis, or pushing a field service report that is missing details needed to make a reportability call. Early afternoon is often where the writing happens: drafting or finalizing MDR or vigilance report narratives against that day's or week's filing deadlines, since these do not wait for a quieter moment.
Later in the day tends to bring the cross-functional work — a trending review meeting with quality leadership, a call with a business unit that disagrees with a reportability determination and wants to understand the reasoning, or coordination with regulatory affairs on how an emerging signal might affect labeling or a pending submission in another market. The mix of solitary analytical work and real-time cross-functional negotiation is part of what makes the role demanding, and part of what makes it interesting to the people who stay in it.
Common Misconceptions About the Job
Outsiders often assume this is primarily clerical — logging complaints and filling in forms. In reality, the reportability judgment calls are the hard, valuable part of the job, and they carry real professional accountability; an inspector reviewing a company's MDR history will ask a specialist to defend specific non-reporting decisions made months or years earlier. Another common misconception is that the role is purely reactive. Strong postmarket surveillance functions spend real energy on proactive trending and early signal detection, not just processing what arrives, because catching a problem at three complaints instead of thirty is where the function earns its keep. Finally, people sometimes assume the work is the same across device types; in practice, an implantable cardiac device program and a low-risk diagnostic accessory program can have very different complaint volumes, risk profiles, and reporting histories, and specialists often develop deep familiarity with the specific product risk profile they support.
Where the Role Leads
Postmarket surveillance and vigilance is not a dead end — it is a well-worn path into broader regulatory and quality leadership. Specialists who spend a few years building reportability judgment and cross-functional relationships often move into complaint management or vigilance team lead roles, then into regulatory affairs management more broadly, or into quality systems leadership. The exposure to real device performance data across a portfolio, rather than a single submission, gives people in this track a market-facing perspective on product risk that translates well into strategic regulatory roles later.
Conclusion
The postmarket surveillance and vigilance specialist role is less visible than the regulatory jobs built around getting a product approved, but it is where a company's regulatory obligations actually get tested against real-world product performance, day after day, complaint by complaint. For anyone who likes analytical judgment work with genuine stakes, cross-functional problem solving, and a direct line to patient safety outcomes, it is worth a serious look — and for anyone hiring or working alongside this function, understanding what the job actually demands makes for a much better working relationship with the people doing it.