Preparing for a Monitoring Visit

Part of Clinical Research Associate (CRA) Training: Monitoring Visits.

About 5 minutes. Free, in your language, no account needed.

Why this matters

The difference between a useful monitoring visit and a wasted day is almost entirely decided before you arrive.

An unprepared CRA spends the morning discovering what is there. A prepared one arrives with a list of specific questions and spends the day answering them.

Review the data before you go

Enrollment and participant status. How many screened, enrolled, screen-failed, withdrawn, discontinued. Who is due for upcoming visits or follow-up windows. Any participant whose status has changed since the last visit.

Data in the electronic system. Missing forms and visit pages. Incomplete or inconsistent fields. Outstanding and overdue queries. Patterns rather than instances: the same assessment missing repeatedly, the same deviation type recurring, values that look copied.

Safety data. Every adverse event and serious adverse event to date, with seriousness, severity, causality and outcome. Whether serious events were reported within the protocol's deadline, measured from the site's date of awareness. Any pattern, such as similar events in several participants at the same site.

Previous visit report and follow-up letter. Open actions, their due dates and their owners. Any prior critical or major finding that needs re-checking. Carrying unresolved actions forward without comment is the most common weakness in monitoring practice.

The monitoring plan and protocol. What this visit requires: the percentage or basis of source data verification, the risk-based focus areas, the critical data points. Any recent amendment or change to monitoring requirements.

Write down the specific questions this review produces. That list is your agenda.

Communicate with the site

Confirm the schedule. Date, start time, expected finish. Which staff need to be present and when — particularly the investigator, who is often available only in a narrow window.

Share the focus. Tell the site which participants and which records you will prioritize. "We will concentrate on participants 001, 003 and 007 because they have serious adverse events" lets the site prepare, and a prepared site is a faster visit, not a hidden one.

Request what you need in advance. Specific logs, consent forms, temperature records, laboratory reports, the deviation log.

Confirm access. Electronic medical record access, pharmacy and laboratory areas, the site file, and any remote access credentials. Access problems discovered on the day cost half a visit.

Handle logistics. Site-specific requirements such as badges, parking or sign-in; and for remote or hybrid visits, the connection details, and a tested route into whatever system you need to see.

A preparation checklist

• Visit type confirmed: initiation, interim, for-cause or close-out.
• Monitoring plan reviewed for this visit's requirements.
• Protocol and current amendments reviewed.
• Previous monitoring report and follow-up letter reviewed.
• Outstanding actions from previous visits listed.
• Data system reviewed: missing data identified, pending queries noted, safety issues flagged.
• Enrollment and participant status report prepared.
• Investigational product inventory status checked from the sponsor or pharmacy system.
• Date and time confirmed with the investigator and coordinator.
• Site understands the visit focus and which documents to prepare.
• Travel and accommodation arranged, for an on-site visit.
• Access to the medical record and site systems confirmed.
• Documents to hand: protocol and Investigator's Brochure, monitoring plan, visit worksheets, prior correspondence.

Set the scope honestly

Decide before you travel what you will and will not cover, based on the monitoring plan and on the risk signals in the data. Then tell the site.

A visit that tries to cover everything covers nothing well. A visit whose scope was never stated leaves the site feeling ambushed and leaves you unable to explain why you looked at what you looked at.

In practice

Preparing for a VT-301 visit, Leah reviews the data and finds three things.

First, four participants have visits recorded outside their windows, all at the month-four visit. Second, one participant has an adverse event with an onset date preceding their consent date. Third, the site has 31 open queries, 14 of them more than 60 days old.

None of this would have been visible on the day. Together they define the visit.

She emails the coordinator three days ahead: she will focus on the month-four visit scheduling process, on that one participant's consent and adverse event chronology, and on why queries are aging. She asks for the site's scheduling process, that participant's full file, and a list of the open queries with the reason each is unresolved.

She arrives to find the participant's chronology already explained — a transcription error in the adverse event onset date, corrected properly with a line-through — and the coordinator ready to walk her through the scheduling problem.

The visit finishes at 15:00 with three clear findings and agreed actions, instead of at 19:00 with a list of things to check next time.

Preparation is not politeness. It is what makes the visit worth the flight.

Key takeaways

• Review enrollment, data, safety and previous actions before traveling, and turn what you find into a written list of specific questions.
• Serious adverse event timeliness is measured from the site's date of awareness, so check that the awareness date is recorded before assessing the deadline.
• Carrying unresolved actions forward without comment is the most common weakness in monitoring, so the previous follow-up letter is required reading.
• Tell the site the focus in advance; a prepared site makes the visit faster, not less honest.
• Confirm system and medical record access before the visit, because access problems discovered on the day cost half a visit.