Operations & SOPs
Weekly SOP Review
A 30-minute weekly review that updates one SOP after something broke, so the document stays true.
Fill in your details
Enter your specific information — the prompt updates automatically.
The prompt
Write a weekly SOP review for [BUSINESS_NAME]. It should take about 30 minutes and update exactly one SOP.
Facts:
- Who runs the review: [REVIEWER]
- Day and time: [WHEN]
- Where the SOPs live: [LIBRARY]
- The SOP that broke this week: [BROKEN_SOP]
- What happened: [WHAT_BROKE]
- The step that was missing or wrong: [MISSING_STEP]
- Who has to follow the new step: [ROLE]
Output:
1. A 30-minute agenda with times. Five blocks at most.
2. The questions the reviewer asks the person who did the job. No more than four questions.
3. The replacement step, written as a verb, using only [MISSING_STEP]. Do not add steps they did not ask for.
4. A change log line: date, SOP name, what changed, who approved.
5. A "do not do this" line: do not rewrite the whole manual in this meeting.
Rules:
- One SOP. If they list two, tell them to pick the one that cost time this week and review the other next week.
- Do not invent a tool, a fine, or a new policy.
- Plain language. The change log should be something they can paste into the top of the SOP.
Paste this into ChatGPT (chat.openai.com) or Claude (claude.ai) and hit enter.
Best for
OwnersOffice managersAnyone with a stack of stale SOPs
operationssopreviewdocumentation