Regulatory Coordinator

Full course · Regulatory Submissions & Stakeholder Management

IRB correspondence management: responding to stipulations, routing modification requests, and maintaining the regulatory narrative across submissions — Regulatory Submissions & Stakeholder Management

IRB correspondence management: responding to stipulations, routing modification requests, and maintaining the regulatory narrative across submissions

Designs an IRB correspondence management system per ICH E6(R3) Appendix C, C.2.1 and C.3.1(a), analyzes regulatory narrative continuity across submissions over time, and creates response templates and routing protocols for delegation.

24 min

The story your IRB file tells

Every study has a regulatory narrative. Not a narrative in the literary sense — there are no characters or plot twists. But there is a story, told across dozens of submissions and correspondence items over months or years, that the IRB reads every time it reviews something from your site. The initial submission introduces the study. The continuing reviews update its progress. The amendment requests propose changes with justification. The stipulation responses demonstrate that the site understands the IRB's concerns and has addressed them. The safety reports show how the site manages risk.

This narrative accumulates. An IRB reviewer processing a continuing review for a study in its fourth year does not read that application in isolation. They read it in the context of every previous submission — the language the site has used, the commitments the site has made, the stipulations the site has addressed. When the narrative is consistent — when the site's language, reasoning, and documentation quality are recognizable from submission to submission — the IRB develops confidence in the site's operations. The review goes smoothly. The approval comes quickly.

When the narrative breaks — when a response to a stipulation uses language that contradicts a previous submission, when a continuing review describes a process differently than the initial application described it, when the voice and quality of the correspondence shifts abruptly because a new staff member wrote it without reviewing the history — the IRB notices. And the IRB responds, correctly, with additional scrutiny.

Module 3, Lesson 4 introduced stipulation tracking as a portfolio-level workflow. This lesson builds the broader correspondence management layer: how to maintain the regulatory narrative for every study across every submission, how to design systems that prevent narrative discontinuity, and how to delegate correspondence to CRCs while preserving the quality and consistency that the IRB expects.

What you will learn3 objectives

By the end of this lesson, you will be able to:

Design an IRB correspondence management system that captures inbound and outbound communications, links them to specific submission events, and maintains the chronological narrative for each study, per ICH E6(R3) Appendix C, Sections C.2.1 and C.3.1(a)
Analyze the concept of regulatory narrative continuity — how consistency across submissions over time builds or erodes IRB confidence in the site's operations
Create response templates and routing protocols for common IRB correspondence scenarios that maintain quality and narrative consistency while enabling efficient delegation to CRCs

Progress saves itself — finish reading and this lesson completes

Continue with the Regulatory Coordinator track

The story your IRB file tells