AITOC FREE SOP CREATION TOOLKIT

Goal.
Measure.
Action.

The shortest useful way to understand any SOP or agent skill. Know the outcome, the proof, and the actions that can change it.

Read the conclusion first.Open the detail when the answer is unclear.

Download the SOP guide See the 3-part method

WORKFLOW MAPOne node selected

STEP 04 · QUICK CONCLUSION

Validate one automation candidate

FOCUS×12

01 · GOAL

Make the candidate ready for a priority decision.The team can compare its value, feasibility, risk, and confidence.

02 · MEASURE

Baseline sourced · feasibility tested · red flags visible.Evidence confidence, owner, and next decision are recorded.

03 · ACTIONS

Collect → challenge → test → classify → record.These actions turn an attractive idea into a comparable candidate.

See the seven details behind this conclusion +

TriggerCandidate passes first screen

RoleAITOC lead + process owner

LocationRegister + source records

EvidenceVolume · time · errors · cost · rules

DecisionEnough evidence to prioritize?

ControlSeparate fact · estimate · unknown

OutputCandidate record + confidence

01Align outcomes

02Inventory work

03Screen candidates

04Validate evidence

05Prioritize & pilot

Start with the three conclusions. Open the seven local details only when you need to understand or change the execution.

OPERATING SYSTEM→WORKFLOW→PROCESS→STEP→DECISION→EVIDENCE

THE 3-PART FILTER

Three questions. One useful summary.

Use this before reading or writing a long SOP. It tells you whether the document is pointed at an outcome—or only describing activity.

GOAL

What must be true?

Write one observable end state.

ONE OUTCOME

MEASURE

What proves it?

Keep only evidence that verifies the outcome.

CHECKABLE PROOF

ACTIONS

What can change the proof?

Keep the decisions, controls, and behaviours that move it.

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.

THE TOOLKIT, EXTRACTED

Learn the lesson before opening the file.

Each resource teaches a different job. Read the conclusions first; open the source when you need the method, form, example, or agent instructions.

CORE GUIDE

SOP Creation Guideline

Use it to design the operating method before filling the template.

6 conclusions +

Define one observable result.

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

Observe the work—not the memory of it.

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

Narrow context around each critical step.

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

Simplify before documenting.

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

Write away operational guessing.

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

Prove it with an uncoached user.

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

SOP Creation Guideline ↘SOP Creation Guideline ↘

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.

6 conclusions +

Business outcomes come before automation ideas.

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

Inventory real work before choosing a winner.

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

The same six lenses make opportunities comparable.

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

Facts, estimates, and unknowns never blend together.

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

Feasibility and critical risk can override a high score.

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

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.

Example SOP: Automation Opportunity Workshop ↘

AUTHORING TEMPLATE

Blank SOP Templates

Use them after the outcome, process, and evidence are understood.

4 conclusions +

Complete the frame before the procedure.

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

Build a context pack for the difficult parts.

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

Write the path and its failure behaviour together.

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

Do not fill “Approved” before the test.

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

Blank SOP Template ↘Blank SOP Template ↘

AGENT SKILL

Human SOP Author

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

4 conclusions +

The agent treats sources as evidence, not truth.

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

Critical steps get local context.

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

The draft includes its own review evidence.

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

The agent cannot declare the SOP final.

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

Human SOP Author Skill ↘

AGENT SKILL

Workflow & Control-Loop Designer

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

5 conclusions +

An approved SOP is not approval to automate.

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

Classify every step before designing the loop.

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

State lives in a system of record.

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

Every action is a bounded contract.

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

Failure and human control are part of the design.

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

Automated Workflow & Loop Designer Skill ↘Agent SOP Skills Pack ↘

PORTABLE REFERENCESOP Toolkit — Quick Read↘

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 stuckReviewed by a person. If we do not see a sensible next step, we will say so.

THE USEFUL STARTING POINT

01
The bottleneck
Where recurring work, delay, or rework is accumulating.
02
The operating context
The people, systems, and handoffs currently involved.
03
The result that matters
What should become faster, safer, clearer, or less expensive.

Goal.Measure.Action.