The Monitoring Visit Report and Follow-Up

Part of Clinical Research Associate (CRA) Training: Monitoring Approaches and Reporting.

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

Why this matters

A visit that is not documented did not happen. The monitoring visit report is the record that goes into the trial master file and that an inspector may read years later, long after everyone involved has moved on.

It is also the mechanism by which anything actually gets fixed.

The monitoring visit report

Written using the sponsor's or CRO's template, usually within a defined period after the visit.

What it contains:

• Visit date, type, location, and whether on site, remote or hybrid.
• Who was present, from the site and from the sponsor or CRO.
• A summary of the activities performed: which participants were reviewed, what source data verification was done and on what basis, what product review took place, what documents were checked.
• Findings, each classified by severity.
• Action items, each with a responsible person and a target date.
• Status of actions from previous visits.
• Anything requiring sponsor or CRO follow-up.
• Recruitment, retention and data entry status.

Write it promptly. A report written three weeks later loses the detail that made the visit worth doing, and by then the site has moved on.

Writing findings that work

A finding is only useful if the site can act on it. Four rules.

Be specific. Not "consent documentation issues" but "for participant 014, the informed consent form version 3.0 was signed on 12 March; the screening blood sample was drawn on 11 March, before consent."

Anchor it to the requirement. Name the protocol section, the standard operating procedure, or the regulation. Anchoring removes almost all arguments, because the discussion stops being about opinion.

Separate the fact from the cause. State what was observed. Then, where you know it, state what caused it. "The site has no process for reviewing incoming correspondence for enrolled participants" is a different sentence from the finding it explains, and both belong in the report.

Classify honestly. Most organizations use critical, major and minor. Critical means participant safety or data integrity is affected, or a significant regulatory breach. Major means important data or compliance are affected. Minor means limited impact. Inflating a minor finding wastes everyone's time; downgrading a critical one is far worse.

Do not speculate about intent in writing. Record what you observed. If you suspect misconduct, that goes through your organization's escalation route, not into a narrative paragraph.

The follow-up letter

Sent to the investigator, and usually copied to the coordinator, within the period your procedures specify.

It reinforces:

• The visit date and type.
• The main findings, categorized.
• The actions required, each with a responsible person and a due date.
• Anything the sponsor or CRO owes the site.

It should contain no surprises. Every finding in the letter should have been discussed at the closing meeting. A letter that introduces a new finding damages trust and is usually a sign that the closing meeting was rushed.

Tracking actions to completion

This is where monitoring most often fails.

• Record every action in the sponsor's tracking system with its owner and due date.
• Chase before the due date, not after.
• Verify completion with evidence, not with an assurance. "Staff were retrained" is verified by seeing the training record.
• Carry unresolved actions into the next visit's agenda explicitly.
• Escalate actions that remain open across two visits.

An action list that grows every visit is a site heading for a serious finding, and the CRA who let it grow shares that.

Common pitfalls

Poor preparation. Time wasted on site, issues missed, review rushed. Fixed by Lesson 2 of the previous module.

Over-emphasizing source data verification and neglecting process. Verification finds errors; process review finds the cause of errors. A visit that checks numbers and never asks how a visit is scheduled or how consent is taken will keep finding the same errors.

Vague communication. The site does not understand the seriousness or urgency of a finding, so it does not act. Fixed by specificity, named owners and dates.

Not following up on previous findings. Recurring issues, and eventually a regulatory finding that the sponsor knew and did nothing.

Writing for yourself rather than for a stranger. The report's real audience is a person who was not there.

In practice

Leah's report on a VT-301 visit lists a major finding: four out-of-window visits in three months, all at the month-four visit.

Her first draft says "the site should ensure visits occur within protocol windows". She rewrites it.

The final version states the four participant numbers and dates, cites the schedule of assessments window of plus or minus three days, records that all four were the month-four visit, and adds the cause: the month-four visit requires fasting and is booked only in afternoon slots, so participants reschedule.

The action is specific: move fasting visits to the first morning appointment, add a visit-window check at the point of booking, and review upcoming windows weekly. Owner: the coordinator. Date: within three weeks.

At the next visit, Leah asks for the booking records rather than asking whether it was done. There are no further out-of-window visits.

Six months later a regulatory inspection reads the same report and finds a site that identified, explained and fixed a problem. That is a much smaller finding than four unexplained deviations.

"The site should ensure compliance" is not a finding. It is a wish.

Key takeaways

• The monitoring visit report enters the trial master file and must be written promptly, for a reader who was not there.
• A usable finding is specific, anchored to the protocol, SOP or regulation, separates fact from cause, and is classified honestly as critical, major or minor.
• The follow-up letter should contain no surprises; every finding in it should have been discussed at the closing meeting.
• Verify action completion with evidence rather than assurance, and escalate actions still open across two visits.
• Source data verification finds errors; process review finds their cause, and a visit that only verifies numbers will keep finding the same errors.