SOPs: AI agent SOPs that run as steps, not wiki pages.

An AI agent SOP, or agent operating procedure, is a standard operating procedure written as workflow steps the agent executes one at a time, with gates where an approval is required. ConvOps turns the SOP your team keeps in a wiki into a process the engine holds, so every run follows it and edits reach the next run.

claude · codex · cursor · any ai client · one step at a time · approvals recorded at the gate

example · Claude Codeconnected
Onboard the new vendor using our SOP.
task created · SOP workflow attached
Step 1 of 5: collect the vendor details. The rest comes one step at a time.
approval · waiting for you
Checks are done. The SOP says a manager approves before the vendor is created.
Approved.
complete · every SOP step recorded
ConvOps · task · exampleVendor onboarding SOP
task

Vendor onboarding · example

step 1 of 5
collect check why approve approvaldone
in short

What is an SOP for AI agents?

A standard operating procedure written as steps an AI agent runs one at a time. In ConvOps the engine holds the steps, the gates and the record.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

key facts · october 2026

  • The engine serves the current step only, so there is no later step to jump to.
  • A gate holds the step until an explicit approval is given, recorded with the account that gave it.
  • A step can stay open until the reason for its decision is recorded.
  • If an approval names an on_rejected step, a rejection sends the run there. Without one, the rejection is refused.
  • Edit a step once and every run that starts afterwards follows the new version.
  • Agents can propose metrics for an SOP. They stay drafts until approved.

best for

  • Teams with procedures that repeat every week
  • Processes where one person's know-how needs to become the team's
  • Audited work that needs the reason for each decision on file

not for

  • Policies with no steps to follow
  • Procedures that change every week

updated

the problem

The SOP exists. Nobody runs it.

The procedure lives in a wiki. People skim it, agents never see it, and the steps drift.

“Did anyone follow it?”

The wiki says a manager approves. Nothing shows whether one did.

“Which version is current?”

Three copies of the procedure, edited by three people, in three places.

“Does the agent know?”

Paste the SOP into a prompt and the model decides which parts matter today.

watch it work

One SOP, from wiki to running.

An example procedure, turned into a workflow from Claude Code, then run on a real case.

01you, in Claude Code

Paste the procedure.

You hand the agent the wiki page. It proposes a workflow: one step per action, a gate where an approval is required, a step that must record its reasoning.

example
example · Claude Codeconnected to ConvOps
Turn our vendor onboarding SOP into a workflow. A manager approves before the vendor is created.
workflow created · 5 steps · 1 approval gate
Collect, check, record why, manager approves, create. Want to review the steps?
02the engine

The wiki becomes steps.

The same procedure, now held by the engine. The agent sees one step at a time, so it cannot jump ahead to the part it likes.

example
Vendor onboarding (wiki) · example
example · SOP · vendor onboardingworkflow
  1. Collect details
  2. Run the checks
  3. Record the reasoning
  4. Manager approveswaits for approval
  5. Create the vendor
03the AI · one step

The checks land on the task.

The agent runs the checks the SOP names and writes the findings down. The step closes only with a reason recorded.

example
example · Vendor onboarding · examplestep 3 of 5

Checks

recorded on the task

tax idformat valid
bank detailsmatch the invoice
policycontract over threshold: needs approval
reason recordedrequire_context
04the manager

The manager decides.

The run stops at the approval gate. The manager reads the findings and decides. Until it is approved, the vendor is not created.

example
waiting for approval

Approve this vendor?

Checks passed · contract over threshold · reasoning recorded

Hold itApprove
approvedStep 5 unlockedCreating the vendor was locked until now.
05the record

The record writes itself.

Every step lands in the history with its reason. Field changes on the task keep the agent label and the signed-in person apart.

example
example · ConvOps · task activityrecord
  • collectdetails captured
  • checkfindings recorded
  • approveapproval passed
  • donevendor created

agent label · implementer | person · verified from the credential

decisionContracts over threshold always need a manager.linked to this task
example
example · Claude Codeconnected to ConvOps
Turn our vendor onboarding SOP into a workflow. A manager approves before the vendor is created.
workflow created · 5 steps · 1 approval gate
Collect, check, record why, manager approves, create. Want to review the steps?
the workflow

The SOP, running.

Each step is served when the run reaches it. The approval sits where the SOP requires a sign-off.

workflow · Vendor onboarding SOPrunning · step 1 of 5
  1. 01

    Collect details

    Legal name, tax id, bank details and contact, as the SOP lists them.

  2. 02

    Run the checks

    Against the policy the SOP names. Findings recorded on the task.

  3. 03

    Record the reasoning

    The step cannot close without the reason written down.

    decision
  4. 04

    Manager approves

    An approval gate holds the run until the vendor is approved.

    needs approval
  5. 05

    Create the vendor

    Only after approval. The step history shows every stage.

what teams run it for

What teams turn into SOP workflows

Labelled examples from different kinds of procedure.

example · customer supportenterprise

Refunds with a threshold

A telecom's refund SOP checks the amount first. Refunds under the threshold go on to processing; larger ones branch to a team lead's approval gate.

Decision step and approval gate

example · qualityenterprise

ISO document review

A manufacturer's document control SOP requires a review report for each controlled document. The step waits until the report is filed, and the quality manager approves the new revision.

Required report type

example · field service

One task per site visit

Each maintenance visit is its own task running the visit SOP: safety check, inspection, parts used, sign-off. The technician's notes land on the task, step by step.

One task per visit

example · HR

Offboarding with a recorded reason

The offboarding SOP keeps the access-removal step open until the agent records which systems were closed and why any were kept. HR approves the final checklist.

Recorded reason and approval

example · IT operations

An incident runbook as child tasks

The runbook opens one child task per affected service, each with its own recovery steps. The incident stays open until every child is completed or cancelled.

Child tasks

example · finance

Expense claims against policy

Each claim runs the expense SOP: receipts checked, policy limits applied, exceptions written up. Claims over policy wait at the approval gate for the budget holder.

Policy check and approval gate

example · laboratoryenterprise

Sample intake at a pharma lab

Every incoming sample runs the intake SOP: label check, storage condition, chain-of-custody entry. There is no approval gate: the record on the task is what the auditor reads.

Ordered steps, no approval

example · procurement

Vendor onboarding, the SOP on this page

Details collected, checks run against the policy the SOP names, the reasoning recorded, then a manager approves before the vendor is created. The same steps for every buyer.

Recorded reason and approval gate

what it remembers

Why the procedure is the procedure.

The reasons behind each step, kept by the team and recalled when the next case arrives.

Decisions

Why the threshold is where it is, recorded at the step that applied it.

why we do it

Corrections

The check that caught a bad bank detail last month, so the next run looks for it.

what went wrong

Where things live

The policy, the vendor sheet and the contract folder. Found once, kept.

where it lives

Rules in context

Policies attached to a workflow reach the agent with the step they apply to.

guidance, not a gate

recurring work

Run it every week

Many SOPs run on a calendar. ConvOps starts them, groups them and measures them.

Put a recurring SOP on a schedule: a weekly safety walk, a monthly control check, a quarterly policy review. Each schedule has its own time zone, and you can preview the next five runs. Group the schedules into a program, and its verdict shows when an SOP is late, silent or failing.

Place the one-off runs on Plan, where capacity comes from four weeks of completed work and spread shows a preview before anything moves.

Define the numbers the SOP must report in Metrics, such as rework per case, and bind them at the step that produces them. An agent can propose a metric too, and it stays a draft until approved. Markers on the trend show every edit to the SOP workflow.

schedule firesweekly safety walk
checklistone step at a time
reasonreason required
managerapproval
rework per casemetric required
program verdicthealthy
the difference

Wiki SOP vs running SOP.

  • The procedure sits in a wiki page
  • The agent reads it, or does not
  • Sign-offs happen in chat, if at all
  • Each copy of the SOP drifts on its own
  • The procedure is a workflow the engine holds
  • The agent gets one step at a time
  • Approval gates hold the run until an explicit approval is given
  • One edit, and the next run follows it

Steps in order

The engine serves the current step only. Steps inside one workflow never run at the same time.

Approval is a gate

An approval gate refuses the advance until an explicit approval is given, and the response lists what is missing.

The why is a gate

require_context keeps a step open until the reason is recorded, so the decision travels with the work.

What the record covers

Step history with reasons, an activity feed, and field-level before and after on tasks and workflow instances.

next to what you use

A ConvOps workflow next to other ways to keep an SOP

The same procedure, kept four ways.

A ConvOps workflow next to a file, a prompt and a wiki page
ConvOps workflowA markdown SOP fileA prompt or skillA wiki page
Who decides the next stepThe engine, after checking the gatesThe model, after reading the fileThe model, each timeWhoever reads it
Approval gateA gate holds the step until it is approvedA line asking for oneAn instruction to askA note on the page
When the SOP changesEdit one step; the next run followsEdit every copy of the fileRe-share the promptEdit the page and hope it is read
RecordStep history with reasons and approvalsNoneThe chat historyPage history
Whether it worksMetrics on every run, with change markersUnknownUnknownUnknown
start this week

Four moves to your first run.

Connect the AI tool your team already uses, install the workflows, and run one real piece of work through them.

  1. move 1

    Pick one SOP your team repeats weekly and paste the wiki page into your AI client

  2. move 2

    Ask the agent to draft it as a workflow: one step per action, a gate where a sign-off is required

  3. move 3

    Run one real case through it and read the step history afterwards

  4. move 4

    Fix the step that was unclear once; every later run follows the new version

install these

questions

What teams ask.

What is an SOP for AI agents in ConvOps?

In ConvOps, an SOP for AI agents is a standard operating procedure stored as a workflow: ordered steps with instructions for each, and gates where an approval or a report must come first. The agent receives one step at a time, and the engine checks the gates before the run moves on. Edit a step once and every later run follows it.

How do I write an SOP an AI agent will follow?

Write one action per step, in the order it happens, and say what done looks like for each. In ConvOps, mark the hard rules with MUST and the preferences with SHOULD, so the agent knows which ones it may weigh. Put a gate where a sign-off is required and name where a rejection goes. Then run one real case and fix the unclear step.

How is a ConvOps workflow different from an SOP markdown file?

A markdown SOP is read by the model, which then decides which parts to follow. A ConvOps workflow is held by the engine: the agent receives one step at a time, the gates are checked before the run moves on, and every step leaves a record. The file describes the procedure; the workflow runs it and shows afterwards what happened.

Can ConvOps stop an agent skipping an SOP step?

Yes. ConvOps serves each step only when the run reaches it, so there is no later step to jump to. A gate holds the step until an explicit approval is given, recorded with the account that gave it, and a required report in enforce mode holds it until the report is filed. A refused advance returns what is missing, so the agent knows what comes next.

How do I know whether an SOP works?

Measure it. In ConvOps you define the metrics the SOP must report, such as rework per case, and bind them at the step that produces them, and each value carries who recorded it and at which step. ConvOps also records the cost, duration, tokens and outcome of every run by itself, and agents cannot write those. Markers on the trend show each SOP edit, so you can tell whether a change helped.

Can one SOP run every week on its own?

Yes. In ConvOps, a schedule starts a task with the SOP attached at the cadence you set, such as weekly or monthly, in its own time zone. It can spawn a new task on each fire or wake an existing one. Group the schedules into a program and its health verdict shows when a run is late, silent or failing.

What happens if the approver says no?

In ConvOps, it depends on the step's approval gate. If the step names an on_rejected target, a rejection moves the run to that step, for example back to the checks, and the step history records it. If the step has no target, the rejection is refused and the run stays at the approval, so name a target for every gate that can say no.

Can steps of an SOP run in parallel in ConvOps?

Not inside one workflow. In ConvOps, the steps of a workflow run in order, one at a time. Independent pieces of work are split into child tasks that start together, each on its own workflow, and the parent waits until all of them finish. That keeps each piece on its own record, with its own gates and its own history.