IRB and REB Protocol Amendments

Keep the research record clear

Published

Ivory-and-green illustration connects a proposed protocol revision, a reviewed decision and current research documents with earlier versions retained.

A community-mobility study proposes an extra interview with participants. The protocol, information sheet and consent wording all change. The research office receives a review decision, but one team still has the earlier interview pack. Months later, staff need to explain what was approved, when the revised pack came into use and what each participant agreed to.

Keep the amendment as a linked change within the research file. Identify the earlier approved documents, proposed revisions, review outcome and conditions for use. Then record the release and participant transition required by the responsible ethics process. A new file in the folder cannot answer those questions on its own.

Identify the decision the amendment needs

An institutional review board (IRB) or research ethics board (REB) assesses changes through the process that applies to the study. Describe what is changing for participants, why it is changing and which materials are affected. Keep the proposed wording distinguishable from the approved set while review is open.

For research subject to the relevant HHS or FDA rules, the joint IRB written-procedures guidance addresses prior review of changes, assessment of consent revisions and communication of decisions. It includes the exception for changes necessary to eliminate apparent immediate hazards to participants. Follow the applicable urgent-change and reporting procedure rather than forcing every event through a routine amendment queue.

In Canada, TCPS 2 Article 6.16 requires documented REB approval before substantive changes are implemented, apart from changes needed to eliminate immediate risks. Review reflects the ethical implications and risk of the change. The responsible ethics process determines the review route and outcome; a document-management status should reflect that decision.

Connect four parts of the amendment record

A practical record model to configure for the study and its review process.
Part of the recordWhat to connectQuestion it answers
Earlier approved setExact protocol and related document versions, decision and applicable scope.What governed the work before this change?
Amendment submissionReason, change summary, proposed documents and affected participant activities or teams.What is being requested and why?
Review outcomeQuestions, responses, reviewed versions, authoritative decision and unresolved conditions.What did the reviewer decide about this submission?
Release and useAccepted prerequisites, released document set, team readiness and required participant transition evidence.When and for whom was the revised set put into use?

Keep submission, decision and effective-use dates distinct. If the reviewer asks for revised wording, retain that request and the response. Record the later decision on the corrected documents before showing them as approved for use. Preserve the earlier submission so staff can reconstruct the review sequence.

  1. 1 · Propose

    Identify the changed activity

    Connect the earlier approved set to the proposed revisions and their reason.

  2. 2 · Decide

    Retain the authoritative outcome

    Keep review questions, corrected versions and approval conditions together.

  3. 3 · Use

    Verify the transition

    Record the released set, affected teams and participant steps required by the decision.

Worked example: adding a follow-up interview

This fictional amendment continues RES-1042 after its earlier protocol review is resolved. The researchers propose an additional follow-up interview. The local process requires an approved protocol, information sheet and consent form to be released together, with a recorded transition for participants invited to the extra interview. Those are example decision terms, not a universal consent procedure.

  1. Register the proposal against the existing study

    The administrator links the amendment to RES-1042 and the earlier approved protocol and consent set. The submission explains the extra activity and includes the proposed protocol, information sheet, consent wording and interview guide. Funding status remains a separate project fact.

  2. Retain the review and corrected wording

    The board requests a clearer account of the interview's purpose and time commitment. The administrator retains the request, response and revised documents in the same amendment history. The proposed pack remains awaiting the required decision.

  3. Record exactly what was approved

    The returned decision identifies the accepted document versions and the participant transition required before the extra activity. The research office records that decision and its scope. Any further institutional or site prerequisites remain visible until the responsible owner accepts them.

  4. Release one consistent document set

    The coordinator checks that each affected team has the approved pack and withdraws obsolete copies from that activity's current-use locations. An old consent form found at one location becomes an assigned correction. Uploading the new pack or sending a notification does not establish that the correction happened.

  5. Keep the participant history accurate

    The authorised study process records which participants were invited to the extra interview and the required consent outcome before that activity. Earlier participation remains associated with its actual approved documents. The project file connects the accepted transition evidence and unresolved exceptions without treating every participant as having used the newest form.

Preserve the documents that applied at the time

A link labelled “current consent form” helps teams find today's approved document. It cannot establish what was presented in an earlier interaction. Retain the exact document reference and applicable decision with the historical event. Where more than one authorised version applies to different activities or groups, make the scope explicit rather than choosing solely by the latest upload date.

Consent also involves the participant's ongoing choice. TCPS 2 Article 3.3 addresses maintaining consent and providing relevant new information. Let the responsible ethics decision and study procedure define communication or renewed consent for the change; do not assume every amendment requires every participant to sign a new form.

Choose where detailed participant records belong and what the project dossier needs to reference. Institutional, departmental, partner and customer-tenant boundaries can require different access. A grant administrator's view of an ethics status does not itself require access to identifiable participant documents.

The research-administration and CRIS guide covers accepted project-fact updates across systems. The document-change guide covers staff learning decisions. Keep those relationships connected to the amendment without confusing either with the ethics decision or participant consent.

Check one amendment from request to use

  • Identify the earlier approved protocol, related documents and affected activity.
  • Keep the proposal, review questions, responses and corrected versions together.
  • Record the authoritative outcome and distinguish outstanding conditions from accepted approval.
  • Confirm the released set and resolve obsolete copies in current-use locations.
  • Retain the participant transition required by the decision and the documents used at each event.
  • Keep sensitive participant evidence within its intended access boundary.

Make the amendment explain what changed in the study

A useful amendment record connects the proposed change, the responsible review, the approved documents and their actual use. Preserve the earlier history and keep unfinished transition work visible. The research office should be able to explain both the current approved position and the documents that governed earlier participation.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call