Process documentation fails when it is written once and never owned. Here is the structure we use on every engagement.
An SOP is not a document, it is a maintained asset. The difference shows up six months later, when the person who wrote it has moved on and nobody has touched it since.
Every procedure we write has four fixed sections: trigger, steps, exceptions and escalation. The exceptions section is where most documentation fails — it is the part that turns a checklist into judgement your team can apply.
Ownership matters more than format. Each SOP names a single owner and a review date. Anything past its review date shows up on the team lead's dashboard until it is either updated or retired.
Finally, tie SOPs to QA. If the quality scorecard scores behaviour that the SOP does not describe, one of the two is wrong. Keeping them in sync is what makes quality coaching feel fair instead of arbitrary.