GP-SOP-011 | Planning and Operations
Turn Repetitive Work Into a Reusable SOP
A tested procedure that captures how work is actually completed, including exceptions and quality checks.
When to use this SOP
Use this when a task is repeated, taught verbally, completed inconsistently, or dependent on one person remembering every detail.
What you need
- A real example of the task
- The person who currently performs it
- Required inputs and finished output
- Known exceptions and risks
The procedure
Follow these steps
- 01
Observe or perform the task once without trying to improve it.
- 02
Record the trigger, inputs, systems, decisions, actions, output, and owner.
- 03
Separate required steps from habits, preferences, and historical leftovers.
- 04
Write each step as one clear action with enough context to make the decision safely.
- 05
Add quality checks at the point where mistakes can still be corrected.
- 06
Document exceptions, stop conditions, escalation paths, and rollback steps.
- 07
Have a second person follow the SOP using a real or safe test case.
- 08
Correct gaps, assign an owner, and set a review trigger or review date.
Human checkpoint
Stop and review before continuing
An SOP should preserve useful judgment, not hide it. Explain the decision rule when a step depends on context.
Definition of done
- The trigger and outcome are explicit
- Required inputs and owners are named
- Steps reflect the real process
- Checks, exceptions, and stop conditions are included
- Another person completed the task successfully
- The SOP has an owner and review trigger
When the process gets stuck
If the process changes every time, document the stable decision framework first instead of forcing it into a rigid sequence.
Where automation fits
The SOP Generator can organize verified notes into a first draft. Observe and test the real process before automating it.
Optional AI assist
Use this after you collect the real inputs
This prompt can organize a first pass. Review the result against the SOP before using it.
Turn these process notes into a draft SOP. Include: - Purpose and finished outcome - Trigger - Owner - Required inputs and tools - Numbered procedure - Decision rules - Quality checks - Exceptions and stop conditions - Recovery or escalation - Definition of done - Questions that must be answered before approval Do not invent steps or pretend uncertain notes are confirmed. Process notes: [PASTE NOTES]