IRB Offices Still Negotiate Reliance in Email

Single IRB policy shrank committees, not your inbox

NIH’s domestic multi-site policy is designed to stop redundant full-board reviews. The policy landing page is the fastest authoritative summary of scope and expectations: NIH single IRB policy. The originating notice is still cited in arguments about timing: NOT-OD-16-094. Follow-on guidance clarifies exceptions and documentation habits: NOT-OD-20-058.

Operational reality is email. Reliance agreements, local context questions, and revised consent language still move as forwards between offices that do not share one ticketing system. OHRP’s FAQ hub is where administrators look for plain-language anchors: OHRP FAQs.

The coordination failure mode

The mistake after sIRB is assuming fewer committees means fewer decisions. It often means more concentrated negotiation in the compliance inbox.

You need a dated trail: who ceded review, what local protections still apply, and which template actually governs the consent document attached to the activation letter.

Thread-native structure without a new system of record

via.email gives specialist agents as email addresses. Forward the packet; get structured outputs; keep humans on sends and signatures.

Distill to Three produces a leadership brief before you forward a chain to counsel. Email distill.to.three@via.email.

Extract Action Items separates obligations by owner and deadline across institutions. Email extract.action.items@via.email.

Prep Meeting Brief synthesizes a long thread into a meeting-ready narrative with open questions. Email prep.meeting.brief@via.email.

Build Compliance Evidence converts vague checklist language into artifact prompts your sites can actually produce. Email build.compliance.evidence@via.email.

via.email does not access IRB software. It does not send on your behalf. It does not remember unrelated threads.

Next step

Take one stuck reliance thread. Run Extract Action Items and compare the table to your SMART IRB checklist. Mismatch means the thread was incomplete—fix that before you argue about PDF page numbers.

Related reading

Research operations stay mail-first. See Grant Exceptions Still Route Through Email First, Clinical Coordinators: Your Thread Is the Compliance Record, and Peer Review Still Lives in Email, Not the Workflow Tab. Browse agents at https://www.via.email/agents.

When two institutions mean different things by the same template

Reliance threads fail for boring reasons. One site uses a consent template version from 2019 because nobody updated the shared drive. Another site assumes SMART IRB covers local recruitment materials that still need translation review.

The fix is not more optimism. It is explicit mismatch hunting: forward the chain to Extract Action Items, then sit with your reliance specialist and mark every row as confirmed, wrong, or missing.

If you want a calmer steering committee readout, add Prep Meeting Brief on the same thread after you paste your institution-specific constraints into the email body. The model cannot invent local policies you do not supply.

Red flags worth stopping the line for

If you cannot name the reviewing IRB, the ceding IRB, and the document version attached to activation, you are not ready to argue about start-up timelines. That sounds obvious until you are in week six of a thread that somehow never states the obvious.

via.email still will not access NIH Reporter, CTMS, or IRB software for you. Treat anything requiring a system lookup as human work. Use agents to compress narrative, not to replace institutional records.