Company Handbook and Procedures | Getting It in Writing

In most small businesses, process knowledge doesn’t live on paper — it lives in the founder’s head, or in the heads of a handful of people. When someone new joins, everything gets explained verbally, the same questions get asked over and over, and things slow down the moment someone takes time off. This gets more expensive the more the business grows.

I turn this knowledge into written procedure: how each task is done, who’s responsible, and in what order it happens. The most efficient approach is to start from existing meeting and walkthrough recordings — instead of asking you to write down what you’ve already explained, I turn what you’ve already said into a structured document.

Where to Start

First, we identify which processes get asked about the most, and which ones cause the most confusion. These are usually recurring daily tasks like greeting customers, order/quote flow, or handling returns and complaints. Instead of trying to document everything at once, we start with the few processes that will add the most value.

I ask you or the relevant person for a short conversation walking through the process; I turn that raw explanation into a written, step-by-step procedure.

Extracting Procedures From Meeting Recordings

If you already explain these processes in internal team meetings, I can extract the procedure using recordings (if you have them) or a short walkthrough session. This is much faster and more accurate than writing from scratch, because it reflects how things actually work, not the theoretical version.

AI speeds up the transcription and first draft here; I personally check that the final language fits your company and is accurate.

One Handbook, a Living Document

I deliver the handbook as a single, organized document, but I say upfront that this isn’t a finished product — it’s a living document. It needs updating as processes change; you can update it yourself, or I can update it periodically.

How do we start? First, we have a free 20-30 minute initial call. We talk about what you want and what’s realistic. If it looks like a good fit, I send you the scope and price in writing, then we begin. You can reach me through the contact page.

Frequently Asked Questions

How many procedures should we start with?

I recommend starting with the 3-5 most recurring processes. Trying to write everything at once slows the project down and reduces its value.

Will my team actually read this handbook?

Long, theoretical handbooks usually don’t get read. I write short, step-by-step, with real examples — the goal isn’t an encyclopedia, it’s a reference someone opens and checks while actually doing the work.

My processes keep changing — does this still make sense?

Yes — in fact, a written version matters even more when processes change often, because a current document is the only way to announce a change to everyone, at the same time, correctly.

How is this different from an onboarding package?

The handbook covers all of the company’s processes; the onboarding package is the summary information a new hire needs in their first few days. The two complement each other.