FDA Inspector Questions: What Inspectors Actually Ask in Food Distribution Audits

The specific questions inspectors ask during FDA and customer audits of food distribution operations — the records they expect, the format they expect them in, and what "audit-ready" actually means in practice.

If you found this article, you're probably preparing for an inspection

This is the most useful article on this site if you're staring down an FDA inspection — yours, or one that might come soon. It's a list of the specific questions inspectors actually ask, organized by the operational areas they walk through.

Two companion pieces also worth reading:

• FDA inspection checklist for food distribution operations — practical readiness checklist organized by time-to-inspection
• Common Form 483 findings — the recurring observations on published 483s, and what they reveal about systemic gaps

The gap between audit prep and audit reality

Most distribution operations have an audit prep checklist somewhere. The food safety plan binder is up to date. SOPs have been reviewed. The pest control folder has the recent reports filed. The quality team feels prepared.

Then the inspector arrives, asks for "the corrective action documentation for the temperature excursion on March 14th," and the next 90 minutes are spent searching through email, file cabinets, sensor exports, and the maintenance manager's notebook to piece together a record that should have been one place.

The records exist. They're just scattered. And the inspector's job — implicitly — is to make you produce them in the format and time frame that demonstrates your controls are actually functional, not just documented.

This article is the list of questions inspectors actually ask, the records they expect, and the rough time window in which they expect to receive them. Treat it as a stress test for your current systems.

The pattern: specific, dated, end-to-end

Inspector questions tend to share three characteristics:

• Specific: They ask about a particular event, asset, or person — not a general topic
• Dated: They ask for records covering a specific time range — usually the past 6 or 12 months
• End-to-end: They follow a thread from beginning to closure — not just one record

A question like "show me your pest control program" doesn't really get asked. A question like "show me the inspection records, findings, and corrective actions for pest control from January through April" does.

Common question patterns and the records they require

Environmental compliance

"Show me documented response to the temperature excursion on [specific date]."

What the inspector expects to see:

• Sensor data confirming the excursion (extent, duration, peak value)
• Acknowledgment record (who acknowledged, when)
• Investigation findings — what caused the excursion
• Product impact assessment — was anything affected, and what did you do about it
• Corrective action — what changed to prevent recurrence
• Effectiveness verification — did the corrective action work

Expected timeframe to produce: minutes, not hours.

Pest control

"Show me the pest control inspection records, findings, and corrective actions for the past 12 months."

What the inspector expects to see:

• Inspection records for every scheduled visit (no gaps)
• Findings from each inspection — including "no activity" findings
• Corrective actions for any findings, with completion verification
• Trend data — are you seeing the same issues recurring
• The contractor's certification and qualification records

Critical detail: the inspector wants to see continuous records. A four-month gap in inspections is a finding, even if every inspection that did happen was thorough.

Maintenance and equipment

"Show me the maintenance history on [specific cooler / freezer / asset] from the past six months."

What the inspector expects to see:

• Complete work order history for the asset
• PM completion records (with checklist results, not just "completed")
• Linked environmental data showing performance
• Any failures and how they were addressed
• Linkage to any related quality events

The linkage matters. If the inspector sees a cooler had a temperature excursion and a maintenance event around the same time — but they're in separate systems with no obvious connection — the question shifts to "how do you know these aren't related?"

Training compliance

"Show me proof that [specific employee] was trained on [specific procedure]."

What the inspector expects to see:

• The specific training record with date and signature
• The version of the SOP the employee was trained on
• Any required refresher or recertification cadence
• Records of recent completions

Variants of this question target specific risks: "Show me allergen training for everyone in receiving." "Show me lockout/tagout training for everyone authorized to perform maintenance." The records have to be retrievable by person, by procedure, and by date.

SOP version control

"Show me which version of [specific SOP] is currently in effect, and which employees have acknowledged the current version."

What the inspector expects to see:

• The current approved version with effective date
• Version history showing what changed and when
• The approval chain (who approved, when)
• Acknowledgment records for relevant employees
• Documented training on changes if the revision was significant

Common failure mode: the SOP in the binder isn't the current version. The current version is in someone's email. Acknowledgments of the new version are inconsistent. Inspectors find this routinely.

Supplier quality

"Show me the qualification records for [specific supplier] and the most recent inspection findings."

What the inspector expects to see:

• The supplier's approval history
• Most recent qualification or re-qualification
• Receiving inspection records for the past 6-12 months
• Any non-conformances tied to this supplier
• Corrective action requests issued and supplier responses
• Most recent COA or certificate of analysis if applicable

Non-conformance and CAPA

"Show me the corrective action taken following the [specific finding from a previous audit / specific event]."

What the inspector expects to see:

• The original non-conformance record
• Root cause analysis (5-Why or equivalent)
• Corrective action plan with owner and due date
• Completion verification — what was actually done
• Effectiveness verification — did it work
• Approval and closure records

This is one of the most common follow-up questions in repeat audits. Inspectors revisit previous findings to verify the corrective actions actually solved the underlying issue, not just the symptom.

Recall readiness

"Walk me through how you would execute a recall on lot [specific lot]."

What the inspector expects to see:

• The current recall procedure
• Lot trace records showing where the product came from and where it went
• Customer contact records
• Evidence of recent recall drills or tabletop exercises
• Documentation showing the team knows their roles

The time dimension

Inspectors don't just want the records — they want them in a time frame that demonstrates your system actually works.

A useful rule of thumb:

• Single specific record: seconds to a minute
• Time-range query (e.g., 12 months of inspections): 1-3 minutes
• End-to-end thread (event → investigation → corrective action → closure): 3-5 minutes
• Cross-functional query (e.g., training + procedure + maintenance): 5-10 minutes

When a record takes 30 minutes to produce, the inspector is forming a different opinion about your operation than when it takes 30 seconds. The actual record might be the same. The retrieval time is itself part of what's being audited.

What "audit-ready" actually means in practice

Audit-ready means three specific things:

1. Records are in one place

Not "in one place after I export from three systems." Actually in one system with consistent retrieval. The inspector should not be watching you wait for an export from a sensor platform while you also pull a PDF from email and a spreadsheet from a shared drive.

2. Records are searchable by the dimensions auditors use

By date range. By asset. By person. By procedure. By non-conformance number. By supplier. A system that can't filter by these dimensions forces you to manually assemble what the inspector asked for, which is slow and error-prone.

3. Records connect to each other

Temperature excursion connects to the maintenance event that caused it connects to the corrective action that resolved it connects to the SOP that was updated as a result. When the inspector follows the thread, the connections are visible — not reconstructed verbally.

Where systems typically fall short

The most common audit-prep failure modes — by far — come from records being in the wrong system or in no system:

• Contractor records in email or paper. The pest control company's records are in their software, not yours.
• Sensor data in a separate platform from the maintenance system. The excursion and the work order are two records, not one event.
• Training in spreadsheets. Often outdated, often incomplete, often missing seasonal hires entirely.
• SOP versions inconsistent across locations. The current version exists, but isn't where the inspector looks.
• Non-conformances tracked outside the main system. Often in separate trackers or spreadsheets that nobody updates after an event closes.

Every one of these comes back to the same root cause: the records exist, but the system architecture doesn't put them where audit retrieval naturally happens.

The honest framing

Audit readiness isn't a feature you add. It's a property that emerges from how your operational systems are structured. If your maintenance, environmental, training, and contractor records all live in one integrated system with consistent retrieval, you're audit-ready by default. If they don't, no amount of binder-prep solves the underlying problem — you're just deferring the gap to the next audit.

The strongest indicator that an operation is genuinely audit-ready: the quality director can demonstrate the answer to any of the questions in this article in front of you, on a live system, in under 5 minutes. If you can't do that today, your next audit is going to be harder than it should be.

Explore QMS Pro FDA inspection checklist