Most pharmacovigilance teams know when an inspection is likely. Far fewer can say how long it would take to answer an inspector’s first ten questions, starting right now.
That gap is the difference between being inspection-ready and preparing for an inspection. Preparation is a project: weeks of pulling records, reconciling trackers, and rebuilding timelines from email. Readiness means the answers already exist, because the work was tracked as it happened.
Here’s what inspectors typically want to see, where teams usually get stuck, and what it takes to close the gap for good.
What an inspector is really asking
A pharmacovigilance inspection looks at whether your safety system works as described and whether you can prove it. Whether the inspection comes from the European Medicines Agency (EMA), the U.S. Food and Drug Administration (FDA), or another regulator, the questions tend to come back to a few themes:
- Commitments: What did you commit to in your Risk Management Plans and Risk Evaluation and Mitigation Strategies, and where does each commitment stand today?
- Decisions: When a safety signal was identified, who reviewed it, what was decided, and when?
- Deadlines: Were aggregate safety reports and other required submissions delivered on time? If not, why not, and what was done about it?
- Responsibilities: Who owns each part of the process, including partners and local affiliates covered by safety data exchange agreements?
- Evidence: Can you show all of this from records created at the time, not reconstructed afterward?
None of these are trick questions. They’re hard to answer quickly when the information is spread across spreadsheets, shared drives, inboxes, and the memory of whoever was on the team at the time.
Where the scramble comes from
Commitments live in too many places
Global Risk Management Plan commitments might sit in one tracker, local implementation of additional risk minimization measures in another, and REMS obligations in a third. Each one may be accurate on its own. The problem shows up when an inspector asks for the full picture for a single product, and someone has to pull it together by hand.
Status depends on the last update, not the current state
A spreadsheet only knows what someone last typed into it. If a commitment changed hands, slipped, or was completed two weeks ago and nobody updated the row, the tracker is wrong, and nobody finds out until it matters.
Decisions aren’t captured where the work happens
Signal review meetings produce decisions. Too often those decisions are recorded in meeting notes, follow-up emails, or not at all. Months later, “why did we close this signal?” becomes a search through calendars and inboxes for whoever was in the room.
History gets rebuilt instead of retrieved
This is the expensive part. When the audit trail isn’t created as a byproduct of the work, it has to be rebuilt before the inspection. That takes people away from actual safety work, and a rebuilt history is always weaker evidence than one recorded at the time.
What “ready on day one” looks like
Inspection readiness isn’t a binder or a mock-inspection checklist, though both have their place. It’s a set of capabilities your team either has every day or doesn’t. A practical test is whether you can do the following within an hour, without asking anyone to go look:
- Produce the current status of every Risk Management Plan and REMS commitment for a given product, including owner, due date, and what’s overdue.
- Show the complete trail for any safety signal, from identification through review, decision, and follow-up actions, with dates and names.
- List every aggregate report due in the past 12 months and show whether each was submitted on time.
- Identify which partners and affiliates hold responsibilities under each safety data exchange agreement, and confirm they’re working from the current version.
- Show who changed what, and when, for any record an inspector picks at random.
If any of those would take days instead of minutes, that’s where to focus first.
Building readiness into the process
Teams that hold up well in inspections usually don’t prepare harder. They structure the work so the evidence builds up on its own. A few principles help:
One place for commitments, not one place per commitment type. Risk management, signals, agreements, and reporting deadlines don’t need to live in the same system of record. But they do need a single view where status and ownership are visible together.
Ownership on every item. A commitment without a named owner is the one that slips. Ownership should be visible to anyone with a legitimate need, not held in someone’s head.
Reminders before deadlines, not reports after them. An overdue report tells you something already went wrong. A reminder ahead of the deadline gives you time to prevent it.
Audit trail as a byproduct. If recording an action is a separate step from doing it, it will eventually get skipped. The record should be created by the work itself.
Cross-functional handoffs that are tracked, not assumed. Most gaps open where work moves between safety, regulatory, quality, and affiliates. Each handoff should leave a timestamp and an owner.
Where Orbit fits
Orbit is a pharmacovigilance process tracking platform built around that idea. It gives safety, risk management, and regulatory teams one view of Risk Management Plan and REMS commitments, signal and surveillance workflows, safety data exchange agreements, and aggregate report deadlines. It sends reminders ahead of due dates and keeps a traceable record of who did what, and when, as the work happens.
It isn’t meant to replace your safety database, document management system, or any other part of your safety system. Orbit works alongside your entire safety system ecosystem, adding the workflow and activity-tracking layer around it, so the questions an inspector asks can be answered from the records you already have instead of rebuilt from scratch.
Start with the one-hour test
Pick one product and run the five checks above with your team this month. Wherever an answer takes more than an hour, that’s where your inspection risk is concentrated, and where better tracking will pay off first.
You’re passionate about patient safety, not spreadsheets, and not spending the weeks before an inspection rebuilding a history that should already exist.
