All answers
How do I create SOPs for a completely new department?
March 6, 2026·2 min read·SOPs by Role and Use Case
Start by identifying the 5-10 workflows the department performs most frequently. Record each workflow using a capture tool as you or the department lead performs the task. Prioritize processes that are repetitive, error-prone, or require handoffs. Do not try to document everything at once — focus on the critical daily tasks first and expand over the first 90 days.
What is the order of priority?
| Priority | Process Type | Example | When to Document |
|---|---|---|---|
| 1 | Daily core tasks | Processing orders, responding to tickets | Week 1 |
| 2 | Handoff processes | Transferring work between teams | Week 2 |
| 3 | Weekly recurring tasks | Reporting, review cycles | Week 3-4 |
| 4 | Exception handling | Escalations, refunds, edge cases | Month 2 |
| 5 | Monthly/quarterly processes | Audits, compliance reviews | Month 3 |
What is the fastest approach?
- List all workflows — Ask the team "What do you do every day?" and write down 15-20 tasks
- Rank by frequency and impact — Daily tasks with handoffs go first
- Record the top 5 — Use Glyde to capture each workflow in real time (5 min each)
- Have someone else follow the guide — If they can complete the task without asking questions, the SOP works
- Iterate — Add context, fix unclear steps, then move to the next 5 workflows
How do you organize department SOPs?
- Create a department wiki page — Notion, Confluence, or SharePoint
- Group by function — "Customer Communication," "Data Entry," "Reporting"
- Title as questions — "How do I process a refund?" is easier to search than "Refund SOP v2"
- Assign owners — Each SOP has one person responsible for keeping it current
- Set review dates — Quarterly review reminders for high-traffic SOPs
This answer is part of our guide to SOPs by role and use case.