Capture a process as a reviewed SOP

SOPs & process documentation · Document & knowledge preparation · checked 2026-10-18

Turn an authorized walkthrough and existing instructions into a source-linked SOP, then have the process owner test the draft against a real example before approval.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

A versioned SOP with inputs, steps, exceptions, owner and acceptance checks.

Steps

  1. Owner

    Collect approved instructions and a walkthrough of the current process.

    Human stepConfirmed
  2. Assistant

    Draft steps and identify gaps without inventing missing actions.

    AI platformConfirmed
  3. Process owner

    Walk through the draft, resolve exceptions and approve a version.

    Human stepConfirmed

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

Human approval

A responsible person checks the source evidence and approves the output before it is used or shared.

Watch out for

Observed shortcuts must not silently become approved instructions.

Starter prompt

Draft a source-linked SOP with inputs, steps, decisions, exceptions and completion checks. Flag every gap; do not invent actions or permissions.

Written for this workflow. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
NotionHuman step notion.com ↗
ClaudeAI platform claude.ai ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
OpenAI Codex Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Google Antigravity Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
ChatGPT Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Gemini Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Perplexity Confirmed No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.

Readiness considers the connection evidence and unresolved steps. Confirmed: documented access and the proposed steps meet the recorded requirements. MCP and API pairings require an explicit reviewed platform note; a named plugin or CLI alone does not confirm MCP. Inferred: an explicit page note describes a plausible pairing that still needs testing. To verify: a connection or step is unresolved. An API and code execution alone do not establish compatible network access, credentials or permissions. None of this is IonBin testing.

Capture what is actually known

Choose one bounded process and name the person who can approve its instructions. Gather the current references and an authorized walkthrough. Record the inputs, expected output, required access and examples of successful completion. Separate observed behavior from approved policy and mark disagreements for the owner; documenting a process does not authorize redesigning it.

Draft for a reader

Ask an assistant to organize the evidence into steps, decision points and exceptions. Every substantive instruction should have a source or an explicit owner decision. Include what to do when information is missing or a system is unavailable. Do not embed passwords, personal records or broad standing authority in an SOP intended for an assistant.

Test before acceptance

Have the owner or intended operator follow the draft using an appropriate sample. Record where the instructions are unclear, what evidence proves completion and which actions require approval. Revise and repeat the affected steps. Keep the accepted version, its owner, review date and change history together. If agent instructions are derived from the SOP, preserve the same permission boundaries and test them separately. A readable SOP is a document deliverable, not proof that an automation has been built or deployed.

Sources

Related workflows

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.