Key takeaways
- The checker uses twelve visible criteria scored clear, partial or missing; there is no hidden model judgment.
- A missing trigger, finish condition, accountable owner or exception path is a hard gap even when the total score is high.
- A high score means ready for a dry run, not approved, compliant or safe for automation.
- Inputs stay in your browser and the action report can be copied without an account.
Check the current SOP
Mark what the current process documentation says—not what an experienced operator remembers. Clear = explicit and testable; partial = implied or inconsistent; missing = absent.
Result · 12/24 · 50%
Rewrite the operating boundary
Boundary
3/6
Ownership
2/4
Execution
3/6
Control
2/4
Maintenance
2/4
Next improvements
- Purpose and scope: Add one outcome sentence plus explicit in-scope and out-of-scope cases.
- Trigger: Name the event, schedule or state change that starts the procedure.
- Finish condition: Name the record, status or receipt that proves completion.
- Accountable owner: Name one accountable role rather than a team or inbox.
- Decision authority: For every approval or deviation, name the role with authority to refuse.
- Inputs and sources: Replace document names with exact fields, formats and systems of record.
How the completeness score works
Each clear answer receives two points, partial receives one and missing receives zero. The total is divided by 24. Below 60% means rewrite the operating boundary; 60–84% means targeted clarification; 85% or more is ready for a dry run—unless a hard gap is missing.
The hard gaps are trigger, finish condition, accountable owner and exception paths. The override is intentional. A procedure with beautiful version control and detailed normal steps still cannot run consistently when nobody can tell when to start, when to stop, who decides or where failure goes.
| Result | Meaning | Next action |
|---|---|---|
| Rewrite the boundary | Too much execution still depends on memory. | Interview an operator and capture start, finish, sources and failure paths. |
| Targeted clarification | The path exists but named fields remain implied or inconsistent. | Fix the listed gaps and run a fresh case. |
| Ready for a dry run | The document is explicit enough to test with another qualified operator. | Run normal and failure cases; revise every verbal clarification. |
Answer from the document, not from experience
- Clear: the field is explicit, unambiguous and testable in the current effective version.
- Partial: it is implied, spread across documents, inconsistent or still needs local knowledge.
- Missing: the current document supplies no dependable answer.
If the process owner can explain a gap aloud, the answer remains missing or partial. The purpose is to expose information that disappears when that person is absent. Use the copied report as the agenda for a working session, then repeat the check against the revised version.
What to do after the score
- 01Repair hard gaps firstStart with trigger, finish, owner and exceptions; prose polish cannot compensate for a broken boundary.
- 02Test with a new operatorUse a normal case plus missing, duplicate and rejected inputs. Record assumptions.
- 03Update and version the SOPTurn every verbal clarification into a controlled change with an effective version.
- 04Map it only after the dry runUse the Workflow Mapper to identify owners, inputs, outputs and safe destinations step by step.
Limitations and when not to use this
- The tool checks declared structure, not whether instructions are correct, efficient, lawful or safe.
- Scores are an educational heuristic designed for comparison within one team; they are not certification or evidence of conformity with a standard.
- The browser does not submit answers to all-agents. Even so, describe fields and roles rather than entering confidential records.
Sources
- Guidelines for Quality Management: Standard Operating Procedures — Food and Agriculture Organization of the United Nations Accessed 1 August 2026
- ISO 9001:2015 — Quality management systems — International Organization for Standardization Accessed 1 August 2026
Translate the procedure
Turn the checked document into trigger, state, rule and exception fields.
Translate the procedureUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.