PROCESS DOCUMENTATION
Process Documentation for Small Business NZ: Write It Once, Automate It Later
How to get the way your business runs out of your head and onto a page, in a form you can hand to a new hire today and to a workflow next year.
Most small businesses in New Zealand run on processes that live in one person’s head. Often the owner’s. It works until that person is on holiday, off sick, hiring their replacement, or trying to automate the job and discovering nobody can say exactly what the job is.
Process documentation fixes that, and it does not have to mean a forty-page operations manual nobody reads. It means one page per process, written the way the work is actually done, kept somewhere the team already looks.
This guide covers what to write, how to capture it without stopping the business, and why doing it now makes automation later faster and cheaper.
What process documentation is, and is not
A documented process answers one question: if a capable person who had never done this task sat down tomorrow, could they do it from the page without asking you? If yes, it is documented. If they would need to come and find you, it is not.
It is not a policy, which says what the business believes. It is not a job description, which says what a role covers. And it is not a flowchart for its own sake. It is a set of instructions for getting one repeatable piece of work from start to finish.
A one-page format that works
Every process page carries the same headings, in the same order. Consistency matters more than the headings themselves, because people learn where to look.
- Name and owner. What the process is called and who is responsible for keeping the page accurate.
- Trigger. What starts it. A new enquiry arrives. It is the 20th of the month. A job is marked complete.
- Inputs. What you need before you begin: the client’s details, the signed quote, a login to a particular system.
- Steps. Numbered, one action each, naming the tool and the exact place in it. “Open Xero, go to Business, then Invoices, then New Invoice” beats “raise the invoice”.
- Decisions. Any step where the person has to choose, with the rule they use. If there is no rule, write “ask the owner” and notice how often that comes up.
- Output. What exists at the end that did not exist at the start, and where it goes.
- Exceptions. The two or three things that commonly go wrong and what to do about them.
- Time and frequency. How long it takes and how often it runs. You will want this later.
Keep it to a page. If it will not fit, you are probably looking at two or three processes stuck together, and splitting them is itself useful.
How to capture it without stopping the business
Nobody has a free week to write documentation. The trick is to capture processes while they are being done, not afterwards from memory.
Record the screen. Next time you do the task, record your screen and talk through what you are doing and why. Twenty minutes of recording turns into a page of steps in a fraction of the time it would take to write from scratch, and it captures the small things you would never think to mention.
Write what happens, not what should happen. The honest version includes the workaround, the spreadsheet on the side and the step everyone skips. Document reality first. You can improve it once you can see it.
Have someone else follow the page. The fastest test of a process document is handing it to a colleague and watching where they get stuck. Every question they ask is a missing line.
Start where the risk is. The first process to write down is the one only you can do. In a lot of New Zealand businesses that is invoicing, quoting or payroll, and it is also the thing that stops the owner taking a proper break over the Christmas shutdown.
Where to keep it
Wherever your team already looks every day. A shared Google Drive folder, a Notion workspace, a SharePoint site or a page in your job management software all work. The page should be two clicks away from the people who need it, and there should be exactly one copy.
Some processes you may already be required to write down, such as health and safety procedures, and business.govt.nz has guidance on those obligations. If you have them, collect them into the same place rather than keeping compliance documents in one system and operational ones in another.
From documentation to automation
Here is why this is worth doing even if you never hire another person. A well-written process page is most of the specification for an automation.
Look at the steps column. Some steps are the same every single time: copy this field there, send this email, create this record. Those are automation candidates. Other steps have a decision in them that depends on judgement. Those stay with a person, at least at first. A process document makes that line visible before anyone has quoted for a build.
The time and frequency line does the rest. A task that takes ten minutes, runs twenty times a week and has no decisions in it is a strong first candidate. A task that runs monthly and needs the owner’s call on every instance is not, however annoying it feels. Our guide to what a service business should automate first turns that into a scoring rule you can apply to your own list.
When you do decide to build, the documentation changes the engagement. Instead of a developer interviewing your team for a week to work out how the process runs, they start from the page, confirm it, and scope the build against it. That is how we prefer to start, and it is described on our business process automation service page. The build is shorter, the quote is tighter, and when the workflow goes live the page becomes the record of what the automation does and where a person steps back in.
Keeping it alive
Documentation goes stale the moment the process changes and the page does not. Three habits stop that.
Put a review date on every page and a named owner next to it. Add a change line at the bottom whenever a step changes, with the date and a few words on why. And make updating the page part of changing the process, not a separate job to do later. If a new tool comes in, the page changes the same week.
A quarterly pass over the whole set is enough for most small businesses. It takes an hour, and it is usually the hour where someone notices that two processes now contradict each other.
Common questions
How detailed does process documentation need to be?
Detailed enough that a capable new person could do the task tomorrow without asking you, and no more. One page per process is the right target. If a process genuinely needs ten pages, it is probably three processes.
Which process should I document first?
The one that only you know how to do. That is the biggest risk to the business, and it is usually also the one you most want off your desk. After that, anything a new hire would need in their first month.
What tool should I use?
Whatever your team already opens every day. A Google Doc, a Notion page, a SharePoint folder or a shared drive all work. The tool is not the hard part. Writing it down and keeping it current is.
How does documentation help with automation?
A clear process document is most of the specification for an automation. It shows which steps are the same every time and which need a decision, and it makes the hand-off between a person and a workflow obvious. Builds scoped from a written process are shorter and cheaper than builds scoped from a conversation.
How often should I review it?
Put a review date on every page and check it when it comes up, or whenever the process changes, whichever comes first. A quarterly pass is enough for most small businesses. Out-of-date documentation is worse than none, because people trust it.
Talk to us about it
AUXA is based in Auckland and builds automation for New Zealand and Australian service businesses. If you have a process written down and want to know whether it is worth automating, send it over. That conversation is free.
Get in touch