The inspection preparation plan

The first thing to do when notification arrives is not to start pulling documents. It is to build a plan. Reactive scrambling -- three people pulling binders while someone else runs to the pharmacy -- is the enemy of systematic readiness. What you need is a structured sequence of activities, each assigned to a specific person, each with a deadline, each building toward a defined state of readiness by the morning the inspector arrives.

I want to be direct about something: the preparation plan is not a bureaucratic exercise. It is a project management tool for a time-limited, high-stakes event. The inspection date is fixed. The tasks are knowable. The question is whether you will execute them in an organized sequence or discover on day one that the sub-investigator's curriculum vitae has not been updated in 18 months and the pharmacy's temperature monitoring log has a gap nobody noticed.

The plan should be structured around milestones. Not every site receives the same advance notice -- FDA inspections typically provide two to four weeks, EMA inspections may provide longer notice with a formal inspection plan, and sponsor audits vary. But regardless of the timeline, the preparation activities cluster into natural phases.

Two weeks before: inventory and assignment

The two-week mark is for assessment and delegation, not for fixing problems. The preparation team -- typically the coordinator, the principal investigator, and any study-specific staff involved in the inspected protocol -- should meet within 48 hours of receiving notification. This meeting has three objectives.

First, review the notification itself. What study is being inspected? Does the notification specify any particular focus areas? For FDA inspections, the notification letter rarely provides detail beyond the study name, but the identity of the study narrows the scope of preparation. For EMA inspections, the notification often includes an inspection plan with specific areas of focus -- informed consent, safety reporting, investigational product management -- which allows more targeted preparation. For sponsor audits, the audit agenda is usually provided in advance and may specify which participants, which time periods, or which processes will be reviewed.

Second, conduct a document status inventory. This is not a full review of every document -- it is a systematic check of document currency. Are regulatory binders current? Is the delegation log up to date? Are all training records filed? Are investigator CVs and medical licenses current? Has the IRB/IEC approval been maintained without gaps? This inventory identifies what needs attention, not how to fix it.

Third, assign responsibilities. Every preparation task should have a name attached to it -- not a team, not a department, a specific person. The coordinator typically manages the overall checklist, but document retrieval, pharmacy preparation, investigator briefing, and logistics each need an owner. If a task does not have a name next to it, that task will not get done.

One week before: remediation and briefing

The one-week mark is when preparation shifts from identifying gaps to closing them. Every document deficiency identified during the two-week inventory should have a remediation plan in progress. Expired GCP training certificates need to be renewed -- and I have seen sites discover, to their considerable distress, that online GCP training courses take 8 to 12 hours to complete, which is difficult to accomplish when the coordinator also has participants to see and data to enter. Lapsed medical licenses need to be verified and updated copies filed. Missing IRB/IEC correspondence needs to be located or reconstructed through the IRB office.

This is also the week for the team briefing -- the single most important preparation activity, in my view, for the human side of the inspection. I address this in detail in the next section, but its timing matters: conduct the briefing during the one-week phase, not the day before. The team needs time to absorb the information, ask follow-up questions, and mentally prepare. A day-before briefing creates anxiety rather than confidence.

Logistics deserve attention at this stage as well. The inspector will need a private workspace -- a room with a door, a desk, a chair, network access if electronic records are involved, and proximity to the records being reviewed. This cannot be the coordinator's desk in a shared office. It cannot be a conference room that has been booked for other meetings during the inspection week. Reserve the space now, confirm it for the full duration of the inspection, and ensure it has working electrical outlets, adequate lighting, and reasonable climate control. These details sound mundane. They are. And they matter more than you might think -- an inspector working in a cramped, hot room without reliable internet access begins the day with an unfavorable impression that no amount of excellent documentation can entirely overcome.

Briefing the study team

The team briefing is where preparation moves from documents and logistics to people. And people, not documents, are what inspectors interact with. The most perfectly organized binder in the world cannot compensate for a sub-investigator who panics during a question about eligibility assessment, or a research nurse who volunteers information about a protocol deviation the inspector had not asked about, or a principal investigator who becomes defensive when the inspector asks why a consent form was signed after the first study procedure.

The briefing should cover three categories: expectations, ground rules, and escalation.

What to expect

Most study team members have never experienced a regulatory inspection. Their mental model -- shaped by television, anxiety, and institutional rumor -- may bear little resemblance to the actual event. The briefing should ground the team in reality. An FDA inspection typically lasts three to five business days. The inspector will begin with an opening meeting to explain the scope and logistics. The inspector will review documents -- regulatory binders, participant charts, source documents, pharmacy records. The inspector will interview the principal investigator and may interview other study team members individually. The inspector will conclude with a closeout meeting where preliminary findings are discussed. The process is formal but civil. The inspector is a professional doing a job, not a prosecutor building a case.

Tell the team who will be present during the inspection and what role each person plays. The principal investigator is the regulatory point of contact and should be available for interviews and questions. The coordinator is typically the logistics manager -- pulling documents, facilitating access, coordinating schedules. A designated note-taker -- and this role is critical -- should document every question the inspector asks, every document the inspector requests, every observation the inspector makes. This contemporaneous record is invaluable for post-inspection response.

Escalation procedures

Not every question from an inspector can or should be answered by the person to whom it is directed. The team needs to know, before the inspection begins, when and how to escalate.

Clinical questions -- questions about medical decisions, eligibility determinations, adverse event assessments -- should be directed to the principal investigator. The coordinator should not attempt to explain why a participant with an exclusionary lab value was enrolled. That is the investigator's determination to explain.

Questions that touch on institutional policy -- human resources records, facility certifications, institutional IRB procedures -- should be directed to the appropriate institutional contact. The coordinator is not the spokesperson for the hospital's IRB.

Questions that raise legal concerns -- allegations of misconduct, requests for personnel records, questions that seem designed to establish individual culpability -- should be noted and, if institutional policy permits, escalated to legal counsel. The site has the right to consult with counsel during an inspection, and exercising that right is not an admission of wrongdoing. But the team must know this in advance. Discovering mid-inspection that you want legal advice and not knowing how to access it is a preventable failure.

The escalation protocol should be simple and rehearsed: if a team member receives a question outside their scope, they should say, "That is outside my area of responsibility. Let me connect you with the appropriate person," and then immediately notify the coordinator, who manages the logistics of connecting the inspector with the right team member. No one should feel embarrassed or pressured about escalating. The briefing should make clear that escalation is expected, not exceptional.

Organizing documents beyond the binder

Your regulatory binder should already be organized, filed, and current. If it is not, the remediation during the two-week preparation period should address that. But a regulatory inspection extends well beyond the contents of the regulatory binder, and the documents the inspector may request include materials that many sites do not think about until the inspector asks for them.

The distinction I want to draw here is between documents that are part of your routine binder maintenance and documents that are ancillary to the binder but essential for inspection. Earlier courses in this track taught you how to maintain the binder. This lesson addresses the materials that surround and support the binder -- the institutional records, the summary documents, and the participant-level files that an inspector may reasonably request.

Institutional and site-level documents

The inspector may ask for documents that live outside the study binder entirely. Institutional policies on research conduct, human subjects protection, and conflict of interest are maintained by the institution, not the study team -- but the study team should know where to find them and ensure they are accessible. The site's standard operating procedures (SOPs) for research activities -- consent processes, adverse event reporting, data management, sample handling -- should be identified, located, and available. Staff training records that demonstrate GCP training currency for every person listed on the delegation log must be verifiable. And the delegation log itself will be scrutinized not just for completeness, but for accuracy -- does it reflect who actually performed each task, and are all delegated individuals qualified and trained?

Participant-level documentation

Inspectors typically select a subset of participants for detailed review -- often five to ten participants from a larger enrollment, chosen based on factors the inspector does not always disclose. For each selected participant, the inspector will want to see the complete source record alongside the case report form, comparing what happened (as documented in the source) with what was reported (as entered in the CRF). The coordinator should prepare participant files so that this comparison can be conducted efficiently. Each file should contain, in accessible order, the signed consent form (every version), source documents for each study visit, laboratory reports, imaging reports if applicable, adverse event documentation, and any protocol deviation reports for that participant.

Additionally, prepare summary-level documents that inspectors commonly request: an enrollment table listing all participants with key dates (consent, first dose, last visit, current status), a screen failure log with reasons for exclusion, and a protocol deviation log organized chronologically. These summary documents allow the inspector to identify which participants to examine in detail, and having them readily available demonstrates organizational competence.

Mock inspections: rehearsal that reveals

I want to address something that many sites skip because it feels like an unnecessary luxury when time is short: the mock inspection. It is not a luxury. It is, in my experience, the single preparation activity with the highest return on investment, precisely because it reveals problems that checklist-based preparation cannot.

A checklist tells you whether a document exists. A mock inspection tells you whether you can find it when someone asks for it. A checklist tells you that the principal investigator has been briefed. A mock inspection reveals that the investigator, under even simulated pressure, defaults to volunteering information about problems the questioner did not ask about. A checklist tells you that pharmacy temperature logs are maintained. A mock inspection reveals that the log has a three-day gap from last August when the battery in the temperature monitoring device died and nobody noticed for 72 hours.

How to conduct an effective mock inspection

The mock inspection should be conducted no later than two to three days before the actual inspection, leaving enough time to address any issues discovered but late enough that preparation is substantially complete. The person conducting the mock should be someone who is not part of the study team -- ideally a quality assurance professional, a colleague from another study at the site, or an external consultant with inspection experience. The point is unfamiliar eyes asking unfamiliar questions.

The mock should follow the actual inspection format. Begin with an opening meeting. Have the mock inspector request documents -- the regulatory binder, specific participant files, pharmacy records, training records. Have them interview the principal investigator and at least one other team member. Ask questions that the team might find uncomfortable: "Walk me through the consent process for participant 007." "Why was this participant enrolled when the screening laboratory value appears to be outside the eligibility range?" "Can you show me the temperature log for the IP storage unit for the month of August?" The value of the mock is not in confirming what you already know works. It is in discovering what does not.

After the mock, debrief immediately. Catalog every issue identified -- missing documents, slow retrieval times, interview responses that were too expansive or too defensive, logistics problems. Assign remediation for each issue and verify completion before the actual inspection. And here is something that matters more than the specific issues found: the mock inspection reduces anxiety. The team has now experienced something resembling the inspection. The unknown has become the somewhat familiar. That psychological shift -- from dread to preparedness -- changes the team's performance on the actual day.

Planning for the unexpected

Preparation plans work best when they include contingency thinking. The principal investigator may be called to an emergency during the inspection. A key team member may be out sick. The electronic health record system may go down on inspection day. The inspector may request a document that nobody anticipated.

For each of these scenarios, the preparation plan should include a documented response. If the investigator is unavailable, who is the designated backup, and is that person briefed? If a team member is absent, who covers their responsibilities? If a system goes down, what is the alternative access pathway for electronic records? And for unanticipated document requests, the team should know the protocol: acknowledge the request, ask whether a specific deadline applies, retrieve the document as quickly as possible, and document what was requested and when it was provided.

The coordinator's role during the inspection is, in many ways, the role of a project manager for a multi-day event. That role is easier -- and the inspection goes more smoothly -- when contingencies have been anticipated rather than improvised.

The inspection preparation plan

The first thing to do when notification arrives is not to start pulling documents. It is to build a plan. Reactive scrambling -- three people pulling binders while someone else runs to the pharmacy -- is the enemy of systematic readiness. What you need is a structured sequence of activities, each assigned to a specific person, each with a deadline, each building toward a defined state of readiness by the morning the inspector arrives.

I want to be direct about something: the preparation plan is not a bureaucratic exercise. It is a project management tool for a time-limited, high-stakes event. The inspection date is fixed. The tasks are knowable. The question is whether you will execute them in an organized sequence or discover on day one that the sub-investigator's curriculum vitae has not been updated in 18 months and the pharmacy's temperature monitoring log has a gap nobody noticed.

The plan should be structured around milestones. Not every site receives the same advance notice -- FDA inspections typically provide two to four weeks, EMA inspections may provide longer notice with a formal inspection plan, and sponsor audits vary. But regardless of the timeline, the preparation activities cluster into natural phases.

Two weeks before: inventory and assignment

The two-week mark is for assessment and delegation, not for fixing problems. The preparation team -- typically the coordinator, the principal investigator, and any study-specific staff involved in the inspected protocol -- should meet within 48 hours of receiving notification. This meeting has three objectives.

First, review the notification itself. What study is being inspected? Does the notification specify any particular focus areas? For FDA inspections, the notification letter rarely provides detail beyond the study name, but the identity of the study narrows the scope of preparation. For EMA inspections, the notification often includes an inspection plan with specific areas of focus -- informed consent, safety reporting, investigational product management -- which allows more targeted preparation. For sponsor audits, the audit agenda is usually provided in advance and may specify which participants, which time periods, or which processes will be reviewed.

Second, conduct a document status inventory. This is not a full review of every document -- it is a systematic check of document currency. Are regulatory binders current? Is the delegation log up to date? Are all training records filed? Are investigator CVs and medical licenses current? Has the IRB/IEC approval been maintained without gaps? This inventory identifies what needs attention, not how to fix it.

Third, assign responsibilities. Every preparation task should have a name attached to it -- not a team, not a department, a specific person. The coordinator typically manages the overall checklist, but document retrieval, pharmacy preparation, investigator briefing, and logistics each need an owner. If a task does not have a name next to it, that task will not get done.

One week before: remediation and briefing

The one-week mark is when preparation shifts from identifying gaps to closing them. Every document deficiency identified during the two-week inventory should have a remediation plan in progress. Expired GCP training certificates need to be renewed -- and I have seen sites discover, to their considerable distress, that online GCP training courses take 8 to 12 hours to complete, which is difficult to accomplish when the coordinator also has participants to see and data to enter. Lapsed medical licenses need to be verified and updated copies filed. Missing IRB/IEC correspondence needs to be located or reconstructed through the IRB office.

This is also the week for the team briefing -- the single most important preparation activity, in my view, for the human side of the inspection. I address this in detail in the next section, but its timing matters: conduct the briefing during the one-week phase, not the day before. The team needs time to absorb the information, ask follow-up questions, and mentally prepare. A day-before briefing creates anxiety rather than confidence.

Logistics deserve attention at this stage as well. The inspector will need a private workspace -- a room with a door, a desk, a chair, network access if electronic records are involved, and proximity to the records being reviewed. This cannot be the coordinator's desk in a shared office. It cannot be a conference room that has been booked for other meetings during the inspection week. Reserve the space now, confirm it for the full duration of the inspection, and ensure it has working electrical outlets, adequate lighting, and reasonable climate control. These details sound mundane. They are. And they matter more than you might think -- an inspector working in a cramped, hot room without reliable internet access begins the day with an unfavorable impression that no amount of excellent documentation can entirely overcome.

Briefing the study team

The team briefing is where preparation moves from documents and logistics to people. And people, not documents, are what inspectors interact with. The most perfectly organized binder in the world cannot compensate for a sub-investigator who panics during a question about eligibility assessment, or a research nurse who volunteers information about a protocol deviation the inspector had not asked about, or a principal investigator who becomes defensive when the inspector asks why a consent form was signed after the first study procedure.

The briefing should cover three categories: expectations, ground rules, and escalation.

What to expect

Most study team members have never experienced a regulatory inspection. Their mental model -- shaped by television, anxiety, and institutional rumor -- may bear little resemblance to the actual event. The briefing should ground the team in reality. An FDA inspection typically lasts three to five business days. The inspector will begin with an opening meeting to explain the scope and logistics. The inspector will review documents -- regulatory binders, participant charts, source documents, pharmacy records. The inspector will interview the principal investigator and may interview other study team members individually. The inspector will conclude with a closeout meeting where preliminary findings are discussed. The process is formal but civil. The inspector is a professional doing a job, not a prosecutor building a case.

Tell the team who will be present during the inspection and what role each person plays. The principal investigator is the regulatory point of contact and should be available for interviews and questions. The coordinator is typically the logistics manager -- pulling documents, facilitating access, coordinating schedules. A designated note-taker -- and this role is critical -- should document every question the inspector asks, every document the inspector requests, every observation the inspector makes. This contemporaneous record is invaluable for post-inspection response.

Escalation procedures

Not every question from an inspector can or should be answered by the person to whom it is directed. The team needs to know, before the inspection begins, when and how to escalate.

Clinical questions -- questions about medical decisions, eligibility determinations, adverse event assessments -- should be directed to the principal investigator. The coordinator should not attempt to explain why a participant with an exclusionary lab value was enrolled. That is the investigator's determination to explain.

Questions that touch on institutional policy -- human resources records, facility certifications, institutional IRB procedures -- should be directed to the appropriate institutional contact. The coordinator is not the spokesperson for the hospital's IRB.

Questions that raise legal concerns -- allegations of misconduct, requests for personnel records, questions that seem designed to establish individual culpability -- should be noted and, if institutional policy permits, escalated to legal counsel. The site has the right to consult with counsel during an inspection, and exercising that right is not an admission of wrongdoing. But the team must know this in advance. Discovering mid-inspection that you want legal advice and not knowing how to access it is a preventable failure.

The escalation protocol should be simple and rehearsed: if a team member receives a question outside their scope, they should say, "That is outside my area of responsibility. Let me connect you with the appropriate person," and then immediately notify the coordinator, who manages the logistics of connecting the inspector with the right team member. No one should feel embarrassed or pressured about escalating. The briefing should make clear that escalation is expected, not exceptional.

Organizing documents beyond the binder

Your regulatory binder should already be organized, filed, and current. If it is not, the remediation during the two-week preparation period should address that. But a regulatory inspection extends well beyond the contents of the regulatory binder, and the documents the inspector may request include materials that many sites do not think about until the inspector asks for them.

The distinction I want to draw here is between documents that are part of your routine binder maintenance and documents that are ancillary to the binder but essential for inspection. Earlier courses in this track taught you how to maintain the binder. This lesson addresses the materials that surround and support the binder -- the institutional records, the summary documents, and the participant-level files that an inspector may reasonably request.

Institutional and site-level documents

The inspector may ask for documents that live outside the study binder entirely. Institutional policies on research conduct, human subjects protection, and conflict of interest are maintained by the institution, not the study team -- but the study team should know where to find them and ensure they are accessible. The site's standard operating procedures (SOPs) for research activities -- consent processes, adverse event reporting, data management, sample handling -- should be identified, located, and available. Staff training records that demonstrate GCP training currency for every person listed on the delegation log must be verifiable. And the delegation log itself will be scrutinized not just for completeness, but for accuracy -- does it reflect who actually performed each task, and are all delegated individuals qualified and trained?

Participant-level documentation

Inspectors typically select a subset of participants for detailed review -- often five to ten participants from a larger enrollment, chosen based on factors the inspector does not always disclose. For each selected participant, the inspector will want to see the complete source record alongside the case report form, comparing what happened (as documented in the source) with what was reported (as entered in the CRF). The coordinator should prepare participant files so that this comparison can be conducted efficiently. Each file should contain, in accessible order, the signed consent form (every version), source documents for each study visit, laboratory reports, imaging reports if applicable, adverse event documentation, and any protocol deviation reports for that participant.

Additionally, prepare summary-level documents that inspectors commonly request: an enrollment table listing all participants with key dates (consent, first dose, last visit, current status), a screen failure log with reasons for exclusion, and a protocol deviation log organized chronologically. These summary documents allow the inspector to identify which participants to examine in detail, and having them readily available demonstrates organizational competence.

Mock inspections: rehearsal that reveals

I want to address something that many sites skip because it feels like an unnecessary luxury when time is short: the mock inspection. It is not a luxury. It is, in my experience, the single preparation activity with the highest return on investment, precisely because it reveals problems that checklist-based preparation cannot.

A checklist tells you whether a document exists. A mock inspection tells you whether you can find it when someone asks for it. A checklist tells you that the principal investigator has been briefed. A mock inspection reveals that the investigator, under even simulated pressure, defaults to volunteering information about problems the questioner did not ask about. A checklist tells you that pharmacy temperature logs are maintained. A mock inspection reveals that the log has a three-day gap from last August when the battery in the temperature monitoring device died and nobody noticed for 72 hours.

How to conduct an effective mock inspection

The mock inspection should be conducted no later than two to three days before the actual inspection, leaving enough time to address any issues discovered but late enough that preparation is substantially complete. The person conducting the mock should be someone who is not part of the study team -- ideally a quality assurance professional, a colleague from another study at the site, or an external consultant with inspection experience. The point is unfamiliar eyes asking unfamiliar questions.

The mock should follow the actual inspection format. Begin with an opening meeting. Have the mock inspector request documents -- the regulatory binder, specific participant files, pharmacy records, training records. Have them interview the principal investigator and at least one other team member. Ask questions that the team might find uncomfortable: "Walk me through the consent process for participant 007." "Why was this participant enrolled when the screening laboratory value appears to be outside the eligibility range?" "Can you show me the temperature log for the IP storage unit for the month of August?" The value of the mock is not in confirming what you already know works. It is in discovering what does not.

After the mock, debrief immediately. Catalog every issue identified -- missing documents, slow retrieval times, interview responses that were too expansive or too defensive, logistics problems. Assign remediation for each issue and verify completion before the actual inspection. And here is something that matters more than the specific issues found: the mock inspection reduces anxiety. The team has now experienced something resembling the inspection. The unknown has become the somewhat familiar. That psychological shift -- from dread to preparedness -- changes the team's performance on the actual day.

Planning for the unexpected

Preparation plans work best when they include contingency thinking. The principal investigator may be called to an emergency during the inspection. A key team member may be out sick. The electronic health record system may go down on inspection day. The inspector may request a document that nobody anticipated.

For each of these scenarios, the preparation plan should include a documented response. If the investigator is unavailable, who is the designated backup, and is that person briefed? If a team member is absent, who covers their responsibilities? If a system goes down, what is the alternative access pathway for electronic records? And for unanticipated document requests, the team should know the protocol: acknowledge the request, ask whether a specific deadline applies, retrieve the document as quickly as possible, and document what was requested and when it was provided.

The coordinator's role during the inspection is, in many ways, the role of a project manager for a multi-day event. That role is easier -- and the inspection goes more smoothly -- when contingencies have been anticipated rather than improvised.