The regulatory close-out checklist: what the IRB needs, what the sponsor needs, what the institution needs
Designs a comprehensive close-out checklist mapping three-stakeholder requirements (IRB, sponsor, institution), analyzes sequencing dependencies, and evaluates the consequences of incomplete close-out including phantom continuing review obligations and audit findings.
The study that would not die
Every experienced RC has at least one. A study that ended — enrollment complete, last participant visit done, database locked, final monitoring visit conducted — but that continued to appear on the IRB's active study list six months later. Then nine months. Then a full year. And each renewal cycle, the continuing review notice arrived in the RC's tracking system, demanding attention for a study that no longer existed in any operational sense.
The RC filed the continuing review anyway, because the alternative was worse: letting the approval lapse, which would create a formal regulatory lapse on a study that was supposed to be closed, which would then require an explanation to the sponsor about why a closed study had a compliance finding. So the RC spent 90 minutes assembling a continuing review package for a study with no active participants, no open queries, no ongoing activities — a phantom obligation generated entirely by an incomplete close-out process.
I have seen this pattern at sites large and small. And the root cause is always the same: someone treated study closure as a single event rather than a coordinated process with three stakeholders, each requiring specific notifications in a specific sequence. The investigator sent the final report to the IRB but did not confirm close-out with the sponsor. Or the sponsor received the site's close-out documentation but the institution's research office was never notified. Or — and this is the one that generates the phantom continuing reviews — the IRB received a final report but never received a formal study termination notification, so the study remained "active with final report pending review" in their system indefinitely.
This lesson addresses close-out as what it actually is: a portfolio-level coordination challenge requiring the RC to manage three separate stakeholder close-out processes simultaneously, with sequencing dependencies that determine whether the close-out completes cleanly or generates months of residual regulatory burden.
What you will learn
By the end of this lesson, you will be able to: