SOP Writing and Process Documentation

Write the process down once so it survives you being unavailable

We interview the people doing the work, write standard operating procedures that are actually followed, and build them into a searchable library with owners, triggers and a definition of done.

A useful SOP is not a long document. It is a trigger, an owner, numbered steps, a definition of done and an escalation path. We sit with whoever currently does the work, capture what really happens rather than what the org chart says should happen, write it in plain language, and put it somewhere searchable. This is also the prerequisite for automation, because you cannot automate a process nobody has written down.

What is included

• Process discovery interviews with the people doing the work
• SOPs written with trigger, owner, steps, definition of done and escalation
• Searchable library structured by function
• Onboarding, delivery, finance and client facing procedures
• Review dates and named owners so documents stay current
• Identification of which steps are worth automating next

What you receive

• A written SOP library covering your core processes
• Templates so your team can add new procedures
• An owner and review date on every document
• A shortlist of automation candidates

Who this is for

Founders who are the single point of failure, and teams about to hire or hand work over.

What you get

A business that keeps running when a specific person does not.