
Sauna assembles IRB submissions, tracks protocol versions and approval dates, drafts amendments and continuing reviews, and keeps the regulatory binder inspection-ready so a study never lapses out of approval.
What it does
Assembles the initial or amendment submission packet — protocol, consent, supporting docs — checks each against the IRB checklist, and drafts the cover memo in Google Docs.
Holds every study's approval, expiration, and continuing-review date in Airtable and flags continuing reviews 60 days out so no study lapses out of approval.
When a protocol changes, drafts the amendment and the consent-form redline, and lists every downstream document that needs to be updated to stay consistent.
Audits the regulatory binder against the required-elements list, lists what's missing or out of date, and posts the gap list to Slack before a monitor visit.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Our oncology study's continuing review is due — assemble the submission, draft the cover memo, check the binder against the IRB checklist, and list anything missing before I send it.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. It assembles and drafts the packet and checks it against the IRB's requirements; you review and submit through the IRB portal.
No. It drafts amendments and redlines and flags downstream impacts; every change is yours to approve before it goes anywhere.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring