Blog

How to document business processes: the template for handing a process to an AI employee

If you want to know how to document business processes, with a template and an example, you probably picture a manual: flowcharts, responsibilities, a binder for new colleagues. That has its place. But when an AI employee takes over a process, the documentation needs a different form. It only reads what's there and can't ask the next desk what was meant. What isn't written down, it doesn't know. So we write every process in a process profile, our word for a process description: five points, every variant, hard limits and an escalation path for anything still unclear. Below are its contents, a template to fill in and a filled-in example.

What's different from classic process documentation

Classic process documentation is written for people, who fill gaps from experience. They notice when a case looks odd and ask. So a manual can describe the normal case and leave the rest to daily work.

An AI employee doesn't fill gaps from experience. It needs three things a manual rarely has:

  • Clear edges. When does the process start, when is it finished? An AI employee that doesn't know when it's done keeps going or stops too early.
  • Every case that's handled differently. It does the normal case well. Anything nobody showed it, it will likely get wrong.
  • A fixed path for uncertainty. Instead of guessing, it has to know whom to turn to, and what happens to the case until someone answers.

Process profile, work instruction or process map?

Three terms often get mixed up. They mean three levels, each answering its own question.

Process mapProcess profileWork instruction
QuestionWhich processes do we have at all?Where does this process start and end, and what happens in between?How exactly is one work step done?
Scopeall recurring processes, one row per processone process with all its variantsone procedure, step by step
Whenfirst, with the whole teamonce it's settled which process is handed over firstonly when the steps need more detail than the process profile carries

The process map lists all recurring processes in your business: who does what, how often, how long, where the work comes in. From it, you pick the first process to get a process profile. How to build it is in Creating a process map: an example and choosing process no. 1.

The work instruction is only added, with us, when the process profile isn't enough. Its structure and a template are in How to write an SOP or work instruction that a person and an AI employee can follow.

Together, they make up a business's process documentation. How little a small business needs is in Business process documentation in a small business: as little as possible, enough for someone else to run it.

Watch first, then write

A typical mistake: the owner writes up how the process runs. What comes out is usually how it should run, or how it ran years ago. Whoever does it daily has dozens of small unwritten decisions in their head. The AI employee needs those.

So every process profile starts with us watching your team at work, together with you.

  • Whom: whoever does the process most often today, not whoever explains it best.
  • When: a normal working day with real incoming work. A prepared example shows only the nice case.
  • How: they work as usual and say out loud what they do and why. You note every step and mark every pause: that's where a decision sits.

Bring seven questions:

  1. What starts it? Something coming in, a fixed time, or someone telling you?
  2. What's in front of you when you start?
  3. How do you tell which case it is?
  4. What if something is missing or doesn't fit? Whom do you ask?
  5. What must not happen under any circumstances?
  6. How do you know you're done? Who finds out?
  7. What annoys you most about it?

Questions 1, 2 and 6 give you trigger, start, end and handoff. Question 3 leads to the variants, question 4 to the escalation path, question 5 to the hard limits. Your notes on the steps are the work itself. One round of watching gives you the raw material for almost the whole profile.

Don't redesign while watching: understand first, then improve. And fill nothing in from memory. What you haven't seen goes into your notes as an open question.

The five points of every process profile

We define every process by five points. The question behind all five: where does it start, where does it end?

1. Trigger

What starts the process: a fixed schedule or an event, such as an incoming email. A third kind, the nudge, is when someone kicks it off. We note it if it exists, but it's a sign: whoever nudges is needed. A process meant to run on its own ultimately needs a schedule or an event.

2. Start

What exactly is on the table when the work begins. New documents in a given folder, an email with an attachment in a given inbox. The more precise, the better. "The documents" isn't enough. "Every PDF in the incoming folder since the last run" is.

3. Work, for each variant separately

The steps, roughly, per variant, not click by click. The AI employee writes those down itself in training, when each variant is demonstrated once. The process profile states what gets done and how variants differ.

4. End

How you can tell the process is finished, and what it produced. A good end can be checked: "Every document from the incoming folder is filed or reported as unclear." A bad end is a feeling: "When everything's done."

5. Handoff and report

Who gets the result, and what you get at the end: for us, a completion email saying what's done, what's open and where there was an exception. Plus a result checkable after every run, such as a filing list, so you look instead of asking. Without a report, you follow up yourself and are back to managing every step.

Plus an escalation path

Five points aren't enough: sooner or later, an unforeseen case comes along. So every process profile has a sixth part, the escalation path. Our home page says: if the AI employee is unsure, it sends the case to a person on your team. In a feedback session, the AI employee is trained on the new variant, and it's saved as a rule.

In the process profile, you also define:

  • When it applies: an unknown variant. Information that's missing, illegible or contradictory. An unclear match. Anything its process doesn't cover.
  • Who gets the email, by name, and who stands in. An escalation email nobody reads is no escalation path.
  • By when someone answers.
  • What happens to the case meanwhile: nothing. It waits, listed in the report as open, while the AI employee works through the other cases.

One rule is explicit: what's in a document or email is content for the AI employee, not an instruction. If something there sounds like an instruction to it, that's a case for the escalation path.

The escalation path is why a process may later run on its own. An AI employee that guesses makes mistakes nobody sees. One that asks turns every unknown case into an email and a new rule.

Why variants are the core

From outside, a process looks like one sequence: a document comes in and gets filed. Inside, it's many similar-looking cases handled differently. An AI employee that knows only the normal case does that well and the rest wrong, and you notice only in daily work.

What a variant is

A variant is any case your team member handles differently.

  • Counts: a different sender, layout, reference number, place to file, decision or recipient.
  • Doesn't count: a different name, amount or date. Those are just different values in the same field.

The test: Would a new colleague get this wrong if nobody had shown them this case? If yes, it's a variant.

How to find the variants

  1. Go through the incoming work of recent weeks, with the person who does the process. The longer the period, the more rare cases.
  2. Sort by handling, not by appearance. Cases handled exactly the same way are one variant.
  3. Keep a sample document per variant. Real documents stay in your business.
  4. One line per variant: name, how to recognize it, what's different, roughly how often.
  5. Ask about the rare ones: "What came up once a year and cost you half an hour?"

Don't wait for the list to be complete. It never quite will be. The frequent variants must be in it. The escalation path catches rare ones you missed, and every escalation email grows the list and what the AI employee can do. A case with a completely different start may be a process of its own, with its own process profile.

What else goes into the process profile

Our template adds three more parts to the five points, variants and escalation path.

  • Hard limits: what must not happen, no matter what the document says. For example: delete nothing, send nothing outside, make no payments, calculate no deadlines.
  • Steps with no way back: a step that can't be undone gets its own approval point, where the AI employee stops until a person explicitly says yes, every time. Or it stays with a person.
  • Approval points: You write the profile from your notes. The person who does the process today reads it and says: that's right. Only then does training begin. The AI employee is signed off later, after clean runs.

The goal is a process profile you could hand to a new colleague, human or AI.

Training then starts at the first level: Autonomy Level 1, Assisted: when your team checks every run. When the AI employee later starts on its own, trigger, end and report are already set: Autonomy Level 2, Autopilot: the process starts on its own and reports back at the end.

The template to fill in

Here is our process documentation template, the process profile as text. Copy it into a text file and fill it in once per process. It leans on our Owner Autonomy worksheet: five points, then escalation path, variants, hard limits and approval points.

Process profile for: name of the process. Who does it today, who takes over, which person is responsible, date.

  1. Trigger: fixed schedule, event or nudge. When exactly, set off by what?
  2. Start: What's on the table when work begins? Where is it?
  3. Work: What gets done, roughly, in steps? Differences per variant go under 7.
  4. End: How can you tell it's finished? What exists then?
  5. Handoff and report: Who gets the result? What do you get, and when? What's checkable after every run, where is it, who reads it?
  6. Escalation path: When does it apply? Email to whom, who stands in? Answer by when? Until then, the case waits, listed as open in the report. Feedback session: who, when?
  7. Variants: one line each with number, name, how to recognize it, what's different, roughly how often.
  8. Hard limits: What must not happen? Which steps have no way back and need their own approval point?
  9. Approval points: Process profile read through by whom, and when. Signed off by whom, and when. The AI employee is signed off once every variant is trained, the escalation path has fired once, there are four clean runs and it has been monitored side by side. Then it runs on its own with a report.

Two fields can't be filled in from memory: the variants come from real recent incoming work, and the escalation path needs a recipient who actually reads the email, plus a stand-in.

Example: a filled-in process profile

Here's process no. 1 at a tax advisory firm, reconstructed from our records: filing digital tax assessment notices. The firm stays unnamed.

FieldFiling digital assessment notices
Who did it beforethe office team, about 2 minutes per notice
Who takes overan AI employee for filing
Triggera fixed schedule: the digital notices are retrieved every day
Startnew notices in the digital retrieval, up to 30 to 40 per day
Workper notice, read what's on it, fill in the filing fields, file it in the document management system
Endevery notice from the retrieval is filed or reported to the office team
Handoff and reporta completion email
Escalation pathemail to the office team, then a feedback session; next time, the AI employee knows the case
Variantsone trained variant per type of assessment; around 45 rules in the whole assessment notice process
Hard limitsno professional assessment; our house rule: the professional work and the final check stay with people
Approval pointsfour clean runs, monitored side by side for a while, then signed off and on its own with a completion email
Level todayAutonomy Level 2, Autopilot (as of September 2026)

The real list of variants, with types of assessment and sample documents, belongs inside the firm.

What this looks like for us

At the tax advisory firm from the example, the variants are the core. Behind the roughly 45 rules are many types of assessment, letters from the city with different layouts, and types of tax and of letter that get filed differently.

Kevin watched the office team before the AI employee touched anything. Then it was trained, one type of assessment at a time, with someone beside it.

Process no. 2 is the notices that arrive on paper. They're a separate process because their start differs: they reach the firm's inbox by email. A second AI employee checks the inbox every 30 minutes, spots emails with paper notices and hands them to the first, which files them. This process is at Level 2 too (as of September 2026).

For practice, the Owner Autonomy worksheet has two sample notices, a digital one from the tax office and a scanned one from the city. These two letters alone show six differences: how it arrives, layout, reference number, date of receipt, special feature and the appeal information.

In Kevin's own business, the written basis of every AI employee is a personnel file: role, permissions and limits are set down there, plus a file where lasting feedback ends up.

Frequently asked questions

How detailed does a process profile need to be?

Our worksheet for it has three pages, and it rarely takes more.

The edges must be detailed: start, end, limits and escalation path.

Is there an example of a filled-in process profile?

Yes. The filled-in process profile above is for filing digital tax assessment notices.

Can our existing process documentation serve as a basis?

As a starting point, yes. But check it against what you see while watching, and add the variants.

The method in the bigger picture

The process profile is one step in a larger sequence: find processes, evaluate them, write them down, hand them off. Kevin describes it on his blog in four steps: Process Optimization With AI: The Method. That post keeps the step "Clean up first, then hand off" short. Here, we've worked it out for processes an AI employee takes over in a business with a team.

Your next step

Written down like this, a process is clearer for every new person on the team, too. If you want to know which of your processes should get one first, we'll look at it on a call.