Blog

Creating a process manual: does a business with ten people need one, and what is enough instead

In many growing businesses, the thought comes up at some point: we should have a process manual. Often after a bad week. Someone was out sick, and nobody knew how their work was done. Or a new colleague took weeks to learn the workflows, and the person who explained them was the owner. The wish behind it is the right one: the knowledge should get out of people's heads and into one place where everyone can find it. Whether a manual is the right way to do that is a different question. In this article, we show what a process manual is, why a business with ten people rarely needs one, what is enough instead and when a manual does make sense.

What a process manual is

A process manual, sometimes called a process handbook or an operations manual, collects the descriptions of a business's processes in one place. Typical contents are an overview of all processes, often as a process landscape, plus a description for each process with responsibilities, flows and the documents that belong to it, such as forms and checklists, and often a matrix of who is involved in which process. How to build a single checklist so that it actually gets used day to day is covered in How to create a checklist your team actually uses: structure, template and the step to an AI employee.

The term is common mainly in quality management, for example in businesses that work according to ISO 9001. There, the tool has a clear purpose: a business shows that it knows, steers and improves its processes, including to third parties. What a standard requires for this is not something we describe here.

For our question, something else counts: does a manual help someone else carry out a process without asking the owner?

Why a business with ten people rarely needs one

A process manual is a big document. It's often written in one go, as a project, and that's exactly its problem in a small business.

It goes out of date faster than it gets maintained. In a business with 3 to 15 people, workflows change often: a new program, a new customer, a colleague takes something over. A manual that nobody maintains is only half right at some point. Anyone who has looked something up once and found the wrong answer won't be quick to look it up again.

It's often written for a different reader. A manual is meant to give an overview. Someone who has a document in front of them that doesn't fit needs something else: the variant, the limit and the path to take when unsure. Whether that's in a manual only becomes clear with a real case.

It ties up time that's missing elsewhere. If you spend weeks writing a manual, you have a document afterwards. If you put the same time into one process and write it down so that someone else can take it over, you have a process afterwards that no longer depends on one person.

Writing things down is still the right move. In a small business, it just works better in small pieces, process by process, at the point where it's needed right now.

What is enough instead

Instead of a manual, we work with three building blocks that live in one place the whole team knows.

  1. The process map. A list of all recurring processes: who does what, how often, how long it takes, what starts it.

    It's the table of contents that a manual would also have. How it comes together is covered in Creating a process map: an example and choosing process no. 1.

  2. A process profile for each process that gets handed over. Five points, trigger, start, work per variant, end and report, plus the escalation path.

    Not every process needs one right away. It's written when the process's turn comes.

  3. The rules. One line per variant: how you recognize the case and what's different then. The rules grow with every case that comes through the escalation path, because in the feedback session afterwards, the new variant is saved as a rule.

Together, these three do what a manual is supposed to do in daily work: the knowledge is in one place. The difference is that they come about piece by piece and are maintained at an event that happens anyway. What else belongs to lean process documentation, work instructions and reports, we describe in Business process documentation in a small business: as little as possible, enough for someone else to run it.

The process matrix: a useful in-between format

One part of the classic manual is worth having in a small business too: the process matrix. It shows on one page who is involved in which process and in what role. The rows are processes, the columns are roles.

Important: roles go in the columns. A role stays even when someone leaves. And whoever has many entries in one column is a bottleneck, whatever that person's name is.

Four letters are enough for the entries:

  • D does the process.
  • A approves before something goes out or can't be taken back.
  • E gets the escalation when something doesn't fit.
  • I is informed, for example through the report at the end.

As a template, it looks like this:

ProcessOwnerOfficeBookkeepingSalesAI employee
………………
………………
………………

You adapt the columns to your business. The matrix shows you two things right away. First: in which rows is there a D or an A under the owner? That's where the business depends on you. Second: are there rows without an E? Then nobody in that process knows where an unclear case goes.

The AI employee column is there on purpose. When an AI employee takes over a process, the D moves from another column to it. With us, the A and the E stay with people on your team. For decisions about people, about money or about anything with legal consequences, our house rule applies: we keep a human involved.

When a process manual can make sense

There are good reasons for a manual, even in a small business.

  • A certification. Which documentation it needs and whether it has to be a manual is something to settle with a quality management consultant.
  • Requirements from customers. Some clients require their suppliers to have described processes. Then the client decides the form.
  • A lot of people doing the same work. When a workflow is supposed to run the same way at several locations, a shared document helps.

For documentation according to standards, we're not the provider. We build AI employees that take over processes, together with you and your team.

But the two don't rule each other out. A process profile that an AI employee uses to carry out a process is a good basis for process descriptions later on. And if you already have a manual, you have a good start for the process map.

If you already have a manual

Then use it as a starting point and check every process that's supposed to be handed over against what happens in daily work. The best way to do that is to watch the person who does it most often today. Pay attention to every spot where they do something differently from what the manual says. Variants like these, and the path for the unclear case, have to be in it before someone else takes over the process.

How to start without a manual

If you want a manual but don't need a certification, go in this order.

  1. Create the process map with your team. All recurring processes on one list, with who, how often and how long.
  2. Put the process matrix next to it. Where is there a D or an A under the owner? Where is an E missing?
  3. Choose one process and write a process profile for that one only. Ideally one that comes up often, follows clear rules and has no step that can't be taken back.
  4. Hand it over, learn, add to it. Every unclear case becomes a rule. Only once the process is running does the next one follow.

That way, the most important parts of a manual come about piece by piece, without you having to write one in a single go.

What this looks like for us

At a tax advisory firm, AI employees have taken over two processes: filing digital tax assessment notices and filing the notices that arrive on paper. Behind them are around 45 rules.

As a process matrix, it looks like this. The roles come from the case; the letters are our own reading. The paper notices are one process with two stations, the inbox and filing, just as we show it in the other articles.

ProcessAI employee for the inboxAI employee for filingOffice teamKevin (looking after the firm)
Filing digital noticesDEI
Paper notices (inbox and filing)DDEI

Today, the AI employees do the filing. From these two processes, the cases that can't be matched with certainty go to the office team. A feedback session follows, and a new rule is added. Both processes are at Autonomy Level 2, Autopilot (as of September 2026).

In Kevin's own business, the responsibilities are set down in the personnel files. Each of his 14 AI employees has a personnel file, a fixed role and clear limits.

Together, they do the job there that the chapter on responsibilities would do in a manual.

Frequently asked questions

What goes into a process manual?

Typical contents are an overview of all processes, a description of each process with responsibilities and flow, the documents that belong to it, and a process matrix. How extensive it has to be depends on the purpose. A certification has different standards than handing over a process.

What is a process matrix?

A table with processes in the rows and roles in the columns. Each cell says what the role does in that process: does it, approves, gets the escalation, is informed. It shows at a glance where the bottlenecks are.

How long does it take to create a process manual?

That depends on the number of processes and on the purpose. We can't give you a reliable number for it. For small businesses, we recommend starting with the process map and a first process profile.

Can an AI employee work with a process manual?

With parts of it. The useful sections are the ones that say what to do in which case. Check beforehand whether the variants and the escalation path are in it. If not, they're added through watching and the process profile.

Read more

The frame above all processes, with core, management and support, is described in Process landscape of a small business: core, management and support processes, with an example. How Kevin approaches processes in businesses with a team is on his page Process Optimization for SMEs.

Your next step

A business with ten people rarely needs a manual. It needs one process that no longer depends on one person, and then the next one. On a call, we find the first one.