Skip to content

THE FREE SOP TOOLKIT

Good work.
Without the guesswork.

Give your team a process they can follow without coming back to you at every step. Turn the way you work into clear, usable standard operating procedures.

Download the SOP guide Browse all downloads

Free SOP templates, guide & worked example · No sign-up

WHEN THE PROCESS LIVES IN YOUR HEAD
“Where do I start?” “Who approves this?” “Have I missed anything?”
WITH A CLEAR SOP

“I’ve got this.”

  • The steps to follow
  • What to do when it’s different
  • How to know it’s done
Your knowledge. In your team’s hands.

THE FREE TOOLKIT

One process. A clear place to start.

Start with the guide, capture one recurring task in the template, then test it with someone who does the work. The example shows what a finished SOP can look like.

01
START HERE · THE GUIDE

SOP Creation Guideline

Learn what to capture, how to write it, and how to check that someone else can use it.

Download guide PDFDownload Word guide
Read the key points6 points
01

Define one observable result.

Continue when someone can point to evidence that proves or disproves the outcome. Write it before the steps.

02

Observe the work—not the memory of it.

Watch real cases, inspect records, and mark facts, conflicts, gaps, and assumptions separately.

03

Narrow context around each critical step.

Keep the trigger, role, exact location, evidence, decision, control, and output. Remove what cannot change execution.

04

Simplify before documenting.

Map the path and question every action that cannot change the result, proof, control, or handoff.

05

Write away operational guessing.

Use exact verbs, objects, locations, thresholds, branches, controls, and completion records.

06

Prove it with an uncoached user.

Observe a representative user, fix critical defects, retest, then publish one controlled version.

02
PUT IT INTO PRACTICE

Blank SOP Templates

Capture the steps, decisions and handoffs for one recurring task.

Download Word templateDownload Markdown template
Read the key points4 points
01

Complete the frame before the procedure.

Purpose, scope, trigger, roles, tools, and entry conditions keep the steps inside one clear boundary.

02

Build a context pack for the difficult parts.

Use it where a decision, hazard, approval, exception, control, or handoff changes execution.

03

Write the path and its failure behaviour together.

Each critical step gets an action, expected result, decision or control, escalation, and retained evidence.

04

Do not fill “Approved” before the test.

A representative user must expose missing explanations, choices, access, tools, and unsafe actions first.

03
ILLUSTRATIVE SOP EXAMPLE

Facilitate an Automation Opportunity Workshop

See how a workshop can be structured as an SOP. This is not the AITOC workshop or facilitator playbook.

Download example PDF
Read the key points6 points
01

Business outcomes come before automation ideas.

The decision owner, desired results, and constraints are fixed before tools or solutions enter the room.

02

Inventory real work before choosing a winner.

Every candidate needs a trigger, output, owner, systems, volume, friction, and failure pattern.

03

The same six lenses make opportunities comparable.

Revenue, cost, feasibility, speed, safety, and scale reveal different reasons an idea may matter.

04

Facts, estimates, and unknowns never blend together.

Every material claim carries a source and confidence so enthusiasm cannot imitate evidence.

05

Feasibility and critical risk can override a high score.

Data, rules, interfaces, exceptions, human control, constraints, and ownership determine whether to continue.

06

The workshop ends with a bounded test—not a vague roadmap.

One or two pilots receive a hypothesis, baseline, scope, measures, owner, guardrails, and decision date.

04
OPTIONAL · FOR YOUR AI ASSISTANT

Human SOP Author

Give an agent a disciplined way to draft from process evidence.

Download author skill
Read the key points4 points
01

The agent treats sources as evidence, not truth.

It separates verified facts, assumptions, gaps, conflicts, and recommendations instead of inventing missing policy.

02

Critical steps get local context.

The agent removes unrelated material and concentrates only what can change the action, decision, control, or proof.

03

The draft includes its own review evidence.

It returns traceability, risks, open questions, a user-test plan, and approval blockers with the SOP.

04

The agent cannot declare the SOP final.

Only the authorised owner can approve it after human review and representative-user testing.

05
OPTIONAL · FOR YOUR AI ASSISTANT

Workflow & Control-Loop Designer

Use it to propose bounded automation after the human process is stable.

Download workflow skillDownload skills pack
Read the key points5 points
01

An approved SOP is not approval to automate.

Decision rules, interfaces, authority, success, failure, and ownership must also be stable and measurable.

02

Classify every step before designing the loop.

Choose automate, assist, keep human, or do not perform—and explain the boundary.

03

State lives in a system of record.

Define states, events, transition guards, owners, terminal conditions, and audit evidence outside model memory.

04

Every action is a bounded contract.

Specify permission, validation, duplicate safety, timeout, retry, verification, rollback, and audit behaviour.

05

Failure and human control are part of the design.

Add stop conditions, approval gates, observability, threat tests, shadow mode, limited rollout, and rehearsed rollback.

PORTABLE REFERENCESOP Toolkit — Quick Read ↘

THE 3-PART FILTER

Make the next step obvious.

A useful SOP answers these three questions. Try it with a colleague: anywhere they still need to ask you is a place to improve the instructions. Read how to write, test and maintain an SOP together.

01
GOAL

What should happen?

Write one observable end state.

ONE OUTCOME
02
MEASURE

How will you check?

Keep only evidence that verifies the outcome.

CHECKABLE PROOF
03
ACTIONS

What are the steps?

Include the decisions, exceptions and handoffs along the way.

CRITICAL CHAIN
THE SHORTEST WORKING RULE

Goal→Measure→Action

If an action cannot change the proof, question it. If the proof cannot verify the goal, replace it.

WORK WITH AITOC

Have a process bottleneck this toolkit cannot solve alone?

Tell us where recurring work is slowing the team down. We will review the situation and contact you if there is a sensible next step.

Tell us where work is stuck Reviewed by a person. If we do not see a sensible next step, we will say so.
THE USEFUL STARTING POINT
  1. 01
    The bottleneck

    Where recurring work, delay, or rework is accumulating.

  2. 02
    The operating context

    The people, systems, and handoffs currently involved.

  3. 03
    The result that matters

    What should become faster, safer, clearer, or less expensive.

    A useful next step
    Workflow Fit Call
    A focused conversation

    Choose a time to talk.

    Talk through your priorities, the work involved and whether AITOC is the right partner.

    • Start with your business and goals
    • Clarify the process, people and systems involved
    • Agree a useful next step together
    What to expect

    Choose an available time in the calendar. The conversation helps us understand what you need before recommending a next step.

    If the calendar does not appear, you can open it in a new tab.Open calendar in a new tab
    AITOC.ioFree AI Opportunity Assessment

    What would you like to change?

    Choose the direction that feels closest. We can refine it together.