Local and institutional IRB submissions: navigating committee-specific requirements and reviewer expectations
Teaches the RC to manage local IRB submission strategy at portfolio scale, including meeting cycle navigation, deadline calculation, batching and sequencing decisions, and reviewer dynamics across concurrent studies before the same committee.
The meeting that happens once a month
Central IRBs operate on rolling review timelines. Submit on Monday, and the review begins that week. Local institutional IRBs operate on meeting cycles. Submit on Monday, and the review happens at the next convened meeting -- which may be three weeks away. And if you missed the submission deadline for that meeting, the review happens at the meeting after that, which is seven weeks away.
This difference in temporal architecture changes everything about how the RC plans submissions. With a central IRB, the submission timeline is largely under the RC's control: prepare the package, submit it, wait for the review. With a local IRB, the submission timeline is dictated by the committee's calendar: meeting dates, submission deadlines calculated backward from those dates, agenda capacity limits, and the human dynamics of committee members who review multiple studies in a single sitting.
For the RC managing a portfolio that includes local IRB studies, the challenge multiplies. It is not just one study navigating one meeting cycle. It is four studies, all reviewed by the same committee, all subject to the same submission deadlines, all competing for the same agenda space and the same reviewers' attention. The RC who does not think strategically about local IRB submission -- about batching, sequencing, and committee dynamics -- will find that the committee calendar, not the science or the regulatory requirements, becomes the rate-limiting factor in the site's activation and amendment timelines.
What you will learn
By the end of this lesson, you will be able to: