SOP Documentation AI workflow template: An SOP a new hire can follow.

The ConvOps SOP Documentation template makes your AI write a standard operating procedure from how the process really runs: capture the steps and the tribal knowledge, draft numbered steps for a first-timer, then walk the draft through as if running it. You approve before it is published, and a rejection returns to Draft SOP.

4 steps · 1 approval · 1 loop back

SOP Documentation · example runyour AI client
  1. 01Capture Process
  2. 02Draft SOP
  3. 03Walkthroughwaits for approval
  4. 04Publishclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the SOP Documentation template do?

For operations teams who need repeatable processes written down: onboarding, refunds, releases, anything that lives in someone's head.

SOP Documentation is stored in ConvOps as four steps, and your AI client receives them one at a time. A SOP Documentation run holds at Walkthrough until an explicit approval is given.

  • Document a customer onboarding process as a step-by-step SOP
  • Write a standard operating procedure for handling refunds
  • Turn a release process into a procedure a new hire can follow
step by step

How does the SOP Documentation workflow run?

The 4 SOP Documentation steps in order, each with the instruction your AI receives there as SOP Documentation stores it.

Capture Process
Draft SOP
Walkthroughapproval
Publishclosing note

A published SOP with a purpose, a trigger, prerequisites, numbered steps, edge cases and a definition of done, walked through before approval.

  1. 01

    Capture Process

    the agent works

    Capture how the process actually runs before writing it up.

    Record:

    • The process name and its purpose: what outcome it produces
    • Who runs it and when it is triggered
    • The steps in order, as they really happen: including the small ones people do from memory
    • Tools, systems, or access needed at each step
    • Common pitfalls or edge cases and how they are handled

    Probe for the tribal knowledge: the "oh, and you also have to" steps that never make it into documentation. If a step is unclear, ask the operator rather than guessing.

    Save the captured process as a task note with task_notes_add. The next step (Draft SOP) reads this note.

  2. 02

    Draft SOP

    the agent works

    Read the task notes with task_notes_list: the note from the Capture Process step contains the steps and the tribal knowledge. Work from it.

    Write the SOP. What good looks like:

    • A title, purpose, and the trigger that starts the process
    • Prerequisites: access, tools, inputs needed before starting
    • Numbered steps in order, each one concrete action a person can do without guessing
    • Edge cases and what to do when they occur
    • The definition of done: how to know the process completed correctly

    Write for someone doing this for the first time. No assumed knowledge.

    Save the full SOP draft as a task note with task_notes_add. If it exceeds 10,000 characters, split across notes or store where the operator keeps documents and record the location. The Walkthrough step reads this note.

  3. 03

    Walkthrough

    waits for your approval

    Read the task notes with task_notes_list: the Draft SOP note holds the procedure and the Capture Process note holds the original steps to check against. Work from them.

    Walk the SOP step by step as if running the process for the first time:

    • Every step is actionable with no missing prerequisite
    • The order is correct and nothing is skipped
    • Edge cases are covered
    • A new person could follow it without asking for help

    Note any gap and fix the draft before sign-off.

    Ask the operator to approve the SOP for publishing. This is a checkpoint: once published the team relies on it, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft SOP.

    rejected → back to Draft SOP

  4. 04

    Publish

    closes with a note

    Read the task notes with task_notes_list: the Walkthrough note holds the approved procedure. Work from it.

    Publish the SOP where the team keeps its documentation: the wiki, doc, or shared space they actually use. Save the published SOP as a task note with task_notes_add so the record stays on file, then close out the task.

reach for it when

  • A process lives in one person's head, and that person is busy or leaving.
  • New people keep asking the same questions about how something is done.
  • The written version must survive a first-timer following it step by step.

something else fits when

  • The agent should run the procedure, not document it: turn the SOP into its own workflow.
  • The process changes weekly, so a document would be stale on publish.
  • What is needed is a policy statement, not steps.
example · airline ground operationsenterprise

Handling a delayed baggage claim

The agent asks two senior agents how they handle a claim, captures the steps they do from memory, drafts the SOP for a first-week hire and walks it through. The station manager sends it back once for a missing escalation step.

Walkthrough approval

where approval is required

Where do you approve in SOP Documentation?

SOP Documentation holds at Walkthrough until an explicit approval is given, recorded with the account that gave it.

step 3

Walkthrough

Once published, the team relies on it. The AI walks every step as a first-timer, checks order, prerequisites and edge cases against the captured process, and you approve or send it back to Draft SOP.

what you review

  • Every step is actionable with no missing prerequisite
  • The order is correct and nothing is skipped
  • Edge cases are covered
  • A new person could follow it without asking for help

reject → back to Draft SOP

gates the engine checks without you

  • Publish closes SOP Documentation only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run SOP Documentation?

make it yours

How do you customize SOP Documentation?

Once installed, SOP Documentation is a workflow in your workspace. Ask your AI to change SOP Documentation in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Draft SOP, add a troubleshooting table at the end.
workflow_step_update · SOP Documentation
Done. SOP Documentation in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Draft SOP, add a troubleshooting table at the end."
  • "In Publish, save the SOP to our Notion operations space."
  • "Add a step that schedules a review of this SOP in six months."
the difference

SOP Documentation: without a workflow vs with it

  • The process lives only in one person's head and breaks the day they are out
  • The SOP gets written but skips the one tribal-knowledge step that actually matters
  • You capture half the steps, get pulled away, and lose the detail you had in mind
  • Nobody knows when the SOP was last validated or what changed since the previous version
  • The SOP Documentation process lives in a prompt, and each run follows it a little differently
  • The AI drives the process into a written SOP anyone on the team can follow
  • The AI pauses at a walkthrough checkpoint so you confirm the steps are complete and correct before publishing
  • The AI saves the captured process and the draft as notes, so a later session resumes the SOP intact
  • Every step (Capture, Draft, Walkthrough, Publish) is logged, so the SOP's provenance is already there
  • Your AI receives the 4 stored steps one at a time, and the run holds at Walkthrough until an explicit approval is given
questions

SOP Documentation template FAQ

What is the ConvOps SOP Documentation template?

The ConvOps SOP Documentation template makes your AI write a standard operating procedure from how the process really runs: capture the steps and the tribal knowledge, draft numbered steps for a first-timer, then walk the draft through as if running it. You approve before it is published, and a rejection returns to Draft SOP.

How does it capture tribal knowledge?

The ConvOps Capture Process step tells your AI to record the steps as they really happen, including the small ones people do from memory, and to probe for the "oh, and you also have to" steps that never reach documentation. It also records who runs the process, what triggers it, the tools needed and common pitfalls, and asks you rather than guessing.

What makes a good SOP in this template?

The ConvOps Draft SOP step asks for a title, purpose and trigger, prerequisites (access, tools, inputs), numbered steps that are each one concrete action a person can do without guessing, edge cases and what to do when they occur, and a definition of done. It is written for someone doing the process for the first time, with no assumed knowledge.

What if the SOP is long?

Each ConvOps step saves its output as a task note with task_notes_add. When the SOP draft exceeds 10,000 characters, the instruction says to split it across notes or store it where you keep documents and record the location in the note. Either way, Walkthrough and Publish read the same record, so nothing depends on the chat history.

What happens at the Walkthrough?

The ConvOps Walkthrough step walks the SOP step by step as if running the process for the first time, checking every step is actionable with no missing prerequisite, the order is right, edge cases are covered and a new person could follow it unaided. The run holds there until an explicit approval is given. Reject it and the run returns to Draft SOP.