What FDA Investigators Are Actually Looking For — And How to Be Ready Before They Knock
- azania85
- Mar 13
- 7 min read
There’s a misconception that quietly persists in quality circles: that an FDA inspection is fundamentally adversarial. That the investigator walking through your door is there to catch you, expose you, shut you down.
That’s not quite right — and misunderstanding the dynamic can actually make you less prepared.
FDA investigators are trained professionals executing a systematic process. Their job is to verify that what you say you do is what you actually do. The gap between those two things — between your documented system and your lived reality — is where findings are born. Understanding that distinction changes everything about how you approach inspection readiness.
After preparing for dozens of regulatory inspections across FDA- and EPA-regulated environments, I’ve seen companies with sophisticated quality systems stumble and lean operations sail through. The difference almost never came down to resources or complexity. It came down to four things that are entirely within your control.
Your Inspection Didn’t Start Last Week
When a Form 483 gets issued, teams often do a post-mortem searching for what went wrong in the days leading up to the inspection. They review what was said, what was shown, how the investigators responded. But the real answer is almost never found in that window.
Your inspection starts the moment you write a record.
Every batch record, every deviation report, every CAPA, every equipment log — these are not administrative artifacts. They are a running account of your quality culture, written in real time, that will be read by someone who wasn’t there and doesn’t have your context.
Think about what that means practically. The deviation you documented at 11pm on a Friday after a long week. The corrective action you wrote when you were already behind on three other things. The training record that technically got signed but didn’t capture what actually happened in the room. Each of those documents becomes a data point. Enough data points form a pattern. Patterns tell a story — and in an inspection, you don’t get to narrate that story. The investigator does.
The practical shift this demands is deceptively simple: write for a future reader who has no institutional knowledge, no goodwill toward your team, and no ability to ask follow-up questions. If a record only makes sense to the person who wrote it, it’s not a compliant record. If a procedure references a step that your team “just knows,” that’s a gap waiting to be surfaced.
Building this habit doesn’t require overhauling your documentation system. It requires building documentation discipline into daily work — not as an extra burden, but as a standard of craft. Train your team to ask: Would someone who has never worked here understand exactly what happened and why? If the answer is no, the document isn’t finished.
Consistency Is the Asset. Perfection Is the Distraction.
Here’s a scenario I’ve seen play out more than once. A company invests heavily in building a sophisticated QMS — tiered risk classification, multi-level review, robust CAPA methodology with quantitative effectiveness checks. On paper, it’s impressive. In the inspection room, it becomes a liability.
Why? Because they were following it 70% of the time.
An investigator reviewing records doesn’t see your intentions. They see what you did. A 30% deviation rate from your own procedures isn’t a minor compliance gap — it’s evidence that your system doesn’t reflect your operations, or that your operations don’t respect your system. Either way, it raises questions about the reliability of everything you’ve submitted.
Compare that to a team running a simpler system — fewer procedure tiers, more streamlined review, less elaborate CAPA infrastructure — but executing it with near-perfect consistency. That team has something the sophisticated-but-inconsistent team doesn’t: a defensible quality record.
The goal of inspection readiness is not to have the most impressive QMS on paper. The goal is to have a system that is accurate, executable, and actually being executed.
This has real implications for QMS design decisions. Before adding a new layer of controls, ask whether your team can sustain it. Before revising a procedure to be more rigorous, ask whether the more rigorous version will actually be followed. A procedure that gets bypassed because it’s too cumbersome doesn’t make your product safer — it makes your compliance record messier.
The discipline of simplicity in QMS design is undervalued. The most inspection-ready organizations I’ve worked with tend to have quality systems that are appropriately lean, well-understood by the people using them, and followed with a consistency that shows up in the records.
Your Team Is the Inspection
Quality leadership often treats inspection prep as their domain. They review records, coach responses, brief management. All of that matters. But here’s the reality that catches organizations off guard: investigators don’t just talk to quality leadership.
They walk the floor. They talk to operators. They ask the person running the centrifuge why a particular step happens in a particular order. They ask the lab technician what they do when a result looks anomalous. They watch.
What they’re assessing isn’t just whether the answer is right. It’s whether the person giving the answer understands the answer — whether the procedure is something they follow because it makes sense, or something they follow because they’re supposed to and they’re not sure why.
That distinction matters because it reveals something about your quality culture that no document can fake.
If your operators know that a particular environmental monitoring step exists because contamination at that point in the process has a direct pathway to the product, they’ll explain it differently than if they know it exists because “QA requires it.” The first answer demonstrates process understanding. The second raises a question: if QA didn’t require it, would it happen?
Building a team that can represent your quality culture well in an inspection requires investment long before the inspection happens. It means training that goes beyond procedure recitation to include rationale. It means line-level supervision that reinforces the why alongside the how. It means a quality culture where operators feel empowered to flag concerns rather than paper over them — because a team that surfaces its own problems is far more inspection-ready than one that doesn’t know its problems exist.
This is also why the relationship between quality and operations matters so much. When quality is seen as the compliance police, operators learn to give compliant-sounding answers rather than accurate ones. When quality is seen as a partner in building systems that actually work, the whole organization speaks the same language — and that language holds up under scrutiny.
Have the Hard Conversations Before the Investigator Does
Every organization has its unfinished business. The deviation that got documented but never fully investigated because the root cause was inconvenient. The validation that keeps getting pushed to next quarter because there’s always something more urgent. The change control that was implemented in practice before the paperwork caught up. The CAPA that technically got closed but whose effectiveness was never really checked.
These items have something in common: they require a hard conversation. They require someone to say, out loud, that something didn’t happen the way it should have. And that conversation is uncomfortable, so it gets deferred.
FDA investigators are trained to find deferred discomfort. They look at CAPA closure patterns. They cross-reference deviation trending with process change history. They notice when validation documentation is conspicuously absent for processes that have been running for years. They ask questions that require you to explain the gap.
The finding doesn’t come from the gap itself — it comes from the fact that your internal system didn’t catch it, escalate it, and address it. The finding is a signal that your quality system isn’t doing what it’s supposed to do.
The alternative is simple in principle and genuinely hard in practice: close your own gaps first. Not the week before an inspection — continuously, as a function of your internal audit program and management review. Make the uncomfortable conversation a routine one, not a crisis.
A robust internal audit program, conducted with the same rigor an investigator would bring, is one of the highest-return investments in inspection readiness. Not because it catches every finding before the FDA does, but because it builds organizational muscle for honest self-assessment. Organizations that audit themselves well tend to know where their weak points are. That knowledge, paradoxically, puts them in a much stronger position during an inspection.
Inspection Readiness Is Not an Event
The framing of “inspection prep” as a defined activity — something you do before an inspection — is one of the most persistent and damaging mental models in quality management.
Preparation implies a beginning and an end. It implies that there is a state of readiness you can achieve and then return from. But inspection readiness isn’t a destination. It’s a baseline.
Organizations that do best in inspections are not the ones who prepared hardest in the weeks beforehand. They’re the ones for whom an inspection is essentially an audit of normal operations — where the records look the way they always look, where the team responds the way they always respond, where the procedures in use are the ones posted on the wall.
Building that baseline requires shifting the conversation from “are we ready for an inspection?” to “is the way we’re operating every day something we’d be comfortable showing an investigator?”
That’s a higher bar. It’s also the only one that actually holds.
For quality leaders, this means making inspection-ready behavior the default expectation rather than the inspection-season expectation. It means building audit habits into the calendar year-round, not just when an inspection is on the horizon. It means having the hard conversations about gaps and CAPAs in management review, not scrambling to close them in January because you heard inspections are ramping up.
For operators and line supervisors, it means treating every record as a record — not as paperwork that happens after the real work.
For executives, it means investing in quality culture as a business function, not treating QA headcount as a variable cost to be optimized when the pipeline slows down.
The Quiet Truth About Inspection Success
The organizations I’ve seen come through inspections well — with no findings, or with only minor observations easily addressed — almost always share a common characteristic. They weren’t surprised by anything the investigator found.
Not because they were hiding things. Because they already knew where their system was strong and where it needed work. Because their internal processes had already surfaced the issues that might otherwise become findings. Because their teams could speak to their quality practices with genuine confidence, not rehearsed confidence.
That’s what year-round inspection readiness actually looks like. Not perfect systems. Not elaborate preparation. Just the kind of honest, consistent quality practice that holds up to scrutiny because it was built to.
The FDA investigator who walks through your door isn’t your adversary. But they are your most rigorous outside reviewer. The question is whether you’ve been that rigorous with yourself.
Azania Selden is the founder of Foundry Quality Group, a quality management consultancy specializing in GLP-to-GMP transitions, QMS architecture, inspection readiness, and CMO/vendor quality oversight for biotech, pharma, and ag life sciences companies.
Comments