Resource allocation during amendment surges: when you cannot do everything at once
When amendment volume exceeds normal capacity, the RC must match available resources to implementation demands, identify compliance risks created by resource constraints, and build contingency plans that keep the portfolio moving without letting safety-critical items stall.
Five amendments, one month, no room to breathe
The triage framework from the previous lesson told the regulatory coordinator what to work on first. It sequenced five amendments by risk: the two safety-driven amendments at Priority 1 and 2, the three substantive amendments at Priority 3, 4, and 5. The sequencing is correct. The problem is that sequencing assumes a queue that moves. And this month, the queue is not moving fast enough.
The RC manages regulatory operations for 18 studies. A junior RC provides part-time support -- perhaps 15 hours per week dedicated to amendment-related tasks. The CRC team, which handles the operational components of amendment implementation (reconsent conversations, source document updates, training attendance), is simultaneously managing a monitoring visit surge: three different sponsors have scheduled visits within the same two-week window. The principal investigator is available for amendment review and signature approximately four hours per week, most of it concentrated on Tuesday afternoons.
Normal capacity for this site is two to three amendments per month. Five is a surge. And the surge does not care about the site's capacity.
This is where triage reaches its limit. Triage tells you what comes first. It does not tell you what is possible within the hours and hands you actually have. That gap -- between the prioritized queue and the available capacity -- is the problem this lesson solves.
What you will learn
By the end of this lesson, you will be able to: