People joke that PSMF also stands for "potential source of major findings," and there's a reason the joke sticks. It's usually the first document an inspector opens, and it's a direct reflection of your whole pharmacovigilance system. If it's not top notch, that's the impression the rest of the inspection starts from.
Tomislav Marković, Senior Pharmacovigilance Manager, sits down with Beáta Bačová, our Head of Project Management, to talk about what keeps a Pharmacovigilance System Master File (PSMF) inspection-ready, and what quietly lets it slip.
The first point is simple but easy to ignore: a PSMF isn't something you write once and file away. It needs a defined update periodicity, and quarterly has become the informal industry standard. Getting there takes more than SOPs. Tomislav points to something less obvious: a culture of ownership. The data comes from regulatory, marketing, medical, and other departments, since no PV professional can track everything happening across a company alone.
That's exactly where things go wrong. People get pulled into daily tasks, the PSMF gets deprioritized, and then an inspection announcement lands and everyone is rushing to collect contributions at once. Tomislav and Beáta frame this as a project management problem as much as a PV one, which is why iVigee runs it with a dedicated PSMF administrator rather than folding it into a project manager's other work.
Tomislav is currently managing roughly 30 PSMFs. Managing 15 PSMFs or 30 doesn't have to mean 15 or 30 times the work. With a modular, global approach, only the territory-specific pieces change.
Got a pharmacovigilance question of your own? Put it to an expert


Hvezdova 1716/2b, 140 00 Prague 4, Czech Republic
1500 District Avenue, Burlington, MA, United States