How would you investigate a consent form version mismatch found during monitoring?

Short answer

First establish the facts: which version each participant signed, which version was approved on that date and what changed between them. Then protect participants by giving them any missing information and reconsenting with the approved version, document the deviation, assess reporting duties and fix the cause.

Why

Consent must use materials the ethics committee approved before use, so a superseded or unapproved form is a deviation, but its weight depends on the content gap. If the old form lacked a new safety risk, participants decided without information they were entitled to, which is serious. If only the phone number changed, it is minor.

The investigation should check every participant at the site, not only the one the monitor saw, because version errors usually come from a process: old stock left in a clinic room, an eConsent system not updated, or a translation released late. Reconsent with the current version, documented with the date, is the usual remedy, and the participant is told what is new. The sponsor decides whether the deviation is important under its criteria, and in the EU whether it reaches the serious breach threshold of Article 52, which needs notification within 7 days of the sponsor becoming aware.

Data collected before reconsent may need review if consent itself is in doubt.

How to work it through

List every participant consented at the site with the version and date they signed.
Match each date to the version the ethics committee had approved at that time.
Compare the wording of the signed and approved versions to see what information was missing.
Arrange prompt reconsent with the approved version for anyone affected, and record it.
Classify the deviation, decide on ethics committee and regulatory reporting, and escalate to the sponsor at once if a safety risk was omitted.
Find the root cause and remove superseded forms or fix the eConsent release process.

An example

At a 40 participant site, a monitor sees participant 1012 signed version 3.0 on 14 March. Version 4.0, approved on 1 March, added a risk of liver injury. A full check finds 6 participants signed version 3.0 between 1 and 20 March because printed copies were kept in a second clinic.

The site reconsents all 6 with version 4.0 within two weeks, one participant chooses to withdraw, and the sponsor assesses whether the omission of a safety risk is a serious breach. Printed stock is destroyed and the site moves to controlled printing from the current file.

Where the answer stops holding

The right remedy depends on what differed between versions and on local ethics committee rules, which vary. Some committees require reporting of any use of an unapproved form. Where the participant has already completed the trial, reconsent may not be possible, and the decision turns to how their data may be used under the consent they gave.

A strong answer covers

Check every participant, not just the one flagged
Compare the content gap between versions
Reconsent with the approved version and document it
Classify the deviation and assess serious breach reporting
Fix the process that let an old version circulate

Common mistakes

Simply getting the participant to sign the new form without telling them what changed.
Treating the mismatch as a filing error and not checking the rest of the site.
Backdating the new signature to match the original consent date.

The interviewer might ask next

How would your actions change if the missing information was a newly identified serious risk?