That empty space will generate a finding. The finding will require a corrective action. The corrective action will involve contacting the person who conducted the consent, asking them to provide the date (which they almost certainly do not remember six weeks later), and documenting why the date was not captured at the time of signing. A note-to-file will be written. The sponsor's quality team will review it. And somewhere in a tracking database, this site will accumulate one more mark against its compliance record.

All of this -- the finding, the corrective action, the note-to-file, the reputational cost -- because someone did not write a date.

I raise this not to alarm you, but to establish a principle that governs this entire lesson: the consent form is not merely a communication tool. It is a legal document, a regulatory record, and an auditable artifact. Every element on the signature page exists for a reason, and every omission creates consequences that extend far beyond the page itself. In my experience, the technical requirements of consent documentation are among the most straightforward elements of clinical research -- and among the most frequently violated. The errors are rarely complicated. They are careless. And they are preventable.

This lesson addresses the form itself: what must appear on it, when each element must be captured, and what happens when the requirements are not met. We are not revisiting the consent conversation -- Modules 2 through 4 covered that thoroughly. And we are not yet discussing the documentation that should accompany the form, such as source notes and process checklists -- that is the work of Lesson 2. Here, we focus on the executed consent form as a legal instrument, with the precision that instrument demands.

That empty space will generate a finding. The finding will require a corrective action. The corrective action will involve contacting the person who conducted the consent, asking them to provide the date (which they almost certainly do not remember six weeks later), and documenting why the date was not captured at the time of signing. A note-to-file will be written. The sponsor's quality team will review it. And somewhere in a tracking database, this site will accumulate one more mark against its compliance record.

All of this -- the finding, the corrective action, the note-to-file, the reputational cost -- because someone did not write a date.

I raise this not to alarm you, but to establish a principle that governs this entire lesson: the consent form is not merely a communication tool. It is a legal document, a regulatory record, and an auditable artifact. Every element on the signature page exists for a reason, and every omission creates consequences that extend far beyond the page itself. In my experience, the technical requirements of consent documentation are among the most straightforward elements of clinical research -- and among the most frequently violated. The errors are rarely complicated. They are careless. And they are preventable.

This lesson addresses the form itself: what must appear on it, when each element must be captured, and what happens when the requirements are not met. We are not revisiting the consent conversation -- Modules 2 through 4 covered that thoroughly. And we are not yet discussing the documentation that should accompany the form, such as source notes and process checklists -- that is the work of Lesson 2. Here, we focus on the executed consent form as a legal instrument, with the precision that instrument demands.