SOPs & process documentation
Turn how your team actually works into SOPs people can follow and agents can use.
Capture a process, have AI draft the SOP, ask its owner to correct it and keep a maintained source copy. An assistant can make instructions easier to use, but it does not guarantee the process will be followed. Test the steps, permissions and exceptions with a representative task.
Most small teams have processes that live in one person’s head. The need has two parts: write the processes down, and make the written version the one people actually use.
Capture: record the owner doing the task, or talking it through on a call.
Draft: have an assistant turn the transcript into steps, inputs, outputs and a checklist.
Correct: the owner edits the draft. AI drafts; people approve.
Store: keep one page per process in a shared workspace (see the SOPs & process stack).
Put it to work: package high-use SOPs as custom assistants (see SOPs as custom assistants). Keep a versioned source and verify how updates reach each assistant. Claude’s current project sharing requires Team or Enterprise; availability of a project does not imply organization-wide sharing. The container is changing: OpenAI’s help article on GPTs (checked 2026-10-17) says it plans to retire custom GPTs in favor of Plugins: retirement is planned for Dec 11, 2026 in affected Enterprise workspaces, other plans are expected to follow, and new GPTs can no longer be created on personal accounts. Google’s Gems help page (checked 2026-10-17) says that from November 2026, Gems on personal Google accounts will move to skills.
Keep the maintained SOP in Notion or Obsidian, IonBin’s top picks for documentation. Notion can also capture the walkthrough with AI Meeting Notes, so the transcript, draft and approved page sit together; Obsidian suits SOPs kept as Markdown files under version control. Dedicated recorders such as Fireflies are a secondary capture option. Notion and Obsidian are IonBin’s editorial top picks; neither sponsored this page and IonBin has no partnership with either.
Less dependence on any one person.
Agent-ready. Written SOPs can inform an agent, provided its tools, permissions and failure handling support the actual steps.
Faster onboarding. New hires can use the page alongside supervised practice and checks.
An unapproved SOP is a guess. Require owner sign-off and a review date.
Sensitive steps. Leave credentials and personal data out of recordings and prompts.
Keep the master copy in your docs. Assistant features get renamed and retired, so the SOP page should stay the source and the assistant a copy.
Snapshot from official sources on Oct 21, 2026.
| Custom GPTs | Retirement planned December 11, 2026 for affected Enterprise workspaces; personal new creation unavailable [1] |
| Claude Projects | All users; Free up to 5. Current shared projects require Team/Enterprise; new Code project beta has separate rollout [2] |
| Gems | Personal accounts transition to skills starting November 2026 [3] |
Turn how your team actually works into SOPs people can follow and agents can use.
| Tool in this entry | How agents connect |
|---|---|
| Notion | MCPAPI/CLIFile import |
| Obsidian | API/CLIFile import |
| Claude | Agent platform MCPAPI/CLIFile import |
| ChatGPT | Agent platform API/CLIFile import |
| Fireflies.ai | MCPAPI/CLIFile import |
| Descript | MCPAPI/CLIFile import |
Levels come from each tool's recorded, sourced compatibility. How the levels work.
Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.
IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “I need our processes written down and actually followed”? Email us with a link to a primary source.
Suggest an edit by email or write to contact@ionbin.com