Standard Operating Procedure (SOP) Templates for Affine

SOP Templates

An SOP turns "ask the person who knows" into a document anyone can follow. This collection gathers AFFiNE's free standard operating procedure templates — general-purpose SOPs, customer support procedures, and operations runbooks — with ownership, versioning, and approval built into the structure.

Each template is a living document: duplicate a layout, write the steps as short numbered actions, route it through the approval section, and publish to the team workspace. Because SOPs live where the team already works, the current version is always the one people find.

Pick the procedure format you need below.

FAQ

What should an SOP include?

Purpose, scope, owner, effective date, the numbered steps themselves, and a revision log. The steps carry the value — one action per step, a screenshot or link where it helps, and no step that hides three decisions inside it.

How detailed should an SOP be?

Detailed enough that a competent new hire can follow it without asking for help — and no more. Over-specified SOPs go stale faster and get skipped; the test is whether the newest team member can execute it cold.

How often should SOPs be reviewed?

Put a review date on every SOP — quarterly for fast-changing processes, annually for stable ones — and review on any process change or incident. An SOP nobody has touched in two years is documentation of how things used to work.