How to Use the IRB Amendment Cover Letter Prompt so Reviewers Find Every Material Edit
Turn an IRB amendment packet into a clear cover letter and tracked change summary: what changed, why, risk impact, consent form updates, enrollment status, and reviewer navigation notes so the board can find every edit without hunting the full protocol.
IRB reviewers should not hunt through a hundred page protocol to find three material edits. They want a cover letter, a tracked change summary, and a consent story that matches enrollment reality. The IRB Protocol Amendment Cover Letter and Tracked Change Summary Planner: Risk, Consent, Enrollment, and Reviewer Navigation Notes prompt builds that packet: cover letter, change table with risk and consent impact, reconsent tree, reviewer navigation, and a filing checklist.
What the prompt produces
- A one page cover letter with protocol identity and purpose.
- A tracked change summary table with risk, consent, and enrollment columns.
- A risk narrative marked for PI confirmation.
- A reconsent decision tree for not yet enrolled versus currently enrolled participants.
- Reviewer navigation notes to tracked and clean files.
- A participant communication draft when people must be informed.
- A filing checklist matched to your packet preferences.
- Likely IRB questions without inventing institutional policy answers.
How to fill the inputs
ProtocolIdentity needs title, IRB number, PI, and amendment label.
ChangeList should list old versus new gists. Long text can be summarized if you keep the meaning.
EnrollmentStatus decides reconsent. Open enrollment with people already on study is different from not started.
RiskDraft is a draft for PI confirmation, not a final determination.
ConsentAndRecruitment names every form and flyer touched.
PacketPrefs tells the prompt whether you file tracked PDFs, clean copies, or both.
Reading the example output
The sample extends CGM wear, adds optional saliva cortisol, clarifies a shift work exclusion, and adds a lobby flyer.
- Reconsent is required before extending wear for people still in window.
- Irritation rates are left as PI confirm, not invented.
- Navigation tells reviewers where highlights live.
Tips for better results
- Number every change ID and keep it stable across revisions.
- Separate optional procedures clearly in consent.
- Ask HRPP about local continuing review wording instead of guessing.
Mistakes to avoid
- Do not invent approval language or meeting dates.
- Do not hide recruitment material changes outside the summary table.
- Do not treat this as legal advice or stamped regulatory opinion.
Who it is for
Study coordinators, regulatory writers, and PIs assembling amendment packets.
Related PromptDig links
Open the IRB Protocol Amendment Cover Letter and Tracked Change Summary Planner: Risk, Consent, Enrollment, and Reviewer Navigation Notes prompt with your change list and enrollment status. For more research prompts, Browse more prompts. If your summary table shortened IRB questions, Share a prompt.
Coordinating with the PI
Send the risk narrative and reconsent tree to the PI before you file. Mark every [PI confirm] in yellow. File only after those confirmations land in email or your eReg system.
When enrollment is open, coordinator calendars should block time for reconsent visits before day eleven of an extended procedure. A beautiful cover letter does not help if participants pass the window.
Stipulation response habits
If the IRB asks for irritation rates, pull them from the safety database. Do not let a chatbot invent percentages. Update the tracked change summary if you alter procedures again in response to stipulations so the board always sees one living table.
Clean versus tracked files
Always file both when PacketPrefs allow it. Reviewers skim the summary table, spot check tracked highlights, then read clean consent as participants will see it. If you only file clean protocol, the board spends the meeting diffing by eye.
Name files with amendment number and version so email threads stay searchable: IRB-24-118-AMD3-tracked-protocol.pdf and consent-v4-clean.pdf beat final_final_v7.pdf.
Version control habits
Keep a simple changelog in the study shared drive: amendment number, date filed, change IDs included, and IRB decision date when you receive it. When a sponsor asks what changed between Amendment 2 and 3, you should answer from the summary table, not from memory.