The amendment pipeline: tracking multiple amendments across multiple studies simultaneously

Free Lesson Preview

Continue with the Regulatory Coordinator track

View the Regulatory Coordinator track for current pricing and enrollment options.

Already enrolled? Sign in

The amendment pipeline: tracking multiple amendments across multiple studies simultaneously

A single amendment in a single study is a project. Fifteen amendments across eight studies is a pipeline -- and without a tracking system that provides cross-study visibility, the RC manages each amendment in isolation, discovering delays only when sponsors ask why submissions are late. This lesson teaches learners to design a portfolio-level amendment pipeline, define status categories with transition criteria, identify systemic bottlenecks, and evaluate pipeline health metrics that drive process improvement.

25 min

Three delays that were actually one problem

The pipeline tracker shows that Study C's Amendment 2 has been sitting at "pending IRB submission" for three weeks. The regulatory coordinator investigates and discovers the reason: the principal investigator has not signed the submission cover letter. Fair enough -- investigators are busy. But then the RC checks the rest of the pipeline. Study F's Amendment 1, also assigned to the same investigator, has been pending the PI's signature for 11 days. And Study J's Amendment 3 -- same investigator -- has been waiting nine days.

Three amendments. Three studies. Three separate delays. And every one of them is waiting for the same signature.

Without a portfolio-level view, each of these delays would have appeared to be an independent problem. The RC would have sent a reminder email about Study C's amendment, perhaps made a phone call about Study F, and eventually noticed Study J during a routine check. Three separate conversations, three separate escalation timelines, three separate explanations to three separate sponsors when they asked why submissions were late.

But the pipeline made the pattern visible. This is not three problems. It is one problem -- a principal investigator whose signature queue has backed up across the portfolio. The intervention is not three reminder emails. It is a single conversation with the investigator about the signature backlog, possibly a delegation arrangement for cover letter review, possibly a scheduled weekly signing session. The pipeline revealed a systemic bottleneck that per-amendment tracking would have obscured.

This, in my view, is the single most underappreciated capability in amendment management: the ability to see across studies, not just within them. Module 4 taught you to verify that a single amendment is fully implemented. This module teaches you to manage the entire portfolio of amendments simultaneously. And this lesson starts with the tracking system that makes that management possible.