What we build

SOP & Process Documentation

SOP and process documentation means turning the steps that currently live in one person’s head into a written process your whole team can follow — and you can actually hand off. It’s usually not that the process is wrong. It’s that it only exists as habit, so it breaks the moment the one person who knows it is out sick, busy, or gone.

Signs you need this

You probably don’t need us to tell you. These are the ones we hear most:

  • No SOP exists.We’ll write it.
  • This process makes no sense.We’ll map it.
  • Only Sarah knows how.We love Sarah. Let’s document it anyway.
  • Only works because one person remembers all of it.Let’s get it out of their head.
What’s included

SOP and process documentation usually covers:

  • SOPs + checklistsStep-by-step documentation for the processes that currently exist only as habit.
  • Process mapsA visual walk-through of how work actually moves, so gaps and bottlenecks are visible, not assumed.
  • Training documentationThe materials someone new actually needs to pick up a role, not a vague handoff conversation.
  • Knowledge baseOne place all of it lives, instead of scattered across someone’s inbox and memory.

The result is something your team can actually follow without asking the one person who used to carry it all — not a document nobody opens again.

We work in the tools you already use: your CRM, accounting software, project management and automation platforms. If something genuinely needs replacing, we’ll tell you why.

How it works within Stonework

Like everything else we build, SOP and process documentation starts on your Ops List. We prioritize it against your goals and CEO Scoreboard, put it In Play, and our team works directly with whoever currently does the process today — Sarah, in most cases — to document how it actually gets done, then clean up what doesn’t need to stay that complicated. When it ships, it’s a Win: documented, in use, and yours.

Mapping a process often surfaces where it’s actually breaking down. When that happens, fixing it becomes its own Ops List item — we won’t just write down a broken process and call it documented.

This is also where a lot of our Empower the Team work overlaps: once a process is documented, it naturally feeds the ownership maps, onboarding and hiring workflows that make the business less dependent on any one person.

Questions
Who actually writes the SOPs?
Our team, working directly with whoever currently owns the process. We document how it’s really done today, not how it’s supposed to be done on paper.
What format do they come in?
Written steps and checklists your team can actually follow, stored in your Stonework Client Playbook alongside everything else we document for you.
Does this replace training?
No, but it supports it. A documented process makes onboarding someone new faster and makes the business less dependent on the one person who currently holds it all.
What if the process itself is broken, not just undocumented?
We’ll say so. Mapping it usually shows exactly where it breaks down, and fixing that becomes its own project on your Ops List.
How many processes can we document at once?
Your plan sets how many projects are In Play at a time, not how many you can put on the list. Add every process that needs it — we’ll work through them in order.
Book a call