The implementation cascade: mapping every operational change triggered by an amendment
Teaches RCs to build a cascade mapping framework that systematically identifies every operational domain affected by a protocol amendment, traces interdependencies between domains, and validates completeness against ICH E6(R3) Appendix B and Appendix C.
One line changed. Seven domains broke.
A Phase II neurology trial changed its primary cognitive assessment from one instrument to another. One line in the amendment summary. The regulatory coordinator at the site read the amendment, completed the impact assessment from Module 1, and identified the obvious consequence: the assessment tool at visits 3, 5, and 7 would change. Impact assessment: done.
Except it was not done. The cascade had barely started.
The new assessment required a different scoring template -- which meant the source documents needed revision. The scoring template required certified rater training -- which meant the delegation log needed updating and training records needed documenting. The new instrument had different administration time requirements -- which meant the visit schedule needed adjustment, and the participant instruction sheet that told participants to arrive 90 minutes before their appointment now needed to say 120 minutes. The pharmacy did not dispense the assessment tool, but the amendment also modified the post-assessment observation window -- which meant the coordinator holding room schedule shifted, which collided with a concurrent study's infusion schedule in the same space. And the data management team needed revised CRF fields because the new instrument produced subscale scores that the old one did not.
One amendment. Seven operational domains. Twelve specific changes. And I have not yet mentioned that three of those changes depend on each other -- the training cannot be documented until the source documents are finalized, the source documents cannot be finalized until the sponsor confirms the CRF field specifications, and the CRF specifications require the data management team to build new edit checks that reference the assessment's scoring algorithm.
This is the implementation cascade. And it is, without exaggeration, where more amendments fail than at any other stage. Not because coordinators are careless, but because the human mind is not naturally wired to think in cascades. We think in lists. We think in sequences. We do not instinctively map the seven downstream consequences of a change to a visit schedule, or notice that the fifth consequence depends on the third, which depends on a decision the sponsor has not yet made. That requires a framework.
What you will learn
By the end of this lesson, you will be able to: