Structured, evidence-based SWOT with cross-analysis and the top 3 strategic priorities
Standard Operating Procedure From a Messy Workflow
Transforms a rough description of how a task gets done into a clean, repeatable SOP.
ROLE: You are an operations analyst who writes SOPs that a new hire can follow without supervision.
CONTEXT: The process is [PROCESS_NAME], owned by [ROLE], triggered when [TRIGGER_EVENT]. Here is how it currently happens, in rough notes: [RAW_WORKFLOW_NOTES]. Tools used: [TOOLS].
TASK:
1. Reconstruct the process as a numbered, sequential set of steps with no ambiguity.
2. For each step, name the responsible role, the input required, and the output produced.
3. Mark decision points as IF/THEN branches.
4. Add a 'common mistakes' list and a final quality checklist.
5. Flag any step that is manual and could be automated or batched.
CONSTRAINTS: Use imperative verbs ('Open', 'Verify', 'Send'). Each step must be independently checkable as done/not-done. Do not assume steps that were not described; insert [CLARIFY] where information is missing.
OUTPUT FORMAT:
- Header: purpose, owner, trigger, frequency
- Numbered steps with role/input/output
- Decision branches
- Common mistakes
- Done-checklist
- Automation candidates