wowprompt

Standard Operating Procedure Writer for a Recurring Task

Turns a rough description of a recurring task into a numbered standard operating procedure with roles, inputs, checks and records to keep. Use it to document office, finance or compliance routines so anyone can run them the same way.

A formatted SOP with purpose, scope, roles table, numbered steps with checks, exceptions, records to keep and a review date
The output this prompt produced, unedited.

The prompt

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

  1. Header: SOP title, version 1.0, owner role, effective date placeholder, review date.
  2. Purpose: two sentences.
  3. Scope: what the SOP covers and what it does not.
  4. Roles table with columns: Role, Responsibility.
  5. Before you start: inputs, access and documents needed.
  6. 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.
  7. Exceptions: what to do when something does not match, and who to escalate to.
  8. Records: what to save, where, and for how long, marked [confirm retention period] where law may set it.
  9. 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.
sop templatestandard operating procedureprocess documentationoffice procedureswork instructions

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity