The email that starts the clock

The email arrives on a Wednesday morning. The monitor confirms the next on-site visit: two weeks from Monday. If you have been maintaining the weekly and monthly readiness routines covered in the previous lesson, this email should produce a mild, professional alertness -- not panic. The ongoing routines have kept your data entry current, your queries resolved, your delegation log accurate, and your regulatory binder filed. The foundation is solid.

But the foundation is not the whole house. There are preparation activities that cannot -- and should not -- be done on a rolling basis because they are visit-specific. The monitor will review a particular set of participants. The investigator needs to be available at particular times. The workspace needs to be configured for an outside visitor who will spend hours reviewing documents. These are not ongoing maintenance tasks. They are targeted preparations that begin when the visit date is confirmed.

What follows is a two-phase preparation sequence: a two-week checklist that addresses the substantive gaps, and a two-day checklist that handles the logistical final staging. Together, they transform the general readiness you have maintained into specific readiness for this particular visit. I have watched this approach work at sites ranging from single-investigator community practices to 40-bed academic research units. The activities scale, but the structure holds.

And here is the part that matters most: this sequence assumes you have been maintaining your ongoing routines. If you have not, you will spend most of the two-week window catching up on what should have been done continuously -- and you will still arrive at the visit less prepared than the coordinator who maintained the routines and spent those same two weeks on targeted preparation. The previous lesson was not a suggestion. It was a prerequisite.

The two-week checklist: closing the substantive gaps

Two weeks is not a long time, but it is enough to address every preparation task that requires substantive work -- resolving data queries, completing overdue entries, coordinating investigator schedules, and verifying that the regulatory infrastructure is current. The two-week mark is when you shift from maintenance mode to preparation mode.

I organize the two-week checklist into five domains. Each one targets a specific area that monitors routinely assess, and each maps directly to monitoring activities described in ICH E6(R3), Section 3.11.4.5.

Query resolution: clearing the backlog

If you have maintained weekly query reviews, your open query count should be manageable -- perhaps a handful of queries from the past week. If not, this is where the pain begins. Monitors evaluate query resolution timelines as a direct indicator of site responsiveness, and per Section 3.11.4.5.4(b), monitoring includes "checking the accuracy, completeness and consistency of the reported trial data" and whether data "were reported in a timely manner."

Open your EDC query inbox and sort by age, oldest first. Every query that can be resolved with information available at the site should be resolved within this two-week window. Queries requiring investigator review should be flagged and routed immediately -- do not wait until next week. Queries requiring external information (laboratory results, outside records) should be escalated to the relevant department with a clear deadline.

The goal is zero open queries at the time of the visit. That is ambitious, and it is not always achievable -- some queries depend on external parties beyond your control. But the monitor should see at most a few recently issued queries, not a trail of items that have been sitting for weeks.

Data entry completion: closing the lag

Review the EDC for any participant visits that have occurred but are not yet entered. The two-week window gives you enough time to complete even a moderate data entry backlog, but only if you start immediately. Per ICH E6(R3), Section 2.12.5, investigators must ensure "the accuracy, completeness, legibility and timeliness of the data reported to the sponsor."

There is a subtlety here that experienced coordinators understand: partial data entry is often worse than no entry at all. A partially completed eCRF page may look like a finished entry with missing data, rather than an entry in progress. Complete every form you start. If you cannot finish a particular form because source documents are missing, note why and plan to resolve it before the visit.

Investigator availability: schedule coordination

Contact the principal investigator and confirm their availability during the monitoring visit. This seems obvious, but it is one of the most common logistical failures at research sites. The monitor will need the investigator's time for at least two things: discussing any significant findings and, in many protocols, reviewing and signing the monitoring visit log or confirmation form.

Block time on the investigator's calendar -- typically 30 to 60 minutes at the end of the first day or the beginning of the second. If the investigator has an unavoidable conflict on the scheduled visit days, communicate this to the monitor immediately. Most monitors can adjust their schedule if given advance notice. What they cannot accommodate is discovering on arrival that the investigator is in surgery all day.

Delegation log and personnel currency

Even if you have been reviewing the delegation log weekly, the two-week mark is the time for a final, careful verification. Check every person currently listed against actual site operations. Has anyone left the team? Has anyone's role changed? Has any new staff member started performing trial-related duties?

Per ICH E6(R3), Section 3.11.4.5.2(c), monitoring includes "confirming that the investigator is maintaining the essential records." The delegation log is among the most frequently reviewed essential records, and an outdated entry -- a person listed who no longer works at the site, or a person performing activities who is not listed -- is a finding that experienced monitors catch quickly.

Essential document expiration scan

Check all dated documents for expiration status. This is distinct from the monthly currency check covered in the previous lesson -- here, you are specifically confirming that no document will expire between now and the monitoring visit. The critical items:

IRB/IEC approval: When does the current approval period end? If it expires within the next 30 days, verify that the continuing review submission has been made or is in progress.

Medical licenses for all delegated staff: Are all current? Some state medical boards issue renewals that take weeks to process. An expired license for the principal investigator is a serious finding.

Laboratory certifications (CLIA, CAP, or equivalent): If the site uses a local laboratory for protocol-specified tests, confirm the certification is current.

GCP training certificates: Some sponsors require annual GCP training. If any delegated staff member's training has lapsed, address it now.

Proactive disclosure: the conversation that changes everything

The sixth item on the two-week checklist deserves its own discussion, because it represents a mindset shift that separates competent coordinators from exceptional ones.

Every site has issues. A participant missed a visit window by two days. A laboratory sample was hemolyzed and had to be redrawn. A protocol deviation occurred during a weekend visit when the usual coordinator was off duty. These things happen in clinical research. They are not ideal, but they are not evidence of a failing site. What distinguishes a strong site is not the absence of problems but the transparency with which problems are communicated.

When you know the monitor will discover an issue during the visit, you have a choice. You can wait and let the monitor find it -- which guarantees the issue will appear as a "discovery" in the monitoring report, framed as something the site had not addressed. Or you can disclose it proactively before the visit, with documentation of what happened, what you did about it, and what you changed to prevent recurrence.

The second approach is always better. Always. Proactive disclosure signals that the site is self-monitoring, that the quality management system is working, and that the coordinator understands the difference between hiding problems and managing them. Per ICH E6(R3), Section 3.11.1, quality assurance should include "implementing risk-based strategies to identify potential or actual causes of serious noncompliance with the protocol, GCP and/or applicable regulatory requirements to enable their corrective and preventive actions." Proactive disclosure is evidence that your site has such processes.

In my experience, monitors respond to proactive disclosure with respect, not criticism. A coordinator who says, "Before you start, I want to flag two deviations that occurred since your last visit -- here is the documentation and the corrective actions we took" has just transformed a potential finding into a demonstration of competence.

The two-day checklist: final staging

Two days before the monitor arrives, the substantive work should be complete. Queries are resolved. Data entry is current. The delegation log is accurate. The investigator's calendar is blocked. Now the focus shifts to logistics and staging -- the physical and organizational preparation that ensures the visit runs smoothly.

This is the phase where you are thinking like a host, not just a coordinator. The monitor will spend hours -- possibly a full day or more -- working at your site. The efficiency of their review depends significantly on how well you have organized the materials they need to access.

Workspace logistics

The monitor needs a quiet, private workspace with power outlets, internet access (or at least guest Wi-Fi credentials), and enough surface area to spread out participant charts, the regulatory binder, and a laptop. This sounds basic, but I have seen monitors working in hallways, cafeterias, and the corner of a busy nursing station. Each of those arrangements slows the review, increases the risk of confidentiality breaches, and communicates a lack of institutional commitment to the trial.

Confirm the workspace reservation two days before. If your site does not have a dedicated monitoring room, reserve a conference room or office and post a sign indicating it is occupied for a research monitoring visit. Ensure the room has sufficient lighting and a door that closes. Place a copy of the site's Wi-Fi credentials and parking information in the room. These details matter more than you might expect -- a monitor who spends 30 minutes trying to connect to the network is 30 minutes behind schedule.

Source document staging

If the monitor has provided a participant list -- the specific participants whose records they plan to review -- pull those charts in advance and stage them in the monitoring workspace. If no participant list has been provided, request one (more on this in the next section). At minimum, prepare an enrollment summary that shows all active participants, their current visit status, and any notable events (deviations, withdrawals, missed visits).

Source document staging is covered in depth in the next lesson, so I will not duplicate that content here. The two-day task is the initial pull and staging, not the detailed organization of each chart. You are ensuring that the materials are physically accessible and ready to be organized.

Regulatory binder verification

Open the regulatory binder and perform a targeted review. This is not the full monthly self-audit you learned in the previous lesson -- it is a focused confirmation that the binder is current and complete for the visit. Specifically verify that:

The most recent IRB/IEC approval letter is filed. The current protocol version is present, with a signed and dated investigator signature page. The current Investigator's Brochure is filed. The delegation log reflects all current personnel with appropriate signatures. Any correspondence received since the last monitoring visit is filed chronologically.

If anything is missing, you have two days to locate and file it. That is enough time, provided you identify the gaps now.

Enrollment and visit status summary

Prepare a one-page summary of the site's current enrollment status and visit schedule. Include the number of participants screened, enrolled, active, completed, and withdrawn. Note any significant events since the last monitoring visit: new enrollments, screen failures, early terminations, protocol deviations. This summary serves two purposes: it gives the monitor an efficient starting point for their review, and it demonstrates that you have a clear picture of your own site's operations.

Team role confirmation

Confirm which team members will be available during the visit and remind them of their roles. The principal investigator knows about the calendar hold. The research nurse knows the monitor may have questions about specific participant visits. The pharmacist (if applicable) knows the monitor will review IP accountability logs. The regulatory specialist (if applicable) knows the binder may be reviewed in detail.

A brief team email or huddle two days before the visit is sufficient. It does not need to be a formal meeting. It does need to happen.

Pre-visit communication with the monitor

The preparation checklists address what you do at the site. But some of the most valuable pre-visit work happens in your communication with the monitor. This communication serves three purposes: confirming logistics, aligning expectations, and establishing the collaborative tone that makes the visit productive for both sides.

Confirming the agenda

When the monitor sends the visit confirmation, they should include -- or you should request -- a visit agenda. This typically outlines what the monitor plans to review: specific participant charts for source data verification, regulatory binder sections, IP accountability records, and any outstanding items from the previous visit's follow-up letter. Per ICH E6(R3), Section 3.11.4.5.1(a), monitoring includes "establishing and maintaining a line of communication between the sponsor and the investigator."

Review the agenda carefully. Does it reference specific participants? If so, you know which charts to stage. Does it mention outstanding follow-up items? If so, verify that those items have been addressed and the documentation is ready. Does it indicate a particular focus area -- consent forms, safety reporting, IP accountability? If so, prioritize your preparation accordingly.

If no agenda is provided, send a brief email requesting one. A reasonable request looks like this: "Thank you for confirming the visit dates. Could you share your planned agenda and the participant list for SDV so I can prepare the workspace and stage the relevant charts? I also want to flag a few items for discussion when you arrive."

Requesting the participant review list

Many monitors select specific participants for source data verification based on the monitoring plan's sampling strategy. Knowing which participants will be reviewed allows you to prepare their charts thoroughly rather than preparing every chart equally. Request this list at the two-week mark. Some monitors share it routinely; others need to be asked.

If the monitor declines to share the list in advance -- some CROs have policies against it, reasoning that sites should maintain all records equally -- accept that gracefully and prepare a representative cross-section of charts. But do ask. Most monitors appreciate the preparation efficiency it enables.

Disclosing known issues

This is where the proactive disclosure you identified on your two-week checklist becomes a communication task. Before the visit, send the monitor a brief summary of any known issues: protocol deviations that have occurred since the last visit, participant withdrawals, missed visit windows, safety events, or any corrective actions you have already implemented. Keep the communication factual and concise. For example:

"Since your last visit, we have had one protocol deviation (missed Visit 4 window for Participant 023 by three days -- deviation report filed with the IRB and data management notified) and one early termination (Participant 018 withdrew consent on 15 February -- all close-out procedures completed). Documentation for both is staged for your review."

That email takes two minutes to write. It saves 20 minutes of awkward discovery during the visit. And it communicates something that no amount of documentation alone can convey: this site is aware of its own operations.

When time is limited: triage by monitoring plan priorities

Not every visit arrives with a comfortable two-week runway. Monitors reschedule. Study timelines compress. Emergencies absorb the preparation time you had planned. There will be occasions when you have five business days -- or fewer -- between the visit confirmation and the monitor's arrival.

This is where your knowledge of the monitoring plan becomes a strategic asset rather than merely background reading. In Module 1, you learned how monitoring plans define what monitors prioritize: the critical-to-quality factors, the sampling strategy for SDV, the specific processes and data points classified as high-risk. That knowledge is not academic. It is your triage guide when preparation time is scarce.

Step 1: Identify what the monitor will definitely review

Start with the non-negotiable items. The monitor will almost certainly review the regulatory binder (especially the delegation log and IRB approval), verify informed consent documentation for the participants selected for SDV, and check data entry currency. These areas receive attention at every visit, regardless of the monitoring plan's specific priorities.

Step 2: Identify the high-risk focus areas from the monitoring plan

What does this trial's monitoring plan flag as high-criticality? In an oncology trial, it might be safety reporting timelines and dose modification documentation. In a device trial, it might be adverse event documentation and procedure logs. In a trial approaching an interim analysis, it might be primary endpoint data completeness. Focus your limited preparation time on these areas.

Step 3: Accept imperfection and communicate transparently

If you cannot prepare everything, communicate that to the monitor before the visit. A coordinator who says, "I had limited preparation time and focused on queries, consent documentation, and the delegation log -- the source document staging for charts 015 through 022 is not yet complete, but I will have those ready by mid-morning on the first day" demonstrates professionalism and self-awareness. A coordinator who says nothing and hopes the monitor does not notice the gaps demonstrates wishful thinking.

The monitor would rather know your constraints in advance than discover them during the visit. Transparency about limitations is not weakness. It is a sign of operational maturity.

Key takeaways

The two-week and two-day checklists transform general monitoring readiness into specific visit preparation. They are structured, sequential, and purpose-driven -- the two-week checklist addresses substantive gaps (queries, data entry, personnel documentation, regulatory currency) while the two-day checklist handles logistical staging (workspace, charts, binder verification, team coordination). Together, they ensure that when the monitor arrives, both the content and the context are ready.

But the most powerful preparation tool is not a checklist at all. It is communication. The coordinator who contacts the monitor before the visit -- confirming the agenda, requesting the participant list, disclosing known issues -- enters the visit as a partner in the quality review, not its subject. That distinction shapes the entire dynamic of the visit, the tone of the monitoring report, and the long-term relationship between site and sponsor.

And when time is limited, as it inevitably will be, the monitoring plan provides the triage logic. You cannot prepare everything in five days. But you can prepare the right things -- the critical-to-quality factors, the high-risk processes, the areas the monitor is specifically tasked with evaluating. That targeted preparation, combined with transparent communication about what remains incomplete, is more effective than a frantic attempt to do everything and a hope that the gaps go unnoticed.

The coordinator who has internalized these principles does not dread the monitoring visit confirmation email. That email is not a summons. It is the starting signal for a process the coordinator already knows how to execute.

The email that starts the clock

The email arrives on a Wednesday morning. The monitor confirms the next on-site visit: two weeks from Monday. If you have been maintaining the weekly and monthly readiness routines covered in the previous lesson, this email should produce a mild, professional alertness -- not panic. The ongoing routines have kept your data entry current, your queries resolved, your delegation log accurate, and your regulatory binder filed. The foundation is solid.

But the foundation is not the whole house. There are preparation activities that cannot -- and should not -- be done on a rolling basis because they are visit-specific. The monitor will review a particular set of participants. The investigator needs to be available at particular times. The workspace needs to be configured for an outside visitor who will spend hours reviewing documents. These are not ongoing maintenance tasks. They are targeted preparations that begin when the visit date is confirmed.

What follows is a two-phase preparation sequence: a two-week checklist that addresses the substantive gaps, and a two-day checklist that handles the logistical final staging. Together, they transform the general readiness you have maintained into specific readiness for this particular visit. I have watched this approach work at sites ranging from single-investigator community practices to 40-bed academic research units. The activities scale, but the structure holds.

And here is the part that matters most: this sequence assumes you have been maintaining your ongoing routines. If you have not, you will spend most of the two-week window catching up on what should have been done continuously -- and you will still arrive at the visit less prepared than the coordinator who maintained the routines and spent those same two weeks on targeted preparation. The previous lesson was not a suggestion. It was a prerequisite.

The two-week checklist: closing the substantive gaps

Two weeks is not a long time, but it is enough to address every preparation task that requires substantive work -- resolving data queries, completing overdue entries, coordinating investigator schedules, and verifying that the regulatory infrastructure is current. The two-week mark is when you shift from maintenance mode to preparation mode.

I organize the two-week checklist into five domains. Each one targets a specific area that monitors routinely assess, and each maps directly to monitoring activities described in ICH E6(R3), Section 3.11.4.5.

Query resolution: clearing the backlog

If you have maintained weekly query reviews, your open query count should be manageable -- perhaps a handful of queries from the past week. If not, this is where the pain begins. Monitors evaluate query resolution timelines as a direct indicator of site responsiveness, and per Section 3.11.4.5.4(b), monitoring includes "checking the accuracy, completeness and consistency of the reported trial data" and whether data "were reported in a timely manner."

Open your EDC query inbox and sort by age, oldest first. Every query that can be resolved with information available at the site should be resolved within this two-week window. Queries requiring investigator review should be flagged and routed immediately -- do not wait until next week. Queries requiring external information (laboratory results, outside records) should be escalated to the relevant department with a clear deadline.

The goal is zero open queries at the time of the visit. That is ambitious, and it is not always achievable -- some queries depend on external parties beyond your control. But the monitor should see at most a few recently issued queries, not a trail of items that have been sitting for weeks.

Data entry completion: closing the lag

Review the EDC for any participant visits that have occurred but are not yet entered. The two-week window gives you enough time to complete even a moderate data entry backlog, but only if you start immediately. Per ICH E6(R3), Section 2.12.5, investigators must ensure "the accuracy, completeness, legibility and timeliness of the data reported to the sponsor."

There is a subtlety here that experienced coordinators understand: partial data entry is often worse than no entry at all. A partially completed eCRF page may look like a finished entry with missing data, rather than an entry in progress. Complete every form you start. If you cannot finish a particular form because source documents are missing, note why and plan to resolve it before the visit.

Investigator availability: schedule coordination

Contact the principal investigator and confirm their availability during the monitoring visit. This seems obvious, but it is one of the most common logistical failures at research sites. The monitor will need the investigator's time for at least two things: discussing any significant findings and, in many protocols, reviewing and signing the monitoring visit log or confirmation form.

Block time on the investigator's calendar -- typically 30 to 60 minutes at the end of the first day or the beginning of the second. If the investigator has an unavoidable conflict on the scheduled visit days, communicate this to the monitor immediately. Most monitors can adjust their schedule if given advance notice. What they cannot accommodate is discovering on arrival that the investigator is in surgery all day.

Delegation log and personnel currency

Even if you have been reviewing the delegation log weekly, the two-week mark is the time for a final, careful verification. Check every person currently listed against actual site operations. Has anyone left the team? Has anyone's role changed? Has any new staff member started performing trial-related duties?

Per ICH E6(R3), Section 3.11.4.5.2(c), monitoring includes "confirming that the investigator is maintaining the essential records." The delegation log is among the most frequently reviewed essential records, and an outdated entry -- a person listed who no longer works at the site, or a person performing activities who is not listed -- is a finding that experienced monitors catch quickly.

Essential document expiration scan

Check all dated documents for expiration status. This is distinct from the monthly currency check covered in the previous lesson -- here, you are specifically confirming that no document will expire between now and the monitoring visit. The critical items:

IRB/IEC approval: When does the current approval period end? If it expires within the next 30 days, verify that the continuing review submission has been made or is in progress.

Medical licenses for all delegated staff: Are all current? Some state medical boards issue renewals that take weeks to process. An expired license for the principal investigator is a serious finding.

Laboratory certifications (CLIA, CAP, or equivalent): If the site uses a local laboratory for protocol-specified tests, confirm the certification is current.

GCP training certificates: Some sponsors require annual GCP training. If any delegated staff member's training has lapsed, address it now.

Proactive disclosure: the conversation that changes everything

The sixth item on the two-week checklist deserves its own discussion, because it represents a mindset shift that separates competent coordinators from exceptional ones.

Every site has issues. A participant missed a visit window by two days. A laboratory sample was hemolyzed and had to be redrawn. A protocol deviation occurred during a weekend visit when the usual coordinator was off duty. These things happen in clinical research. They are not ideal, but they are not evidence of a failing site. What distinguishes a strong site is not the absence of problems but the transparency with which problems are communicated.

When you know the monitor will discover an issue during the visit, you have a choice. You can wait and let the monitor find it -- which guarantees the issue will appear as a "discovery" in the monitoring report, framed as something the site had not addressed. Or you can disclose it proactively before the visit, with documentation of what happened, what you did about it, and what you changed to prevent recurrence.

The second approach is always better. Always. Proactive disclosure signals that the site is self-monitoring, that the quality management system is working, and that the coordinator understands the difference between hiding problems and managing them. Per ICH E6(R3), Section 3.11.1, quality assurance should include "implementing risk-based strategies to identify potential or actual causes of serious noncompliance with the protocol, GCP and/or applicable regulatory requirements to enable their corrective and preventive actions." Proactive disclosure is evidence that your site has such processes.

In my experience, monitors respond to proactive disclosure with respect, not criticism. A coordinator who says, "Before you start, I want to flag two deviations that occurred since your last visit -- here is the documentation and the corrective actions we took" has just transformed a potential finding into a demonstration of competence.

The two-day checklist: final staging

Two days before the monitor arrives, the substantive work should be complete. Queries are resolved. Data entry is current. The delegation log is accurate. The investigator's calendar is blocked. Now the focus shifts to logistics and staging -- the physical and organizational preparation that ensures the visit runs smoothly.

This is the phase where you are thinking like a host, not just a coordinator. The monitor will spend hours -- possibly a full day or more -- working at your site. The efficiency of their review depends significantly on how well you have organized the materials they need to access.

Workspace logistics

The monitor needs a quiet, private workspace with power outlets, internet access (or at least guest Wi-Fi credentials), and enough surface area to spread out participant charts, the regulatory binder, and a laptop. This sounds basic, but I have seen monitors working in hallways, cafeterias, and the corner of a busy nursing station. Each of those arrangements slows the review, increases the risk of confidentiality breaches, and communicates a lack of institutional commitment to the trial.

Confirm the workspace reservation two days before. If your site does not have a dedicated monitoring room, reserve a conference room or office and post a sign indicating it is occupied for a research monitoring visit. Ensure the room has sufficient lighting and a door that closes. Place a copy of the site's Wi-Fi credentials and parking information in the room. These details matter more than you might expect -- a monitor who spends 30 minutes trying to connect to the network is 30 minutes behind schedule.

Source document staging

If the monitor has provided a participant list -- the specific participants whose records they plan to review -- pull those charts in advance and stage them in the monitoring workspace. If no participant list has been provided, request one (more on this in the next section). At minimum, prepare an enrollment summary that shows all active participants, their current visit status, and any notable events (deviations, withdrawals, missed visits).

Source document staging is covered in depth in the next lesson, so I will not duplicate that content here. The two-day task is the initial pull and staging, not the detailed organization of each chart. You are ensuring that the materials are physically accessible and ready to be organized.

Regulatory binder verification

Open the regulatory binder and perform a targeted review. This is not the full monthly self-audit you learned in the previous lesson -- it is a focused confirmation that the binder is current and complete for the visit. Specifically verify that:

The most recent IRB/IEC approval letter is filed. The current protocol version is present, with a signed and dated investigator signature page. The current Investigator's Brochure is filed. The delegation log reflects all current personnel with appropriate signatures. Any correspondence received since the last monitoring visit is filed chronologically.

If anything is missing, you have two days to locate and file it. That is enough time, provided you identify the gaps now.

Enrollment and visit status summary

Prepare a one-page summary of the site's current enrollment status and visit schedule. Include the number of participants screened, enrolled, active, completed, and withdrawn. Note any significant events since the last monitoring visit: new enrollments, screen failures, early terminations, protocol deviations. This summary serves two purposes: it gives the monitor an efficient starting point for their review, and it demonstrates that you have a clear picture of your own site's operations.

Team role confirmation

Confirm which team members will be available during the visit and remind them of their roles. The principal investigator knows about the calendar hold. The research nurse knows the monitor may have questions about specific participant visits. The pharmacist (if applicable) knows the monitor will review IP accountability logs. The regulatory specialist (if applicable) knows the binder may be reviewed in detail.

A brief team email or huddle two days before the visit is sufficient. It does not need to be a formal meeting. It does need to happen.

Pre-visit communication with the monitor

The preparation checklists address what you do at the site. But some of the most valuable pre-visit work happens in your communication with the monitor. This communication serves three purposes: confirming logistics, aligning expectations, and establishing the collaborative tone that makes the visit productive for both sides.

Confirming the agenda

When the monitor sends the visit confirmation, they should include -- or you should request -- a visit agenda. This typically outlines what the monitor plans to review: specific participant charts for source data verification, regulatory binder sections, IP accountability records, and any outstanding items from the previous visit's follow-up letter. Per ICH E6(R3), Section 3.11.4.5.1(a), monitoring includes "establishing and maintaining a line of communication between the sponsor and the investigator."

Review the agenda carefully. Does it reference specific participants? If so, you know which charts to stage. Does it mention outstanding follow-up items? If so, verify that those items have been addressed and the documentation is ready. Does it indicate a particular focus area -- consent forms, safety reporting, IP accountability? If so, prioritize your preparation accordingly.

If no agenda is provided, send a brief email requesting one. A reasonable request looks like this: "Thank you for confirming the visit dates. Could you share your planned agenda and the participant list for SDV so I can prepare the workspace and stage the relevant charts? I also want to flag a few items for discussion when you arrive."

Requesting the participant review list

Many monitors select specific participants for source data verification based on the monitoring plan's sampling strategy. Knowing which participants will be reviewed allows you to prepare their charts thoroughly rather than preparing every chart equally. Request this list at the two-week mark. Some monitors share it routinely; others need to be asked.

If the monitor declines to share the list in advance -- some CROs have policies against it, reasoning that sites should maintain all records equally -- accept that gracefully and prepare a representative cross-section of charts. But do ask. Most monitors appreciate the preparation efficiency it enables.

Disclosing known issues

This is where the proactive disclosure you identified on your two-week checklist becomes a communication task. Before the visit, send the monitor a brief summary of any known issues: protocol deviations that have occurred since the last visit, participant withdrawals, missed visit windows, safety events, or any corrective actions you have already implemented. Keep the communication factual and concise. For example:

"Since your last visit, we have had one protocol deviation (missed Visit 4 window for Participant 023 by three days -- deviation report filed with the IRB and data management notified) and one early termination (Participant 018 withdrew consent on 15 February -- all close-out procedures completed). Documentation for both is staged for your review."

That email takes two minutes to write. It saves 20 minutes of awkward discovery during the visit. And it communicates something that no amount of documentation alone can convey: this site is aware of its own operations.

When time is limited: triage by monitoring plan priorities

Not every visit arrives with a comfortable two-week runway. Monitors reschedule. Study timelines compress. Emergencies absorb the preparation time you had planned. There will be occasions when you have five business days -- or fewer -- between the visit confirmation and the monitor's arrival.

This is where your knowledge of the monitoring plan becomes a strategic asset rather than merely background reading. In Module 1, you learned how monitoring plans define what monitors prioritize: the critical-to-quality factors, the sampling strategy for SDV, the specific processes and data points classified as high-risk. That knowledge is not academic. It is your triage guide when preparation time is scarce.

Step 1: Identify what the monitor will definitely review

Start with the non-negotiable items. The monitor will almost certainly review the regulatory binder (especially the delegation log and IRB approval), verify informed consent documentation for the participants selected for SDV, and check data entry currency. These areas receive attention at every visit, regardless of the monitoring plan's specific priorities.

Step 2: Identify the high-risk focus areas from the monitoring plan

What does this trial's monitoring plan flag as high-criticality? In an oncology trial, it might be safety reporting timelines and dose modification documentation. In a device trial, it might be adverse event documentation and procedure logs. In a trial approaching an interim analysis, it might be primary endpoint data completeness. Focus your limited preparation time on these areas.

Step 3: Accept imperfection and communicate transparently

If you cannot prepare everything, communicate that to the monitor before the visit. A coordinator who says, "I had limited preparation time and focused on queries, consent documentation, and the delegation log -- the source document staging for charts 015 through 022 is not yet complete, but I will have those ready by mid-morning on the first day" demonstrates professionalism and self-awareness. A coordinator who says nothing and hopes the monitor does not notice the gaps demonstrates wishful thinking.

The monitor would rather know your constraints in advance than discover them during the visit. Transparency about limitations is not weakness. It is a sign of operational maturity.

Key takeaways

The two-week and two-day checklists transform general monitoring readiness into specific visit preparation. They are structured, sequential, and purpose-driven -- the two-week checklist addresses substantive gaps (queries, data entry, personnel documentation, regulatory currency) while the two-day checklist handles logistical staging (workspace, charts, binder verification, team coordination). Together, they ensure that when the monitor arrives, both the content and the context are ready.

But the most powerful preparation tool is not a checklist at all. It is communication. The coordinator who contacts the monitor before the visit -- confirming the agenda, requesting the participant list, disclosing known issues -- enters the visit as a partner in the quality review, not its subject. That distinction shapes the entire dynamic of the visit, the tone of the monitoring report, and the long-term relationship between site and sponsor.

And when time is limited, as it inevitably will be, the monitoring plan provides the triage logic. You cannot prepare everything in five days. But you can prepare the right things -- the critical-to-quality factors, the high-risk processes, the areas the monitor is specifically tasked with evaluating. That targeted preparation, combined with transparent communication about what remains incomplete, is more effective than a frantic attempt to do everything and a hope that the gaps go unnoticed.

The coordinator who has internalized these principles does not dread the monitoring visit confirmation email. That email is not a summons. It is the starting signal for a process the coordinator already knows how to execute.