New Introducing QMS Pro — quality & maintenance management for distribution centers. Try the live demo →

FDA Inspection Checklist: How to Prepare a Food Distribution Center

A practical, distribution-focused checklist for the weeks before an FDA inspection — what to have ready, where the gaps usually are, and how to avoid the most common findings.

How this checklist is organized

FDA inspections of food warehouses, distribution centers, and 3PLs follow predictable patterns. Inspectors don't ask random questions — they work through specific areas of the operation, looking for specific evidence. This checklist mirrors that pattern.

It's organized into three time horizons:

  • Stage 1 (1-4 weeks out): Foundational documentation and program health
  • Stage 2 (the week of): Practical readiness and operational tightening
  • Stage 3 (the day of): Inspection-day execution

Each item references where the records actually need to be retrievable from — because the most common audit failure isn't missing records, it's records the team can't produce quickly when asked.

Stage 1 — Foundational readiness (1-4 weeks out)

Food safety plan

  • Current written food safety plan exists, dated, signed by the qualified individual
  • Hazard analysis is documented and reasonably current (typically reviewed annually)
  • Preventive controls are identified for each hazard
  • Monitoring procedures are specified for each control
  • Corrective action procedures are documented
  • Verification activities (review of records, calibration, etc.) are specified
  • Recall plan is included and tested at least annually

Sanitation program

  • Master sanitation schedule exists and is current
  • Sanitation completion records exist for the past 12 months
  • Verification activities (visual inspection, ATP swabs, environmental monitoring) are documented
  • Failed sanitation checks have corrective action documented
  • Sanitation chemicals are inventoried with SDS sheets accessible

Pest control records

  • Complete inspection records for the past 12 months — no gaps
  • Findings documented for each inspection (including "no activity")
  • Corrective action records for any findings, with verification of completion
  • Pest control contractor qualification documents on file
  • Trend data showing whether issues are recurring

Pest control is one of the most consistently scrutinized areas in food warehouse inspections. Most facilities outsource it, which means the records often live with the contractor. See Working with Outside Contractors for how to close this gap.

Environmental monitoring

  • Continuous temperature/humidity monitoring in storage areas
  • Mean kinetic temperature calculations where applicable (see MKT explained)
  • Sensor calibration records for the past 12 months
  • All excursion events documented with response
  • Excursion response includes: acknowledgment, investigation, product impact, corrective action, verification

Training records

  • Initial food safety training documented for all employees who handle food
  • Annual refresher training records
  • SOP-specific training records for procedures requiring sign-off
  • Allergen training documented for relevant employees
  • Seasonal hires and contractors covered (not just permanent employees)
  • Training records retrievable by employee, by procedure, and by date

Maintenance and equipment

  • Preventive maintenance schedules current and being executed (see PM schedules that get done)
  • Work order history available for past 12 months
  • Equipment failure events documented with root cause and corrective action
  • Maintenance manuals/procedures version-controlled

Supplier records

  • Approved supplier list current and signed
  • Supplier qualification records for the past 12 months
  • Receiving inspection records
  • COAs (certificates of analysis) tied to specific lots where applicable
  • Foreign supplier verification records if you import food (FSVP)

Non-conformance and corrective actions

  • All non-conformances from past 12 months documented
  • Root cause analysis completed for significant events
  • Corrective and preventive actions tracked to completion
  • Effectiveness verification for closed CAPAs
  • Previous audit findings show evidence of resolution

Stage 2 — Practical readiness (the week of)

Walk the facility

  • Walk the facility as if you were the inspector — look at what they'll see
  • Visible cleanliness: floors, walls, ceilings, drains
  • Pest evidence: rodent stations, insect light traps, exterior bait stations
  • Equipment condition: cleanable, not rusted, gaskets intact
  • Storage practices: spacing from walls, off the floor, no products against the ceiling
  • Temperature recording devices visible and functioning
  • Allergen segregation maintained where required
  • Signage current: handwashing reminders, GMP requirements, allergen warnings

Employee readiness

  • Brief the team on what to expect — calm and professional, not anxious
  • Reinforce: answer questions directly, don't volunteer information beyond what's asked
  • Designate who escorts the inspector and who handles record requests
  • Designate a single point of contact for the inspector
  • Have a backup if the primary contact is unavailable

Documentation access

  • Verify all records mentioned in Stage 1 can actually be retrieved quickly
  • Test specific lookups: "show me the corrective action for [random NC from 6 months ago]"
  • Test by-date queries: "show me pest control inspections from January through March"
  • Test by-person queries: "show me allergen training for [specific employee]"
  • If anything takes more than 5 minutes to retrieve, fix it before the inspector arrives

Internal mock inspection

  • Have someone with audit experience walk through as if they were the inspector
  • Use the question patterns in What Inspectors Actually Ask
  • Document the gaps found and address them before the actual inspection

Stage 3 — Inspection day

When the inspector arrives

  • Request their FDA credentials and a Form FDA 482 (Notice of Inspection)
  • Verify their identity matches the credentials
  • Brief them on facility safety requirements (PPE, restricted areas)
  • Have your designated escort with them at all times
  • Provide a workspace with internet access for their records review

During the inspection

  • Answer questions factually and directly
  • If you don't know an answer, say so and find out
  • Take detailed notes of every observation and request
  • If photos or samples are taken, request copies/duplicates
  • Document everything they look at and everything they ask for
  • Don't argue findings in real-time — note them and address in your response

At the close-out meeting

  • Listen to the inspector's findings without interrupting
  • Ask clarifying questions if needed
  • If Form 483 observations are issued, accept the form and note the response window
  • Confirm your contact information for any follow-up
  • Don't commit to specific corrective actions on the spot — those require formal response

The hidden checklist: what your software needs to support

Almost every item above ultimately comes down to one capability: can you find any specific record in seconds, by any relevant dimension?

If your records live in five systems — sensor platform for temperature, CMMS for maintenance, document system for SOPs, spreadsheet for training, email for contractor work — assembling the answer to a single inspector question takes 30 minutes. Times 50 questions per inspection, that's a multi-day exercise.

Records that live in one integrated system, organized around the dimensions inspectors actually query (date, asset, person, procedure, NC number), make this difference vanish. Each question becomes a 30-second filter and export.

The 12 most common findings to head off

Across published FDA Form 483s for food warehouses and distribution operations, certain findings recur with high frequency. See our companion article on common Form 483 findings in food distribution for the detailed breakdown. The high-level pattern:

  1. Inadequate or outdated hazard analysis
  2. Preventive controls not implemented or not monitored
  3. Sanitation program gaps or undocumented completion
  4. Pest control documentation incomplete or missing
  5. Temperature monitoring records with gaps or unaddressed excursions
  6. Training records missing for employees who handle food
  7. SOP version control failures (employees following old procedures)
  8. Supplier qualification records incomplete
  9. Corrective actions not completed or not verified
  10. Previous audit findings not adequately addressed
  11. Allergen segregation procedures not followed
  12. Recall procedures not tested or documented

If you're reading this because you have an inspection coming up

The honest answer: if you're discovering this checklist for the first time the week before an FDA inspection, you're behind. The work of FSMA compliance is daily, not pre-audit. The right time to think about retrievability is when you're building the system, not when the inspector is walking up the drive.

That said — even an inspection in two weeks is enough time to materially improve your readiness if you focus on the highest-risk areas: pest control records, temperature excursion responses, training compliance for the workforce, and SOP version control. These four areas account for a disproportionate share of Form 483 findings.

And for the next inspection, consider the structural fix: an integrated quality and maintenance system where records flow into one audit-ready place automatically, instead of being assembled from five sources in the days before an inspection.

See what audit-ready records actually look like.

The QMS Pro live demo is loaded with a fictional food & beverage 3PL. Try answering any of the inspector-question patterns yourself — temperature excursion response, pest control inspection records, training compliance, maintenance history. The retrieval times described in this article are achievable, but only with the right system design.

Explore QMS Pro What inspectors actually ask

Be audit-ready every day, not just inspection week The demo shows what integrated records look like.

Try the demo