Blog

Business process documentation in a small business: as little as possible, enough for someone else to run it

When it comes to business process documentation, many people think of thick binders that were put together once for an audit and that nobody has opened since. Or of a wiki that someone started two years ago and that is only half right today. Yet the question behind it is simple: can someone else run a process without asking you? A business with a team doesn't need thick binders for that. It needs a few building blocks, in one place, that get a little better after every unclear case. In this article, we show which building blocks those are, where they live, who maintains them and what you can safely leave out.

Whom you're documenting for

All process documentation has a reader. What goes into it depends on who that is.

Documentation for auditors is meant to show that a business knows and steers its processes. It's the kind you know from quality management. It describes responsibilities, flows and interfaces, often at a high level. For that purpose, it's the right approach. What a standard requires for it in detail is not our topic.

Documentation for the people who do the work is meant to make sure someone can get the process done. This reader wants to know: what do I do now with this document that's right in front of me?

We write for the second reader, and in a way that an AI employee can work with too. With us, an AI employee works under one rule: a case it can't match with certainty isn't guessed at but goes to a person through the escalation path. Whatever gets settled in the feedback session afterwards is written into the documentation as a new rule. Documentation built like this also helps the new colleague and the stand-in during vacation.

Five building blocks of lean process documentation

With our method, these five building blocks are enough for a business with 3 to 15 people. Each one has its own purpose, and none repeats another.

1. The process map

A list of all recurring processes in your business: who does what, how often, how long it takes, what starts it, and whether it takes thinking or just doing.

It's the table of contents of your documentation. Anyone who wants to know whether there's a process for a topic looks here. How it comes together is covered in Creating a process map: an example and choosing process no. 1. The bigger frame above it, with core, management and support, is described in Process landscape of a small business: core, management and support processes, with an example.

2. The process profile for each process

For every process that gets handed over, a process profile, our word for a process description, with the five points: trigger, start, work per variant, end, report. On top of that, the escalation path and the hard limits, meaning what must never happen.

The process profile sets the edges. It's the most important building block, and the article How to document business processes: the template for handing a process to an AI employee describes it in detail.

3. The work instruction, where needed

Some processes need more than the process profile: step-by-step instructions, for example because a person only does the process rarely or because every click in a piece of software matters. Then a work instruction, often called an SOP, is added. It's more detailed than the process profile and hangs off it. How to write one is covered in How to write an SOP or work instruction that a person and an AI employee can follow.

Not every process needs one. With an AI employee, the exact steps come about during training: someone demonstrates each variant once, and the AI employee writes the steps down itself.

4. The rules

A rule describes a variant: how you recognize the case and what's different then. The rules are the part of the documentation that grows the most. That's because every case nobody knew about yet reaches the team through the escalation path. In the feedback session afterwards, the AI employee is trained on the new variant, and it's saved as a rule.

5. The reports

After every run of a process, there's a report: what's done, what's still open, where there was an exception. For us, that's a completion email.

Reports are part of the documentation because they show what actually happened. The other four building blocks describe how it's supposed to run. The reports show whether it does.

Overview: your process documentation on one page

Building blockWhat's in itWho maintains itWhen does it change?
Process mapall recurring processes, who, how often, how longyou, with the teamwhen a process is added or dropped
Process profiletrigger, start, work per variant, end, report, escalation path, hard limits…when the start, the end or the limits change
Work instructionsteps in detail, only where needed…when a step changes
Rulesone line per variant…after every feedback session
Reportswhat's done, what's open, which exceptionthe AI employee, with every run; for people: …after every run

The "Who maintains it" column is left open on purpose. Enter a person, not a department, because this is about who takes care of it. A building block without a name goes out of date quickly. In the process matrix, which shows who is involved in which process, you enter roles instead. We describe that in Creating a process manual: does a business with ten people need one, and what is enough instead.

Where the documentation lives

In one place. That sounds obvious, and yet it's often missing. If the process profile is in one folder, the rules are in an email and the owner has the process map on their own computer, then nobody has the whole picture. Everyone works with a different version.

Which place that is matters less. A shared folder is enough, and so is a wiki. Three things matter:

  • The team knows where it is. Every person who works on a process knows where the documentation lives.
  • There's one version. No copies in emails, no printouts with notes in the margins.
  • The AI employee can get to it. When an AI employee takes over the process, it has to be able to read the rules, with access that allows as little as necessary.

Who maintains it

Documentation goes out of date when maintaining it is a task of its own that gets done at some point. It stays current when maintaining it is tied to an event that happens anyway.

For us, that event is the feedback session. When an AI employee can't match a case with certainty, it sends it to a person on your team. Afterwards, you talk through what would have been right, and the new variant goes into the documentation as a rule.

That way, the documentation grows with the process, exactly in the places where it was missing.

For the process map, there's a second event: the monthly review. In Owner Autonomy, we look together once a month at which level each process is on and decide what comes next.

That's when you notice if a process has been added that doesn't have an entry yet.

What you can leave out

Lean documentation is also a question of what doesn't go into it.

  • The normal case in prose. If the process profile has the start, the end and the variants, you don't need a block of text that tells the same story again.

  • Org charts for three people. Who does what is on the process map.

  • Processes that are about thinking. Developing ideas, concepts, strategy: these aren't flows with rules. They stay in conversation and don't need a process profile.

  • Rarely used special cases at full length. One line in the rules is enough. Whatever comes up only very rarely is caught by the escalation path.

  • Anything you haven't seen. Whatever comes only from memory goes in as an open question, not as a rule.

What doesn't belong in the process documentation but still needs a fixed place, such as customer knowledge, logins and the reasons behind decisions, is covered in Business systems: how the knowledge in your head becomes something your team can use.

How you can tell the documentation is enough

Whether your process documentation is enough is something a handover will show you: give it to someone who doesn't know the process and have them explain what they would do. How this test works step by step is covered in How to write an SOP or work instruction that a person and an AI employee can follow.

For the documentation as a whole, one rule counts here: every spot where they hesitate is a gap. Close exactly that gap, and no more. If you rewrite everything from scratch after every test, you end up with thick binders again. If you only fill the gaps, you have documentation that gets a little more precise with every round and still stays short.

What this looks like for us

Kevin's own business has 14 AI employees: content, SEO, video editing, bookkeeping prep, leads and email. Each one has a personnel file, a fixed role and clear limits.

The personnel file is the written basis of every AI employee: role, permissions and limits are set down there. On top of that comes a file where lasting feedback ends up. That's process documentation in its shortest form: who am I, what am I allowed to do, what have I learned.

At a tax advisory firm, an AI employee files tax assessment notices, both digital ones and ones that arrive on paper. The documentation of this process consists mainly of rules: the assessment notice process distinguishes around 45 of them, because there are many types of assessment, letters from the city with different layouts, different types of tax and types of letter.

These rules are documentation that has grown over time. They come from watching the office team, from training one type of assessment at a time and from the cases that came through the escalation path afterwards: anything the AI employee can't match with certainty goes to the office team by email, a feedback session follows, and the rule is added. On top of that come the completion emails after every run. What a process profile for this process can look like is shown in the example in How to document business processes: the template for handing a process to an AI employee.

Both processes, filing the digital notices and filing the notices that arrive on paper, are at Autonomy Level 2, Autopilot (as of September 2026).

Frequently asked questions

How do I start with process documentation when there's nothing there yet?

With the process map. It shows which processes exist. Then you choose the one that should be handed over first and write a process profile for that one only. The others follow when their turn comes.

Is our existing documentation from quality management enough?

As a starting point, yes. But check it against what happens in daily work. In our view, documents written for auditors often lack the variants and the path for the unclear case. Those are exactly what someone doing the work needs.

Do I need a process manual?

A business with ten people rarely needs one. For handovers in daily work, the five building blocks in one place do the same job, and because they're tied to the feedback session, they go out of date more slowly. When a manual can make sense is covered in the article on the process manual.

Who writes the documentation, me or the team?

Both. You ask the questions and write the process profile; the person on the team who does the process reads it through. The rules come afterwards, from the feedback sessions.

What an AI employee is

If you can't quite picture an AI employee with a personnel file yet, Kevin explains it on his blog: What Is an AI Employee?. This article was about which documentation an AI employee like that needs in a business with a team.

Your next step

Good process documentation is short, lives in one place and gets better with every unclear case. On a call, we look for the process your documentation should start with and settle who takes care of maintaining it in your business.