Help center

Get your team using SOPCompass

A rollout checklist that uses the features built for getting SOPs read, not just written.

Updated
On this page
  1. 1. Give everyone a home
  2. 2. Start with a small onboarding set
  3. 3. Assign, do not announce
  4. 4. Check understanding where it matters
  5. 5. Point questions at Ask
  6. 6. Make it easy on the job
  7. 7. Invite feedback
  8. 8. Keep it current

The most common reason SOPs fail is not bad writing. It is that nobody reads them. SOPCompass is built around putting the right SOP in front of the right person. Here is a practical way to roll it out.

1. Give everyone a home

Before inviting people, set each person’s departments on the People page. Their Boards page then opens on the SOPs for their departments, so the first thing they see is relevant. See Departments and the department switcher.

2. Start with a small onboarding set

Pick three to five SOPs every person needs, such as how the company works, the tools you use and who to ask for what. Keep them together in a library in the Company area. For example, Harbor Lane Catering (example) keeps “Your first week”, “Our tools” and “Who to ask” in a Company library called “Start here”.

3. Assign, do not announce

An announcement in a group chat is easy to miss. Instead:

  1. Open each onboarding SOP and click Assign.
  2. Pick the people and stagger the due dates (day 1, day 3, day 5).
  3. Add a one-line note on why it matters.

People get an email and see a badge on Assignments. See Assignments and due dates.

4. Check understanding where it matters

For safety rules, compliance or anything costly to get wrong:

  • Add a short quiz and require a passing score on the assignment.
  • For handbooks and policies, turn on policy sign-off so each person signs with their name.

5. Point questions at Ask

When someone asks “how do we…?”, reply with “Ask SOPCompass”. Ask answers from your SOPs with links, and the questions it cannot answer become your list of what to write next.

6. Make it easy on the job

7. Invite feedback

Tell people to use Comment on any step that is wrong or unclear, and to @mention the SOP’s owner. Resolved comments stay as a record. See Comments and @mentions.

8. Keep it current

  • Give each SOP an owner and a review interval. See Owners, review dates and tags.
  • On the Business plan, check Insights for SOPs nobody has opened, searches that found nothing and overdue reviews.