USFDA INSPECTION STEP-BY-STEP PLAYBOOK

(From Readiness → Confidence → Compliance)

A Simple, Practical Guide for First-Time and Every Time Inspected Facilities

When an FDA investigator visits your facility for the first time (Pre Approval Inspection) or anytime (Routine or Post Surveillance Inspection) , it can feel overwhelming. But with the right preparation and a calm, organized approach, you can handle the inspection professionally and confidently.

This playbook walks you through everything - from before the investigator arrives to after they leave - in simple, easy-to-follow steps.

8 Steps

Great inspections are won before the inspector walks through the door. Use this checklist to get ready in advance.

Pick specific people for each role and make sure everyone knows their job:

  • • Inspection Host - The main person who talks to the investigator
  • • Document Person - Collects and hands over requested documents
  • • Note-Taker / Scribe - Writes down everything that happens
  • • Subject Experts - One person per department (Lab, Manufacturing, Warehouse, etc.)
  • • Runner - Helps fetch things, arrange rooms, and support the team
📌 Always assign a backup for every role. If one person is absent on inspection day, the backup steps in automatically.

Choose one conference room as your internal 'base.' This is where your team coordinates, not where the investigator sits.

  • • Stock it with blank paper, pens, a printer, and a photocopier
  • • Keep all SOPs, Batch Records, and Quality Files accessible from this room
  • • Have a phone available for quick calls to legal/regulatory support
  • • Use a whiteboard or chart paper to track all document requests in real time

This is the most important preparation you can do. If your documents are messy, missing, or out of date - the inspection will go badly.

  • • Make a master list of all SOPs, Batch Records, Validation Reports, Lab Records, And Quality files.
  • • Ensure all documents are current - no outdated procedures in active use.
  • • Practice retrieving any document within 30 minutes. If you can't do this, fix it now.
  • • Check that all training records are complete and up to date for all employees.
  • • Confirm all deviations, OOS results, and CAPAs are properly documented and closed or actively tracked.

At least once a year - and again before any expected inspection - run a practice (mock) inspection internally or with an external expert.

  • • Walk through your facility as if an investigator is watching
  • • Ask questions the way FDA would ask them
  • • Identify any gaps and fix them before the real inspection
  • • Practice the opening meeting, document requests, and facility tour

Every employee needs to know what to do if the FDA visits. Hold a short briefing session covering:

  • • Always tell the truth - no exceptions
  • • Answer only what is asked - do not add extra information
  • • If unsure of an answer, say 'I will need to verify that' and refer to a supervisor
  • • Be polite and professional at all times
  • • Do not discuss internal problems or management disagreements
  1. The front desk or security must stay calm and polite. Do not panic.
  2. Politely ask the investigator to wait in the reception area.
  3. Immediately call the Inspection Host - do not let the investigator go anywhere unaccompanied.
  4. Do not answer any questions about the facility until the Inspection Host arrives.
  5. Activate the rest of the Inspection Team through your pre-agreed notification system (phone/email/PA).
warning

Never refuse entry to an FDA investigator

Refusal is a violation of federal law and will immediately escalate the situation.

Before the inspection begins, you have the right to verify who the investigator is:

  • Ask to see their official FDA photo identification (FDA ID/Badge).
  • Ask to see the FDA Form 482 (Notice of Inspection) - Note scope and areas of inspection and Do not delay acceptance.
  • Make a photocopy of both - this is standard and the investigator expects it.
  • Write down the investigator's name, badge number, and time of arrival in your inspection log.
  • Inform Site Head, QA Head, Inspection Core Team immediately.
push_pin

The FDA Form 482 tells you what kind of inspection it is and what regulations apply. Read it carefully.

  • meeting_room Quiet Room Provide a quiet, dedicated room for the investigator
  • wifi Basics & Comfort Arrange basic amenities: Wi-Fi connection (if allowed), printer access, and water/coffee.
  • menu_book Inspection Logbook Start an Logbook (time,requests,responses)
  1. Welcome the investigator and introduce your team members by name and role.
  2. Give a short overview of your facility — what you make, how many people work there, and what regulatory approvals you hold (keep under 5 minutes).
  3. Inform the investigator that all document requests must go through your designated Document Person.
  4. Confirm that your escort will accompany them at all times throughout the facility.
  5. Ask the investigator what their expected working hours are and what general areas they plan to review.
  6. Let them know your note-taker will be documenting the inspection on behalf of the facility — this is your right.
  7. 🎤 Opening Interaction Protocol

    Keep it professional and concise.

    Provide: Site overview (brief) , Org chart , Product list / operations summary & Clarify scope, timing, and daily schedule

  8. 🧑🏼‍🤝‍🧑🏼Activate Inspection Team:
    • Assign roles:
      • Front Room (primary spokesperson/SME)
      • Back Room (document retrieval/support)
    • Ensure key SMEs are on standby (QA, Production, QC, Engineering, IT).

Train your entire team to strictly follow these core rules during all interactions:

1

Only answer the question that was asked.

Answer truthfully, clearly, briefly. Nothing more.

2

If you don't know, say 'I will find out and get back to you.'

Never guess.

3

Never lie or mislead the investigator.

No guessing, no speculation, no over-explaining.

4

Stay calm and professional

Even if the investigator is tough or aggressive.

5

Write down everything that happens,

One voice at a time (avoid cross-talk).

6

Ensure documents are Complete, approved, current and Consistent across records.

Track every document shared (copy control)

7

Never promise something you cannot deliver.

Only commit to what you can actually do.

info

The inspection could last one day or several days. Here is how to manage it day by day.

🔗 Remember : Golden Rules
• Stay calm, respectful, and transparent
• Consistency = credibility
• Data Integrity at all times (ALCOA+++)

The investigator will ask for many documents. Here is the right process:

  1. Write down every request in your Document Request Log — date, time, what was asked for, and who is getting it.
  2. Before handing over any document, your Document Person must quickly review it for accuracy and completeness.
  3. Always provide a clean photocopy — keep the original in your facility whenever possible.
  4. If you need more time to retrieve a document, tell the investigator honestly: "We will have that for you by [time]."
  5. If a document does not exist, say clearly: "That record does not exist in our system."
  6. Never remove, hide, or change any document once an inspection has started.
warning

Never give the investigator a document that contains errors or is not the current version without first explaining it. This will look far worse than simply saying you need a moment to review.

The investigator will want to walk through your facility. Here is how to handle it:

  • The Inspection Host leads the tour. A departmental expert walks alongside the investigator in their own area.
  • The note-taker walks behind and documents everything observed and discussed.
  • Before the tour , quickly alert all supervisors that the inspection is in progress in their sector.
  • Ensure strict line clearance, complete labeling, and absolute cleanliness.
  • Operators should be calm, trained, and confident
  • Follow SOPs exactly as written
  • Make sure all areas are tidy, equipment is labeled correctly, and logs are up to date.
  • If the investigator asks to see an area that is not in operation, explain this clearly and offer the relevant documentation instead.
warning

If the investigator notices a problem in an area - do not try to hide it or quickly fix it without telling them. Acknowledge it, document it, and say you will investigate. Trying to hide observations makes things much worse.

The investigator may want to speak directly with your employees. Here is the protocol:

  1. All interview requests go through the Inspection Host first.
  2. Listen fully; do not interrupt.
  3. Clarify respectfully if needed.
  4. Do not argue; document immediately.
  5. Begin internal assessment in back room.
  6. Briefly remind the employee before the interview: answer truthfully, answer only what is asked, say 'I don't know' if unsure.
  7. The Inspection Host or a senior team member should be present as an observer — not to interrupt, just to listen and take notes.
  8. After the interview, debrief with the employee privately to note any concerns.
push_pin

Never tell an employee what specific answers to give. That is obstruction. Just remind them to be truthful and to only answer what they are directly asked.

Keep the command structure synchronized through this daily operational rhythm:

wb_sunny Morning (before investigator arrives)

Quick 20-minute team meeting - review yesterday's events, open document requests, and today's expected activities.

query_stats During the Day

Track all requests in real time. Keep the investigation log updated. Flag any concerning patterns to legal counsel.

nights_stay Evening (after investigator leaves)

Full team debrief - finalize notes, close out document log, identify any potential problem areas for the next day.

  1. Have your full team present — Inspection Host, Document Person, subject matter experts (SMEs), and legal counsel.
  2. Do not argue or get defensive. Listen carefully to every observation. Your scribe must write down every single comment and observation.
  3. After all observations are read, you may politely correct any clear factual errors — only if you have immediate, written proof on hand.
  4. Accept the signed FDA Form 483 and sign to confirm receipt. Signing does NOT mean you admit to any violation or regulation breach.
push_pin

The closing meeting is not the time to fight observations. Your written response - submitted after the inspection - is where you address them properly.

The FDA 483 lists the investigator's observations of conditions that may be violations of regulations. Think of each observation as a problem the investigator saw or noticed.

  • It may include documentation issues, process concerns, equipment maintenance problems, or operator training gaps.
  • Every single observation must be addressed in your final submission — you cannot ignore or bypass any concern.
  • The FDA Form 483 is not a final enforcement action — it is a preliminary list of concerns requiring your written explanation and CAPA commitments.
info

Within 15 business days of receiving the FDA 483, you must send a written response to the FDA. This response is the most important document you will write.
A good response can prevent a Warning Letter. A poor response can invite one.

  • Thank the investigator
  • State commitment to cGMP and data integrity
  • Summarize key systemic improvements
  • Provide contact person for follow-ups
BE TIMELY•BE TRUTHFUL•BE THOROUGH•BE ACTIONABLE
  1. Submit within 15 working days of receipt
  2. Assign a single owner (QA lead) and cross-functional SMEs
  3. Use a tracking sheet for each observation (owner, due dates, status)
  4. Address every single observation - do not skip any.
  5. For each observation, state what happened (factually, without being defensive).
  6. Rephrase clearly to show understanding. Define scope (product(s), batch(es), timeframe)
  7. Explain why it happened - the root cause & Describe what corrective (Creative)action you have taken or will take along with Proactive (Preventive) action you will take in post inspection.
  8. Give a realistic completion date and name the person responsible.
  9. Attach supporting evidence for anything you have already fixed
  • Do not argue with the FDA or say they are wrong — Clear, concise, factual (no fluff), No blame shifting (own the issue) & Avoid vague words: “will ensure,” “as needed,” “ongoing”
  • Use data and specifics (numbers, dates, versions).
  • Do not make vague promises like 'We will improve our system.' Be specific.
  • Do not commit to timelines you cannot meet. If you say 3 months, deliver in 3 months.
  • Do not submit the response late. If you need more time, contact FDA in advance and explain why.
push_pin

Have a regulatory consultant or legal counsel review your response before submitting. One poorly worded sentence can change the outcome significantly.

info

After you submit your response, the FDA will classify your inspection into one of three operational categories.

FDA Classification What it Means What You Should Do
NAI
No Action Indicated 		You passed. FDA found no significant issues. Best possible outcome. Continue maintaining your quality systems. Keep records of the clean inspection.
VAI
Voluntary Action Indicated 		Minor issues were found. FDA is not taking formal action but expects you to fix the issues voluntarily. Submit your corrective action plan. Fix the issues and document everything.
OAI
Official Action Indicated 		Significant problems were found. FDA is likely to issue a Warning Letter. Engage regulatory counsel immediately. Prepare a comprehensive corrective action plan. Respond quickly and thoroughly.

A Warning Letter is a formal notice from FDA that your facility has serious violations. It is publicly posted on FDA's website. Here is what to do:

  1. Do not ignore it. You must respond within 15 business days.
  2. Immediately engage a regulatory attorney or experienced regulatory consultant.
  3. Develop a comprehensive corrective action plan that addresses every item in the letter.
  4. Consider a voluntary recall if any product safety issue is identified.
  5. Request a meeting with the FDA district office if appropriate.
warning

A Warning Letter that is ignored or poorly responded to can result in product seizure, injunction, import alert, or consent decree. These consequences can shut down facility operations permanently.

info

Once the inspection is over, your job is not done. Inspection readiness is not a one-time event - it is a continuous process.

  • Don’t “relax after inspection”—operate in a constant state of readiness
  • Turn observations into system improvements, not one-time fixes
  1. Convert all 483 actions into CAPA with owners, timelines, milestones
  2. Weekly CAPA review dashboard (status, risks, delays)
  3. No overdue actions— escalate early
  4. Complete all corrective actions you committed to in your 483 response. On time, every time.
  5. Update your SOPs and training records to reflect any gaps identified.
  6. Run another mock inspection focused on the areas the investigator examined.
  7. Debrief your entire quality team on the lessons learned.
  8. Rebuild your inspection readiness posture - assume FDA may return within 6 to 12 months.
  9. “Inspection readiness = everyone’s responsibility”
    • Encourage early reporting of issues (no blame)
    • Recognize compliant behaviors
  10. Inspection Readiness Kit (Always Ready)
  11. Updated:
    • a. Site overview deck
    • b. Org chart & SME list
    • c. Product list / process flow
    • d. Key SOP index
  12. Defined Front War Room / Back War Room roles
AUDIT → LEARN → IMPROVE → STANDARDIZE → SUSTAIN

Facilities that do well in FDA inspections are not lucky. They are prepared. They have:

  • Clean, organized, accurate documentation - always.
  • Trained employees who know how to behave during an inspection.
  • A culture where quality problems are documented and fixed - not hidden.
  • A team that knows their roles and stays calm under pressure.
  • A habit of regular self-inspection so nothing surprises them.
push_pin

The single best predictor of a successful FDA inspection is the quality of what you do every day — not what you do when the investigator is in the building.

checklist

QUICK CHECKLIST — PRINT AND KEEP HANDY

“If it is not documented, it did not happen.”

Before Any Inspection

“Inspection readiness is not an event—it is a daily discipline.”

Inspection team assigned with backups (War Room)
Command room set up and stocked
All documents current and retrievable within 30 minutes
Mock inspection completed
All staff briefed on inspection conduct
Legal/regulatory consultant contact saved
SOPs current, approved, and followed - Employees trained & confident - R&R clearly defined

When Investigator Arrives

No guessing / no assumptions Stay calm. Escort to reception.
Call Inspection Host immediately
Check FDA credentials and FDA 482
Photocopy credentials and 482
Activate full inspection team
Log arrival time

During the Inspection - Every Day

Be honest, clear, and concise. Answer only what is asked. If unsure → “I will check and revert.”
Front War Room / Back War Room defined. SMEs available on call & Clear communication flow.
All document requests logged
No documents handed over without review
Investigator escorted at all times
Notes taken for every activity
End-of-day team debrief done

At the Closing Meeting

Full team present
All 483 observations written down
FDA 483 received and signed
Internal 483 response team assigned

After the Inspection

483 Response Drafted & Reviewed
Response submitted within 15 business days
All CAPAs opened and tracked
Mock inspection updated and scheduled