# Standard Operating Procedure (SOP) Template

Provided by Saker Axis. Adapt freely for your organization.

---

## 1. SOP details

| Field | Entry |
| --- | --- |
| SOP title | |
| SOP number | |
| Version | |
| Process owner (role) | |
| Approved by | |
| Effective date | |
| Next review date | |

## 2. Purpose

Why does this process exist? What problem does it prevent or what outcome does it produce? Keep it to two or three sentences.

## 3. Scope

- **Applies to:** which roles, teams, locations, or clients
- **Does not apply to:** anything that is explicitly out of scope

## 4. Trigger

What starts this process? For example: "A new client signs an engagement letter" or "A maintenance request is received."

## 5. Roles and responsibilities

| Role | Responsibility |
| --- | --- |
| | |
| | |

Every step below should have one owner. A role, not a department.

## 6. Tools and resources

- Systems used (CRM, project management, shared drive)
- Templates and checklists (link to them rather than pasting them here)

## 7. Procedure

| # | Step | Owner | Tool or template | Notes |
| --- | --- | --- | --- | --- |
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |

Tips: start each step with a verb. One action per step. If a step has many sub-steps, it may need its own SOP.

## 8. Definition of done

How do we know this process was completed correctly? List the checks.

- [ ]
- [ ]
- [ ]

## 9. Exceptions and escalation

What happens when something does not fit the standard path? Who decides?

## 10. Measures

Which one or two numbers tell us this process is working? For example, response time, completion time, or error rate.

## 11. Revision history

| Version | Date | Changed by | Summary of change |
| --- | --- | --- | --- |
| 1.0 | | | Initial version |