Documenting Consent and Re-consenting

Part of Clinical Research Coordinator (CRC) Training: Informed Consent.

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

Why this matters

Consent findings are among the most common and most serious at inspection, and almost all of them are documentation failures rather than ethical ones. The discussion was fine. The record of it was not.

This lesson is about making the record match what actually happened.

The signed form is not the whole record

The form proves that a signature exists. It does not prove that a proper process happened. Your source notes must show that.

A consent note should record:

Two or three sentences in the notes, written the same day, are enough. Written a week later from memory, they are worth much less.

The signature check

Before the form is filed, check every one of these. Missing entries cannot be added later by anyone other than the person they belong to.

Never sign or date on a participant's behalf, and never ask them to sign a form dated to a different day. Both are falsification.

The order of events

The single most consequential rule in consent documentation: the consent date and time must precede the first study-specific procedure.

This is checked directly. A monitor compares the consent date with the date of the first study blood test or assessment. If a screening test was performed the morning before the form was signed that afternoon, it is a deviation, and it is not fixable by rewriting anything.

Where the protocol permits use of a test done as part of routine care, that is different and should be documented as such.

Re-consent

Re-consent is required whenever the basis on which the person agreed has changed. Common triggers:

The sequence is always the same:

  1. Ethics committee approves the new version.
  2. Site staff are trained on the change, and that training is recorded.
  3. Every superseded copy is removed from circulation the same day.
  4. Enrolled participants are re-consented on the new version, before the changed activity applies to them.
  5. Each re-consent is documented like an original consent.

Track it. A simple table with each participant's row and a column per consent version shows instantly who is outstanding. This is where sites lose control: a version is approved, and three months later nobody can say which participants were re-consented.

What a coordinator does when something is wrong

If a consent problem is discovered:

In practice

Vantis Pharma amends VT-201 to add a liver function test at each visit. Consent form version 4.0 is approved on 12 May.

Nadia trains the team on 13 May, removes every version 3.0 copy from the clinic that morning, and starts using 4.0 the same day. She builds a re-consent tracker listing all 25 enrolled participants.

Twenty-three are re-consented at their next scheduled visit, before any liver test is taken. Two are not due for another two months. Nadia flags their records so the extra test cannot be drawn first, and calls them to explain the change rather than surprising them at the visit.

One participant, when re-consented, declines the extra blood test but wants to continue. Nadia does not decide what happens. She documents the refusal, and Dr. Osei discusses it with the sponsor's medical monitor, who confirms in writing what the protocol permits.

At the next monitoring visit, Marcus asks for the re-consent status of all participants. Nadia hands him the tracker.

A consent process you cannot evidence is, to an inspector, a consent process that did not happen.

Key takeaways