How to write SOPs an advisory firm will actually use

Nearly every firm we work with has tried this before. There is a folder somewhere with procedure documents in it, written during a quiet stretch by somebody conscientious, and almost nobody opens it.

The documents are usually fine. The problem is structural, and it is the same problem every time.

Why the central manual fails

An SOP kept in a shared drive requires somebody mid-task to stop, leave the system they are working in, find a folder, find a file, and locate the relevant section. Nobody does that under pressure. They ask a colleague instead, which is faster and is also exactly the dependency the document was written to remove.

The second failure is drift. A central document is updated when somebody remembers, which means within a year it describes a process the firm no longer follows, and the first person to notice stops trusting all of them.

Documentation is not finished when it is written. It is finished when somebody can find it six months later without asking anyone.

Put the procedure where the work happens

The single change that makes SOPs stick is location. The procedure for a CRM workflow belongs on the workflow, as task-level instructions attached to the stage somebody is standing in. The filing convention belongs in the document system. The approval steps belong on the approval.

Written that way, the documentation is not a thing you consult. It is a thing you are already looking at, and it gets corrected in place the first time somebody finds it wrong. That is one of the standards we hold every engagement to.

What a usable procedure contains

• The trigger: what has happened that means this procedure now applies
• The owner: a named role, not a person, so it survives a departure
• The steps, in the order they are actually performed, in the systems they are actually performed in
• The exceptions, which is the part everybody omits and the part everybody needs
• What "done" looks like, so two people would agree on whether it is

The exceptions section is the one that separates a document from a genuinely useful one. Anybody can write the happy path. The value is in what happens when the custodian rejects the form.

Write them in the order that pays

Do not attempt to document everything. Start with the processes that repeat most and hurt most when they go wrong, which for most firms is onboarding, annual reviews, and money movement. Three good procedures that are used beat thirty that are filed.

This is also the material a buyer reads during diligence, which we covered in what a buyer is actually pricing, and the material a new hire learns from, so it pays twice before it ever pays at exit.