GuidesFor CRCs & regulatory staff
How IRB Continuing Review Lapses Actually Happen
Jun 17, 2026GuideRegulatory Deadline TrackerAdministrative reference · Zero-PHI examples only
IRBcontinuing reviewdeadlinestrainingZero-PHI
The “forgot it was due” failure mode for IRB renewals, training, and delegation — and how Regulatory Deadline Tracker surfaces the same urgency bands sites already use for kits.
The problem on the clinic floor
Continuing review rarely fails because a site decided to ignore the IRB. It fails because the due date lived in an approval letter PDF, a calendar invite from last year, or a regulatory binder tab that is not part of Monday huddle. Clinic volume wins. The lapse shows up as an email from the IRB or a CRA question that starts with “when was continuing review last approved?”
Training and delegation renewals rhyme with the same pattern. GCP certificates and CV currency expire on individual schedules; delegation log updates wait until “someone has time.” Each item has a quiet due date. Together they form a compliance pile that only becomes loud when something is already late.
Email reminders help until filters, shared inboxes, and staff turnover bury them. A spreadsheet helps until it is not opened. The common ingredient is lack of an urgency view that looks like the kit closet board people already understand.
Multi-study sites multiply the dates. Study A’s continuing review, Study B’s amendment response, and three staff GCP renewals land in different folders. Without one active list sorted by urgency, the item due in nine days waits behind the item due in ninety — until both are suddenly due.
Completed renewals that never get marked done clutter the mental model. People remember “we submitted continuing review” but forget to update the tracker, so the next huddle still shows a red band for something already in flight. Stale active rows erode trust in the board itself.
Practice context
IRB continuing review, staff training/certification currency, and delegation renewals are administrative controls sites are expected to maintain. Lapses can pause enrollment, trigger CAPA, or become monitoring findings even when subject safety was never in doubt.
Tracking these dates does not require PHI. Protocol IDs, staff role labels, and due dates are enough. Keep subject names and MRNs out of the deadline list entirely.
Regulatory folders and eIRB portals remain the systems of record for approvals. The deadline tracker is the site’s urgency layer — it tells the team what needs action this week, not what the IRB stored after approval.
Internal QA and sponsor audits increasingly ask for evidence that someone reviewed regulatory currency on a schedule. A printed or exported deadline log with completion dates supports that narrative without exposing subject data.
How to use Regulatory Deadline Tracker for this
Mirror kit-style urgency for regulatory dates so “due in 12 days” is as visible as an expiring lot. Add continuing review, training, and delegation items to the same weekly pass coordinators already use for mango windows — one board, one huddle rhythm.
- Open Regulatory Deadline Tracker and add IRB continuing review, training/certification, and delegation renewal items with due dates and short administrative labels — no subject identifiers. Use protocol IDs and role labels (“PI GCP,” “Sub-I delegation”) instead of personal health information.
- Review Active items by urgency bands (on track, ≤60d, ≤30d, ≤7d / due today, past due) during the same weekly pass you use for kit mango windows. Start with past due and ≤7d; those are the items that can pause work.
- Mark items complete when renewals land so history stays available without cluttering the active urgency list. Note submission date versus approval date if your SOP distinguishes them — keep the active row accurate to what is still pending.
- Export audit CSV or print a binder-ready deadline log before monitoring or internal QA. Include the export date so reviewers see a contemporaneous snapshot.
- Backup the workspace with Export Session Backup (.json); clear shared browsers when finished. Pair the tracker with your regulatory binder — the tracker drives action; the binder holds signed approvals.
Most continuing-review lapses are calendar failures, not ethics failures. Put the due date on a board that gets opened on purpose. When regulatory urgency looks like kit urgency, fewer dates die quietly in PDF footers.