FDA Inspection Playbook

The Agency established OII through the October 2024 reorganisation of the former Office of Regulatory Affairs. OII leads field inspections, investigations, import operations, emergency response, and law-enforcement activities. Its personnel collect evidence and provide insights that support fact-based Agency decisions. OII does not independently make every compliance or enforcement decision.

The office operates across the United States, its territories, and more than 90 countries. Current Agency figures state that OII conducts approximately 30,000 inspections and 10,000 investigations annually. An FDA mock inspection can help manufacturers rehearse document requests, interviews, and evidence-based reviews. It cannot reproduce every OII activity or guarantee a favourable inspection result. Understanding OII helps manufacturers prepare for the Agency’s field operations. Its personnel evaluate facilities, processes, records, data, and other evidence during authorised activities.

Investigates Beyond the Facility

OII conducts approximately 10,000 investigations annually. These activities involve consumer complaints, health fraud, product tampering, recall compliance, and public-health emergencies.

Investigations may examine products, records, distribution channels, imports, and other relevant evidence. The scope depends on the underlying concern and applicable authority.

The Office of Criminal Investigations operates within OII and handles alleged criminal conduct. It works with US attorneys, the Department of Justice, and other law enforcement partners.

Operates Continuously and Globally

OII works throughout the United States, its territories, and more than 90 countries. Its teams inspect facilities, investigate complaints, review imports, and coordinate with regulatory partners. The office also responds to emergencies and natural disasters involving regulated products. Its Emergency Operations Centre provides crisis coordination continuously throughout the year. OII’s global presence does not mean that every facility receives continuous monitoring. The Agency prioritises inspections and other activities according to risk, legal authorities, and programme needs. Manufacturers should therefore maintain continuous compliance and inspection readiness. They should not rely solely on previous inspection intervals.

How FDA Actually Conducts Inspections

Agency inspections follow defined procedures, assignments, and applicable compliance programmes. Their scope and techniques vary by product, inspection type, risk, and available evidence. Investigators do not rely on one universal checklist. They review records, observe operations, interview personnel, and compare actual practices with written procedures. Reviews may cover CAPA, complaints, validation, production, suppliers, laboratory controls, and other relevant systems. The applicable requirements and inspection scope determine which systems receive attention.

Questions may change as evidence develops. An inconsistency can prompt additional review when it suggests a related compliance concern. Investigators assess whether the establishment complies with applicable requirements and maintains effective control. An FDA mock inspection should test implementation, traceability, record accuracy, and the evidence supporting decisions. Written system design matters, but consistent performance and objective evidence matter equally.

What to Do When an FDA Investigator Arrives

Agency investigators may arrive with or without advance notice, depending on the circumstances. For a domestic inspection, the investigator normally presents credentials and issues Form FDA 482. A designated, knowledgeable representative should accompany the investigator and coordinate requests. Inspection duration varies with scope, facility complexity, findings, record availability, and follow-up needs. Onsite work may extend across multiple days, so no organisation should assume a fixed timetable.

Investigators gather facts and document observations. The Agency later evaluates the evidence and makes compliance and enforcement decisions. Follow your inspection procedure, maintain an accurate request log, and provide complete records within the applicable timeframe. Personnel should answer truthfully and concisely. If they do not know an answer, they should confirm the facts before responding. Never guess, speculate, alter records, or create missing documentation to answer a request.

A mock FDA inspection helps teams practise these controls before an actual visit. You cannot control the duration, but preparation can support an orderly and efficient inspection.

What Are FDA Investigators Actually Looking For?

Investigators gather evidence to assess compliance with applicable laws and regulations. They do not make the Agency’s final inspection classification while standing in the facility. Instead, they examine operations, review relevant records, interview personnel, and collect samples when appropriate. Procedures alone cannot demonstrate implementation. Investigators compare written requirements with actions, data, timelines, and documented decisions. They may trace deviations, complaints, CAPAs, changes, and validation activities across connected systems. Reliable records should show what occurred and who acted. They should also explain decisions and demonstrate whether actions proved effective. Conflicting records, unsupported conclusions, or ignored trends may lead to additional questions and broader review.

An FDA Form 483, when issued, lists observations that may indicate objectionable conditions or practices. It does not represent the Agency’s final determination of violations. Effective readiness depends on accurate records, controlled operations, credible data, and consistent execution. An FDA mock inspection should verify those connections through realistic questioning and document requests.

What to Say and Not to Say

Say:

• “Let me verify that and provide an accurate answer.”
• “Please clarify which record, date range, and format you need.”
• “Those records are stored off-site. We can retrieve them by this time tomorrow. Is that timeframe acceptable?”
• “Our designated contact will coordinate this request and confirm when we provide the records.”
• “I do not know the answer. I will confirm it with the responsible person and respond by [time].”
• “I need to correct something I said earlier. The accurate information is as follows.”
• “Would you discuss today’s inspection coverage and any observations or concerns identified so far?”
• “We have a documented safety or product-quality concern about photography here. May we explain it and discuss an alternative?”

These responses support accuracy, reasonable timing, and clear communication. The Agency recognises that some records require additional retrieval time. However, the organisation should provide a reasonable explanation and agree on a production timeframe.

A mock FDA inspection should teach personnel to provide factual answers rather than memorised scripts.

Do not say:

• “I think…”
• “Probably…”
• “We usually…”
• “That is how we have always done it.”
• “We do not have that,” before conducting a reasonable search.
• “That record does not matter.”
• “That is outside the inspection scope.”
• “You cannot take that photograph.”
• “Come back when our expert is available.”
• “I will create that document for you.”
• “We fixed everything,” without complete supporting evidence.
• “This is off the record.”

Unsupported statements, speculation, and unreasonable access restrictions can damage credibility. Some conduct may also delay, deny, or limit an inspection.

The Agency treats photography as an inspectional evidence-gathering method. Raise genuine safety or product-quality concerns through the designated contact. Do not impose a categorical prohibition without a documented reason and prompt escalation.

Never invent, alter, or recreate a missing record. State that the organisation has not located the record after completing a reasonable search. Then explain the applicable retention requirement, investigation, and corrective action when appropriate.

Best rule:
Answer truthfully, directly, and completely. Address the question asked, but include any context necessary to prevent a misleading answer. If you do not know, say so and commit to a reasonable response time.

An FDA mock inspection should test whether personnel can apply this rule under realistic questioning without guessing or relying on scripted answers.

How to Set Up Front Room and Back Room During an FDA Inspection

Manufacturers of any size may use a structured front-room and back-room model to coordinate an inspection. The Agency does not require this model; it is an industry management practice. The front room hosts direct interactions with investigators. The back room retrieves records, tracks requests, verifies information, and supports accurate responses. These rooms may be physical, virtual, or a combination of both. This structure should improve accuracy and organisation. It must never restrict investigator access, coach employees, filter evidence, or delay authorised requests. Investigators may speak directly with employees, observe operations, and request records within their inspectional authority.

A mock FDA inspection can test this structure and confirm that each participant understands their responsibilities.

Manage Requests With Speed and Control

When an investigator requests many records, clarify the scope and establish a reasonable production schedule. Provide responsive records as soon as reasonably possible. If phased production becomes necessary, explain the reason and obtain agreement on timing. Identify which records remain outstanding and when the team expects to provide them. Never assume that an initial production satisfies the entire request. Agency guidance identifies providing only some authorised records as conduct that may limit an inspection.

The back room may confirm document identity, version, date range, legibility, completeness, and responsiveness. It must not alter records, make unreasonable redactions, omit responsive information, or create unnecessary delays. Maintain a request log showing the request, assigned owner, receipt time, status, and exact records provided. Record any agreed deadlines and outstanding items. Speed supports the inspection only when the organisation also protects accuracy and completeness. An FDA mock inspection should test whether teams can produce records quickly without changing or withholding them.

Back Room (Support and Control Team)

The back room locates, reproduces, and tracks requested records. Participants may include quality, regulatory, document-control, information-technology, data-integrity, and subject-matter specialists. Enter every request into the inspection log. Assign an owner and record the request time, due time, status, and exact production.

The team may perform an administrative quality check before release. Confirm the correct record, version, date range, completeness, and legibility. Preserve the original record and never change its content. Escalate missing, conflicting, or incomplete records immediately. Describe their status accurately and begin the appropriate internal quality process. Never create a replacement record or delay production while attempting a correction. Use an approved, secure method to provide electronic records. Preserve relevant file formats and metadata when the investigator requests them. When records require off-site retrieval or extensive compilation, explain the circumstances and agree on a reasonable timeframe.

A mock FDA inspection can verify that the back room supports prompt, complete, and accurate production. Its purpose is coordination—not concealment or selective disclosure.

The Back-Room Leader as Inspection-Response Strategist

In our inspection experience, the back-room leader often carries the broadest strategic responsibility. The front-room host must communicate carefully because every statement may influence the investigator’s review.

Outside the investigator’s presence, the back-room leader can facilitate candid internal discussions and challenge assumptions. This person verifies facts, reconciles inconsistencies, coordinates specialists, prioritises requests, and advises the front-room team. The ideal leader combines authority, judgement, quality-system knowledge, and inspection experience. This responsibility may require someone more senior or experienced than the front-room host.

However, the back room must support complete, accurate, and timely responses. It must never conceal evidence, coach misleading answers, alter records, or delay authorised access. Internal discussions and notes are also not automatically legally privileged.

Using Former FDA Experience in the Back Room

In our experience, engaging a former FDA investigator as a back-room adviser can provide significant strategic value during an inspection. A qualified former investigator can interpret requests, anticipate follow-up questions, identify inconsistencies, prepare subject-matter experts, and guide escalation decisions. This adviser understands how investigators connect records, statements, and operational evidence. That perspective can help the response team remain accurate, organised, and prepared as the inspection develops.

The consultant must not imply special access, influence, or certainty about inspection outcomes. The organisation remains responsible for every statement, record, and compliance decision. Because the consultant left federal service more than seven years ago, the usual time-limited restrictions have expired. Nevertheless, the consultant should confirm that no matter-specific conflict applies.

Core Roles During an FDA Inspection

An inspection-response team benefits from clearly defined roles. However, the Agency does not prescribe these titles or require this staffing model. Smaller organisations may assign several responsibilities to one qualified person. Each responsibility should still have a clear owner and backup.

An FDA mock inspection should confirm that the team has enough capacity and understands every handoff.

• Senior Management Representative: Opening and Closeout Meetings. The owner, operator, agent-in-charge, or most responsible onsite official should receive the investigator. The site leader or senior quality representative should normally attend the opening meeting. CEO participation remains optional and should serve a clear purpose. Appropriate senior management should attend the closeout meeting whenever possible.
• Receptionist: First Contact. The receptionist should greet the investigator professionally and promptly notify the designated inspection contact. Normal visitor safety and security procedures may apply. Never require unnecessary waiting or use a safety video solely to create preparation time.
• Front-Room Leader. This person coordinates direct communication, document requests, meeting schedules, and subject-matter expert participation. The leader promotes accurate and consistent responses but does not control what employees may say. Investigators may speak directly with personnel about their responsibilities and working practices.
• Back-Room Leader. This person manages the request log, assigns owners, prioritises retrieval, and escalates potential problems. Whenever practical, appoint one of the organisation’s most knowledgeable quality-system leaders. The individual should have sufficient seniority and authority to mobilise departments, set priorities, and escalate issues promptly. No single leader must know every technical detail. However, they should understand system interdependencies and know which subject-matter experts to involve. The leader checks that records match each request and remain complete and legible. No review should alter records, omit responsive information, or create unreasonable delays.

A mock FDA inspection should test the handoff between the front-room and back-room leaders under realistic time pressure.

• Scribe. The scribe takes contemporaneous notes covering questions, answers, requests, document identifiers, commitments, and timing. This person normally observes rather than leads the discussion. Audio or video recording requires separate legal and organisational consideration.
• Escort. The escort accompanies the investigator and explains applicable safety, gowning, security, and contamination-control requirements. This person facilitates reasonable access and observes inspection activities. The escort must not obstruct movement, block employee interactions, or delay the inspection.
• Document Transfer Coordinator. This person securely transfers records between the back room and front room. Electronic inspections may not require a physical runner. The coordinator should track every file, delivery time, and outstanding item.
• Subject-Matter Experts. Specialists answer technical questions concerning their assigned responsibilities. They should respond truthfully, concisely, and from their own knowledge. When uncertain, they should acknowledge that uncertainty and verify the facts. The organisation should never provide coached or memorised answers.
• Information Technology or Data Specialist. This person supports electronic record retrieval, system demonstrations, metadata, audit trails, and secure file transfers. The specialist must preserve original records and explain system functions accurately.
• Inspection Adviser: Optional. A qualified consultant, including a former FDA investigator, can advise the back-room leader during the inspection. This adviser may interpret requests, anticipate follow-up questions, identify inconsistencies, and guide escalation. The consultant must not imply special influence or replace the organisation’s responsibility for its responses.
• Legal Counsel: As Needed. Counsel may advise on genuine questions involving inspection authority, privilege, potential enforcement exposure, or post-employment conflicts. The team should escalate these questions promptly without creating unnecessary delays.

No universal staffing minimum applies to every manufacturer. The organisation should base its structure on facility size, product risk, inspection scope, and available personnel.

An FDA mock inspection can reveal overloaded roles, communication gaps, and document-retrieval bottlenecks before an actual inspection.

Establish an Internal FDA Inspection Playbook and Train Your SMEs

The Agency does not require manufacturers to maintain a document called an inspection playbook. However, many organisations formalise one to ensure consistent inspection responses. When the organisation treats its playbook as a quality-system document, apply the relevant document-control requirements. Define responsibilities, backups, communication pathways, document handling, escalation, and request tracking.

The playbook should address reception, front-room and back-room operations, escorts, interviews, electronic records, daily briefings, and closeout activities. It should also explain how personnel handle missing records, delayed retrieval, and questions concerning inspection authority. Applicable CGMP and quality-system requirements require qualified and appropriately trained personnel. They do not specifically require training on investigator interviews. However, interview-response training remains a valuable readiness measure. Subject-matter experts should answer truthfully from their own knowledge. They should avoid speculation and include any context needed to prevent a misleading answer.

A mock FDA inspection can test the playbook through realistic questions, record requests, and communication challenges. Experienced FDA Consulting support may also help train SMEs without scripting their answers.

Prepare the Front Desk and Coordinate SME Contacts

An inspection may begin at reception. The receptionist should remain professional, obtain the investigator’s name, and immediately notify the designated contacts. The owner, operator, agent-in-charge, or most responsible onsite official should examine the credentials. That official normally receives FDA Form 482 during a domestic establishment inspection.

Reception personnel must not photocopy or photograph investigator credentials. Normal visitor safety and security procedures may apply, provided they do not unreasonably delay or limit the inspection. The receptionist may record the arrival time, team size, names provided, immediate requests, and relevant statements. They should report this information exactly without assumptions or interpretation. Do not restrict the receptionist to one scripted sentence. If an investigator asks a substantive question, the receptionist should refer it to the designated contact without guessing.

A suitable response is:

“Welcome. I will notify our designated inspection contact immediately. They will meet you here shortly.”

An FDA mock inspection should test reception procedures, contact availability, notification speed, and the arrival log.

Conduct Periodic Internal FDA Inspection Drills

Inspection-response drills should simulate realistic arrivals, questioning, document requests, handoffs, and subject-matter expert interviews. No regulation establishes a universal drill frequency. Set the frequency according to product risk, organisational changes, inspection history, and previous drill results. Consider additional exercises after significant personnel, facility, process, or regulatory changes.

The exercise controller may test the initial notification process without advance warning. However, the controller should identify the exercise before requesting actual facility access or regulated records. A mock FDA inspection drill must remain clearly distinguishable from official government activity. Participants must never impersonate federal officers, display counterfeit credentials, or claim government authority.

Use separate activation messages:

“Training exercise—activate the inspection drill procedure.”

For an actual inspection, use:

“Actual Agency inspection—activate the inspection-response procedure.”

After each drill, document findings, assign responsible owners, and establish completion dates. Evaluate identified quality-system weaknesses through CAPA or another appropriate process.

Drills should assess performance, not merely confirm that a written procedure exists.

What Goes Wrong During an FDA Inspection

Many inspection problems arise from execution failures, even when procedures exist. Common examples include conflicting explanations, unavailable personnel, slow record retrieval, and incomplete document production. Communication creates additional risk when personnel speculate, overstate conclusions, or contradict approved records. Poor front-room and back-room coordination may also produce duplicate, inconsistent, or delayed responses. Investigators compare statements with records and observed practices. An inconsistency may prompt follow-up questions or broader review when it suggests a related compliance concern.

No single weak answer automatically expands an inspection. However, unsupported statements can direct attention towards connected records, systems, or decisions. Inspection problems may be technical, procedural, or operational. Even a well-designed quality system may appear uncontrolled when personnel cannot explain or demonstrate its implementation.

An FDA mock inspection can expose communication gaps, overloaded roles, retrieval problems, and inconsistent execution before an actual inspection.

FDA Forms 482, 483, and 484 — What Are They?

The Agency uses several forms at different stages of an inspection. Each form serves a specific purpose, and not every inspection involves all three. These forms may document notice, observations, or physical sample collection. They do not all represent findings or final Agency decisions. A mock FDA inspection should prepare personnel to receive, review, log, and escalate each form correctly.

Form 483 Inspectional Observations

At the inspection’s conclusion, an investigator may issue Form 483 when reportable observations exist. It lists conditions that may constitute violations, based on the investigator’s judgment. The document may not include every objectionable condition. More importantly, it does not constitute the Agency’s final determination.

Receiving a Form 483 does not mean the establishment has “failed” its inspection. Likewise, receiving no Form 483 does not guarantee that the Agency will identify no further concerns. The Agency later evaluates the inspection report, supporting evidence and the organisation’s response. It then determines the final inspection classification and whether further action is appropriate.

An FDA mock inspection should prepare management to discuss observations accurately and begin a controlled response process.

Form 463a Affidavit

The Agency may use Form FDA 463a or another affidavit to document material facts from a knowledgeable individual. The individual should provide only facts they can personally verify. Before signing, the individual should read the complete statement and correct any inaccuracies. They must affirm that the statement is true and accurate. The investigator then witnesses the signature and affirmation; a separate notary is not necessarily involved.

A person may request legal counsel’s review before signing. However, that request should not create an unreasonable delay. If the person declines to sign, the investigator may document the refusal and its stated reason. Never sign an incomplete, inaccurate, or speculative statement. A mock FDA inspection should train personnel to recognise and escalate affidavit requests immediately.

A Well-Trained, Silent Scriber Is Essential

A dedicated scribe should document the inspection accurately and in real time. Although not required by the Agency, this role provides an important inspection-readiness control. The scribe records each request, response, document provided, timestamp, follow-up commitment, and significant investigator statement. Notes should remain factual and avoid speculation, interpretation, or legal conclusions.

A disciplined scribe normally remains silent and does not participate in substantive discussions. They should not answer technical questions or speak for the organisation. If directly addressed, the scribe should refer the question to the front-room leader. These notes support daily debriefings, request reconciliation, and consistent follow-up. They may also help the team recognise emerging concerns before the inspection concludes. The organisation should control, retain, and review inspection notes under its approved procedures. It should not assume that the notes carry legal privilege or confidentiality.

An FDA mock inspection can test the scribe’s accuracy, discipline, and coordination under realistic conditions. For structured scribe training, delivered remotely or on-site, contact CIRG.

Do not wait for the Agency to test your systems. Schedule a periodic mock FDA inspection to evaluate performance under realistic conditions. Frequency should reflect product risk, operational changes, inspection history, significant CAPAs, and planned regulatory submissions. The exercise can simulate investigator questioning, record tracing, facility walkthroughs, and cross-functional pressure.

A well-designed simulation may identify weaknesses in execution, not merely documentation. It tests front-room discipline, back-room control, document retrieval, and SME responses under scrutiny. More importantly, it shows whether systems remain controlled when challenged.

Experienced FDA consultants can offer insight into current inspection methods and common areas of concern. Findings should support a prioritised remediation plan rather than promise a particular inspection outcome. If inspection readiness matters to your organisation, test it before the Agency does.