When should a research site write a note to file?

When something in the study record needs explaining, such as a late entry, a missing document or a one-off process change, so a monitor or inspector can follow what happened.

Is a note to file the same as a deviation report?

No. A deviation report documents a departure from the protocol and is reported as required. A note to file explains the record. A deviation may need both.

Who should sign a note to file?

The author signs and dates it. Many sites also have the investigator review and sign, depending on the SOP.

Free template

Note to file template

A free note to file template for research sites. Use it to document an issue, why it happened and what was done about it, so the study record shows what happened.

Email (optional, for template updates)

No sign-up needed to download.

Why sites keep one.

A note to file explains something in the record that would otherwise be unclear: a missing signature, a late entry, a process change.

A note to file does not fix a problem by itself. Pair it with a corrective action, and report deviations as the protocol and IRB require.

Tips

Write it as soon as the issue is found, and date it the day it is written.
Be specific and factual. Avoid blame.
File it with the record it explains and reference it in your deviation log if applicable.

What goes in each column

Study / protocol number: Protocol number and short title
Site: Site name and number
Participant ID: If the note concerns one participant
Subject of note: One line, e.g. Late entry of Week 4 vitals
Description: What happened and when
Root cause: Why it happened
Corrective and preventive action: What was done and what will change
Author name and role: Who wrote the note
Author signature and date: Signed and dated by the author
Investigator signature and date: PI review, if required by your SOP

When this record is needed

Use a note to file according to the protocol, sponsor requirements and your site procedures. ICH E6(R3) describes investigator oversight and essential records; 21 CFR 312.62 addresses applicable investigator records and retention. Neither source mandates this exact downloadable layout for every study.

Agree on the record’s owner, update frequency and filing location before using the template. A form should help reconstruct what happened, not create a parallel tracker with conflicting information. Keep original supporting records and use the approved study convention for identifiers and dates.

Filled example, not real study data

A sample note explains that a Week 4 entry was documented late. It identifies the actual procedure date, the date of the note, what evidence was reviewed and the corrective action. The author signs on the real writing date; the note is not backdated or used to conceal the late entry.

The example is deliberately limited. Do not put live identifiers into a public download preview or email request. Adapt the field explanations with your study team, then check that an independent reviewer can identify the responsible person, event, date and supporting evidence without an oral explanation.

Filled example, not real study data
Sample issue	Actual event	Note date	Action
Late Week 4 entry	24-Oct-2026	27-Oct-2026	Document evidence and review process

Review risks before monitoring

Common review risks include missing dates, unclear task or criterion references, signatures that cannot be tied to a person, and entries that contradict the source record. These are practical checks, not a claim about the frequency of findings in an inspection dataset. Review one row against its supporting evidence before treating the log as ready.

Do not overwrite an earlier entry to make the file look current. Record changes using your site’s correction procedure and retain the earlier information. A late explanation does not erase the original issue or change whether a deviation must be reported. Confirm reporting requirements with the protocol, sponsor and IRB.

How Kyros Trials handles the related work

Use the regulated-record change or deviation workflow for the underlying issue, with a reason and retained history. A note explains context; it does not replace a required correction, deviation report, consent record or investigator review.

The template remains a free planning and record-format aid. Electronic workflows add record context and access controls, but your team still owns intended-use review, training, investigator oversight and retention. Inspect the corresponding workflow in a demo and compare it with your site’s procedure before switching from paper.

Questions people ask.

Answers to the questions research sites ask most.

Still have questions? Book a demo

Keep these logs in Kyros Trials instead.

Walk through your visit schedule, source records and sponsor billing with our team.

Book a 20-minute demo