Skip to content
caadoo
de

Process documentation template: how to document a process

Process documentation that people use fits on one page and describes the work as it is done today. Here is a template you can copy, seven steps for documenting a business process, a worked example from a 120-person manufacturer and the mistakes that leave these documents unread.

By T. Krause12 min read

The person who sets up new customer accounts is off sick for two weeks. Three new customers are waiting for their first delivery, and the only written guide is an email she sent a colleague in 2022. Half of the screens it describes no longer exist. Somebody now has to work out from scratch how a customer gets into the ERP and why the last account a colleague set up got stuck at dispatch.

This guide is for owners and operations leads in companies of 20 to 250 people who need to get one process out of one person's head and onto a page. You get a process documentation template you can paste into a wiki or a Word file and seven steps for filling it in. An invented example shows what a finished one looks like. If you keep books in Germany, there is a section on what the GoBD, the tax authority's rules for electronic bookkeeping, add for accounting processes. That section is based on the Federal Ministry of Finance's official 2026 handbook. None of this is tax advice.

Photo: Unsplash

What process documentation is

Process documentation describes a recurring piece of work well enough that someone who has never done it can do it. It records what starts the process, who does each step in which system, where decisions are made and how you know the work is finished. One process usually fits on one page.

It is not a company-wide process manual. Firms that start with the manual tend to end up with a table of contents and forty empty chapters. Start with one process and finish it before you touch the next.

How to document a business process in seven steps

1. Pick a process that hurts right now. Good candidates are processes only one person knows, or ones you plan to automate soon. If you can't tell which process that is, have your team keep a tally for a week. What to automate first explains how.

2. Write down where it starts and where it ends. One sentence each. "Starts when sales sends a signed order from a customer we haven't supplied before. Ends when the customer account is live in the ERP and the first order can be released." Without that sentence, the process grows in every direction while you write it up.

3. Watch the person who does it. A manager knows how the process is supposed to run. The person doing it every day knows how it runs. Sit next to them for an hour and ask them to walk through two real cases. Write down the small moves they think are too obvious to mention. Those are the ones missing from every document written at a desk.

4. Write the steps as a table. One row per step, with role, system, input and output. Use roles, not names. "Credit control checks the limit" survives a staff change, and "Anna checks the limit" doesn't. Start every step with a verb. A step you can't phrase that way usually isn't a step.

5. Write down the decisions and exceptions. This is the knowledge that walks out of the door when someone leaves. When does a new customer pay in advance? Who can approve a credit limit above the normal ceiling? Give every rule a number or a condition. "Usually" is not a rule.

6. Run the stand-in test. Hand the document to someone who has never done the process and have them handle a real case with it. The usual owner watches and stays quiet. Every question they ask marks a gap. Write the answer into the document and repeat until a case goes through without a single question.

7. Give it an owner, a home and a review date. The document gets a responsible role, one place where everyone can find it, a version number and a date for the next review. When a system or an approval limit changes, the owner updates the document that week and logs the change.

The process documentation template

Copy the five tables below into your wiki or a Word document and replace everything in square brackets. The header says what the process is for and who owns it. The steps table describes the work. The other three hold the things that usually get lost.

Header

FieldEntry
Process name[e.g. New customer account setup]
Purpose[one sentence on why the process exists]
Trigger[what starts it]
Output[what exists at the end, and for whom]
Owner[role that keeps this document current]
Stand-in[role that can run the process without asking]
Systems[e.g. ERP, CRM, credit check service]
Volume and time[e.g. 6 cases a week, 40 minutes each]
Version and date[1.0, date]
Next review[date, no later than twelve months out]

Steps

No.Step, verb firstRoleSystemInputOutput
1[Check whether the customer already exists][Sales admin][ERP][Signed order][Confirmed new customer]
2[next step][role][system][what you start with][what you end with]

Decisions and exceptions

At stepIfThenWho decides
[4][Requested limit up to €20,000][Approve within the standard limit][Credit control]
[4][Requested limit above €20,000][Escalate with the credit report attached][Head of finance]

When something breaks

ProblemWhat to doWho to ask
[Credit check service down][Hold the account, note it on the open-items list][IT provider, phone number]

Change log

VersionDateWhat changedBy
[1.0][date][first version after the stand-in test][role]

If you keep books in Germany: the GoBD

For most processes, documentation is your own choice. For bookkeeping in Germany it is partly a requirement. The GoBD, the Federal Ministry of Finance's principles for electronic books and records, call for a Verfahrensdokumentation, a procedure documentation. Paragraph 151 of the GoBD as published in the ministry's official 2026 AO handbook requires a clearly structured procedure documentation for every IT system, showing the content, structure, flow and results of the procedure completely and consistently. A knowledgeable third party must be able to check it within a reasonable time. How detailed it has to be depends on how complex your business, your organisation and your IT system are. The ministry issued the letter on 28 November 2019 and amended it on 11 March 2024 and 14 July 2025.

Under paragraph 153 the documentation normally has four parts, a general description, user documentation, technical system documentation and operating documentation. Paragraph 154 is where the template above earns its keep. The documented procedure must match the one used in practice, and changes must be traceable over time, which the ministry says you meet with versioning and a change history. You keep the documentation for as long as the records it explains. Under paragraph 155, missing or inadequate documentation is not a formal defect of material weight as long as your books stay traceable and verifiable. I wouldn't lean on that. Books whose process only one person can explain are exactly where traceability breaks down.

For a single accounting process such as invoice intake, the template mainly covers what the GoBD call user documentation. The system and operating parts come from your software vendor and your IT provider, and your tax adviser can tell you which parts you are missing. If an AI assistant works on the process, GoBD and AI chatbots covers what it adds to the documentation.

Table or flowchart?

There is a standard notation for process diagrams, BPMN. The Object Management Group, which publishes it, describes BPMN 2.0.2 as the de facto standard for business process diagrams. A process with two roles and ten steps doesn't need it. Anyone can read a table, and a BPMN diagram only makes sense to people who know the symbols. Draw a diagram once more than three roles are involved or the process branches at many points, and draw it from the finished table.

Example: new customer accounts at a 120-person manufacturer

This company is invented. A manufacturer of machine parts with 120 people opens about six new customer accounts a week. For years one person in sales admin has done all of them. When she is off sick and an account set up by a colleague gets stuck at dispatch, the operations lead has the process written down.

The start-and-end sentence from step 2 is the one quoted above. Watching her in step 3 turns up two things nobody had written down. She asks credit control for a report before she enters any limit, because the ERP will accept a limit with no approval at all. She also sets a delivery block on every new account until the first payment term is confirmed, and that block is why the colleague's account got stuck. Nobody had told him to lift it.

The finished steps table has eleven rows and the decisions table has five rules. The one that matters most is the €20,000 line. Credit control approves up to that amount, and above it the head of finance decides with the credit report in hand. In the stand-in test, a colleague from purchasing sets up two real accounts using only the document. He asks three questions the first time, all about the delivery block. With the second version he gets through without one. Credit control becomes the owner, and the review date goes into the shared calendar.

Where process documentation goes wrong

Managers write the ideal process. The document says how things should work, and people carry on as before. Write down the current process first. Improve it afterwards, in version 2.

Everything at once. A project called "document all our processes" tends to end in a folder of half-finished outlines. One finished process a month gets you further.

Names instead of roles. "Anna checks the limit" is true until Anna goes on parental leave.

No owner, no review date. A document nobody owns goes stale at the next system change. Whoever follows it after that makes mistakes, and after one bad experience nobody opens it again.

Nobody knows where it lives. If the document sits in someone's personal OneDrive, the stand-in won't find it. Link it from where the work happens, such as the team's channel in Teams.

Automating before documenting. Automate a process nobody has written down and you build every workaround into the automation. The process document is the brief for the build. Once the automation is live it needs its own short runbook, as described in automations that survive the builder leaving. Before you build, also record how long the process takes today, or you won't be able to show what the automation changed. Measure before you build covers that.

As part of a caadoo subscription I cover the stretch from a written-down process to an automated one. I document the process with your people, run the stand-in test and then tell you which steps a machine can take over and which should stay with a person. If one of your processes depends on a single person right now, tell me which one.

Frequently asked questions

What should process documentation include?

The purpose, trigger and output of the process, the owning role with a stand-in, and the systems involved. Then the steps with role, system, input and output, the decision rules and exceptions, what to do when something breaks, and a version number with a change log. For one process that usually fits on a single page.

How do I document a business process?

Write one sentence on where it starts and where it ends, then watch the person who does the work every day. Turn what you see into a table of steps that names roles instead of people, and add the decisions and exceptions. Finally, have someone who has never done the process handle a real case using only the document. Each question they ask is a gap to close.

Is process documentation a legal requirement?

Not in general. For electronic bookkeeping in Germany, though, the GoBD require a procedure documentation for every IT system that a knowledgeable third party can check within a reasonable time. Ask your tax adviser what that means for your accounting.

Do I need software to document processes?

Not to start. A SharePoint page or a Word document stored where everyone can find it is enough. What matters is that every document has an owner and a review date. A BPMN modelling tool starts to pay off when many roles are involved or the process branches a lot.

How long does it take to document one process?

For a process of around ten steps, plan for three short sessions. One to watch the work, one to go through the first draft with the person who does it, and the stand-in test. The exceptions take most of the time, not the steps.

Topics

  • Process documentation
  • Template
  • Business processes
  • GoBD
  • Mittelstand
All articles

Keep reading

  • 11 min read

    Is ChatGPT GDPR compliant for business? A checklist

    Whether ChatGPT is GDPR compliant depends less on OpenAI than on the plan you buy and the paperwork your company does around it. This piece covers which plans come with a data processing agreement, training, data location and the duties that stay with you.

  • 13 min read

    AI usage policy template for firms of 20 to 250

    An AI policy nobody reads settles nothing. This template has ten clauses with wording you can copy, and for each one it names the decision your company has to make first.

  • 18 min read

    AI and works councils in Germany: what to agree

    You must inform the works council about an internal AI assistant while you are still planning it, and if the tool records use per person, there is a strong case that the council has a say. This piece covers when that applies, the order of steps for a company of 20 to 250 people, and what a works agreement on AI should cover.

End of call

You can hang up now.

Or book 15 minutes. I'll ask you the questions I'd ask on the phone, and tell you at the end whether it fits. If it doesn't, we've both lost a quarter of an hour instead of a month.

Or call. Cold, if you like. My AI assistant picks up and I call you back. +49 5136 9414999

Analytics

With your consent I use Google Analytics to see which pages get read. Without it, no analytics code loads. Your answer is stored locally in your browser.

Privacy notice