Menu Book a free audit
Practical20 November 20265 min readFayez Nicolas Chaar

Document the process before you automate it

Documenting a process before you automate it means writing down, step by step, how the work actually gets done today: what starts it, who does what, which rules they follow, and what happens when something odd turns up. Automation repeats whatever you give it. If the steps live only in someone's head, the automation will repeat the gaps too.

In short

Write down what really happens, not what should happen. A one-page description with a trigger, the steps, the decisions, the exceptions and an owner is enough to start. If you cannot describe a process on one page, it is not ready to automate.

Why document first?

Most small-business processes grew by habit. One person knows that a certain customer gets a different template, that a particular supplier always sends the wrong format, or that large orders need a second look. None of that is written anywhere. When you hand the work to software, those unwritten rules disappear, and the mistakes show up in front of customers.

Writing the process down also tends to expose things you can fix without any software: steps nobody needs, handoffs where work waits for days, and two people doing the same check. Sometimes the right answer after documenting is to simplify and stop there. If you are still deciding whether the work is ready, our automation readiness checklist covers the wider groundwork.

What should the document include?

Keep it plain. A shared document or a simple table is fine. For each process, capture:

  1. Name and purpose. One sentence on what the process is for and what a good result looks like.
  2. Trigger. What starts it: a form submission, an email, a completed job, a date.
  3. Inputs. The information needed to begin, and where it comes from.
  4. Steps in order. Each one written as a short action, with who does it and which tool they use.
  5. Decisions. Every place where someone chooses between paths, and the rule they use. Mark the ones that rely on judgment.
  6. Outputs. What exists at the end: a record, a message, an invoice, a task.
  7. Exceptions. What goes wrong or falls outside the normal path, and who handles it.
  8. Owner. One named person responsible for the process.

How do you capture what actually happens?

Do not write the process from memory at a desk. Use one of these approaches:

  • Watch it being done. Sit with the person who does the work and have them narrate while they do a real case. Ask "why" when they skip or add something.
  • Walk through recent examples. Pull the last ten cases and trace each one from start to finish. Note where they differed.
  • Ask the people at the edges. The person who receives the output and the person who supplies the input often know where the process breaks.
  • Record, then tidy. A short screen recording or a voice note is often quicker than typing. Turn it into steps afterwards.

Expect the first draft to be wrong. Read it back to the people who do the work and let them correct it. The corrections are where most of the value is.

Why list the exceptions?

The normal path is usually easy. The trouble is in the cases that do not fit: a missing field, a duplicate, a customer with special terms, a request that arrives in an odd format. Ask the people doing the work what they do in those cases and how often they happen. You do not need exact figures, just a sense of whether something is rare or routine.

Each exception then gets a decision: handle it automatically, send it to a person, or stop the process. Our article on the exception problem explains why this list matters more than the happy path, and designing a review queue shows how to route the cases that need a person.

What do you look for once it is written?

Read the finished page with a critical eye and mark anything that falls into these groups:

  • Unclear steps. Anything you cannot describe as a rule, such as "I just know when it looks right". These need a person, or a clearer rule, before software can help.
  • Messy inputs. Data that arrives in several formats or is often incomplete. Clean-up comes first; see cleaning data before you automate.
  • Waiting. Steps where work sits until someone notices it. These are often good candidates.
  • Duplicated effort. The same information typed into two systems, or the same check done twice.
  • Steps with no owner. If nobody is responsible, nobody will notice when it breaks.

Then decide which steps to automate, which to simplify and which to leave alone. If you are not sure where to begin, what to automate first gives a simple way to score the candidates.

What does the document do for you afterwards?

A written process is useful well beyond the build. It is the brief you give to whoever builds the automation, whether that is a colleague, a freelancer or an agency, so they are not guessing. It is what you test against when you run the new version beside the old one. And it is the first thing you open when something stops working, which is why it connects directly to why automations break. Keep it current: when the automation changes, update the page.

Frequently asked questions

How long should the document be?

For a single process, one page is usually enough. If it runs to several pages, it probably covers more than one process, and it may be easier to split it.

Do I need special software?

No. A document, a spreadsheet or even a whiteboard photo is enough. A diagram can help, but a numbered list is often clearer.

What if different people do the same task differently?

That is useful to know. Decide which way is best, or whether the differences exist for a reason, before you automate any of them.

Can I skip this for a small, simple automation?

For something very small, a few lines of notes may be enough. The more customers, money or records an automation touches, the more it is worth writing down first.

Want help mapping a process before deciding what to build? Book a free audit and we will go through it with you.

Want this built for your business?

We will look at how your work flows today and tell you which steps are worth automating, and which are not. Free, and you keep the notes.

You will talk to Fayez or Kareem, the two founders.