Operating Systems

SOPs (Standard Operating Procedures)

Short, specific, operable documents that describe how a recurring task is done at an agency — distinct from training manuals or policy documents.

Also known as: Standard Operating Procedures · Operating Procedures · Playbook Documents

Full definition

Standard operating procedures (SOPs) at service agencies are short, specific documents — typically 1–3 pages each — that describe exactly how a recurring task is performed. Good SOPs are operable: a team member can follow them end-to-end and produce the expected output without additional guidance. They are distinct from training materials (which teach a concept) and policy documents (which set rules). Effective SOP libraries cover the 15–25 highest-frequency tasks at an agency; attempting to document everything produces compliance burden rather than operating value.

When this matters

SOPs matter most in the 6–25 person range — the point at which the founder can no longer train every team member directly. Below that, SOPs are overhead; above that, operating consistency depends on them.

Commonly confused with

Agencies often build SOPs as documentation projects. They become operating assets only when paired with a trigger (when is this done?) and an owner (who runs this SOP?).

Related terms

Related reading