Power comboSource-backedVerified 2026-04-20
Office Manager / Keep office SOPs and service standards current after system changes
Change request to updated SOP to comms draft
When a system or policy change lands, run it through AI to produce the updated SOP, the changelog entry, and the staff announcement in one pass.
Best for
Analysis & Decisions
Docs seat + free AI
Setup
1 hrs
One-time setup estimate
Workflow
- 1Collect the source material for "Keep office SOPs and service standards current after system changes" before opening the tool.
- 2Run the starter prompt in Claude + Notion + email client and paste in the real context.
- 3Review the output for accuracy, tone, names, numbers, and policy-sensitive details.
- 4Save the improved prompt or checklist so the next run takes less time.
Inputs you need
- - Office Manager
- - Keep office SOPs and service standards current after system changes
- - Examples, notes, files, or customer context for this task
- - Your preferred tone, constraints, and final format
Expected output
- - Change request to updated SOP to comms draft
- - A usable draft or workflow for keep office sops and service standards current after system changes
- - A repeatable prompt you can improve after each run
Ready-to-copy asset
Starter prompt
A change has landed. Produce the full documentation update. Change: [DESCRIBE] Affected SOPs: [PASTE] Return: updated SOP(s), changelog line with date and owner, staff announcement email, FAQ with 5 likely questions, and a rollout checklist with dates.
Caveats
- - Do a human review before sending, publishing, filing, or making a decision.
- - Verify numbers, names, claims, citations, and compliance-sensitive details.
- - AI drafts. You decide. Final responsibility is yours.
Measurable value
3.1 hrs saved per run
Before: 4 hrs. After: 55 min.