Help CenterSOPs & Tasks

Writing SOPs your team will actually follow

📋 SOPs & Tasks
5 min

Writing SOPs your team will actually follow

Structure, language, and a template that works for any process.

SOPs (Standard Operating Procedures) document repeatable processes. Good SOPs are short, scannable, and outcome-focused.

Anatomy of a good SOP

  1. Title — verb-led (e.g. "Onboarding a new client").
  2. Purpose — 1–2 sentences on why this matters.
  3. Owner — the person responsible.
  4. Trigger — when this SOP runs (e.g. deal moves to Won).
  5. Steps — numbered, with clear actor for each.
  6. Definition of done — how you know it worked.

Template

## Purpose
Why this SOP exists.

## Owner
@person

## Trigger
What kicks this off.

## Steps
1. **[Role]** does [action] → [outcome].
2. ...

## Done when
- ✅ Customer received welcome email
- ✅ CRM updated with kickoff date

Tips

  • One verb per step ("Send the invoice", not "Send the invoice and follow up").
  • Link to related SOPs.
  • Add screenshots for UI steps.

💡 Tip: Train your chatbot on your SOPs — it instantly becomes an internal helpdesk.

More in SOPs & Tasks

Still need help?

We typically reply within 24 hours.

Contact support