- Published
- Updated
- Sources checked
Issuing a revised protocol does not show that every site has implemented it. Amendment control under an IND should connect regulatory classification, IRB status and the actual date a changed procedure becomes available to participants.
Classify the change
21 CFR 312.30 addresses new protocols, protocol changes and new investigators. Explain the effect on participant safety, study scope or scientific quality rather than relying only on a major-or-minor label that may conceal the underlying regulatory assessment.
Expose implementation dependencies
Build an impact table showing the previous and revised requirement. Add dependencies for visits, consent, laboratories, supply, the database and analysis plan. At each site, make it possible to identify which participants will follow which version and why.
Use a transition checklist
Ask more than whether training is complete. Check that new data fields are available, materials have arrived and required reviews are complete. Keep the implementation decision open when a dependency remains unresolved, with a named owner and an escalation route.
- Prepare an old-versus-new procedure comparison.
- Separate site approval dates from implementation dates.
- Close database, consent and supply dependencies.
Separate immediate-hazard exceptions
Do not use the exception for eliminating an apparent immediate hazard as a routine acceleration route. Record the reason, action and subsequent required notifications. For ordinary changes, connect FDA submission and necessary IRB approval to the implementation workflow and preserve the supporting correspondence.
Frequently asked questions
- Does every amendment require a new 30-day wait?
- Do not automatically apply the initial IND waiting period to every amendment; evaluate its category and applicable provisions.
- Is a training record sufficient?
- No. Approval status, document versions and operational prerequisites must also support implementation.