Fill in these first
- Task name: [for example monthly vendor payment run, new employee document collection]
- Who does it now and how often: [role and frequency]
- How it is done today: [describe the steps in your own words, even if messy]
- Tools and systems used: [software, forms, shared folders]
- Known mistakes or risks: [what has gone wrong before]
- Country and state or region: [jurisdiction, if the task has a legal or tax element]
Task
Write a standard operating procedure that a new team member could follow correctly on their first attempt. If the task involves tax, data protection, employment or other legal requirements, ask for the jurisdiction if it is missing and add a note that the SOP is general guidance, not legal advice.
Output format
- Header: SOP title, version 1.0, owner role, effective date placeholder, review date.
- Purpose: two sentences.
- Scope: what the SOP covers and what it does not.
- Roles table with columns: Role, Responsibility.
- Before you start: inputs, access and documents needed.
- Procedure: numbered steps. Each step starts with a verb and names the role doing it. Add a "Check" line after any step where an error would be costly.
- Exceptions: what to do when something does not match, and who to escalate to.
- Records: what to save, where, and for how long, marked [confirm retention period] where law may set it.
- Revision history table: Version, Date, Change, Approved by.
Rules
- One action per step; split compound steps.
- Use role titles, never personal names.
- Never include passwords, account numbers or access codes; refer to where they are stored instead.
- Keep the procedure under 25 steps; split into sub-procedures if longer.






