Nobody has time to write it down
Everyone agrees the processes should be documented. There is a folder called Procedures with three documents in it, one of them from before the last system change. Every time someone leaves, a chunk of how the business works leaves with them.
The people who know the processes best are the busiest, and asking them to spend an afternoon writing a procedure for something they do without thinking is a hard sell. When they do try, the result misses the steps they no longer notice they do.
You may also be looking at automation and have been told the first step is to 'map your processes'. That sounds like weeks of workshops and sticky notes, and nobody can spare the people for it.
Why documentation never gets written
The usual explanation is time, and it is part of the truth. The bigger reason is that writing a procedure from memory is genuinely hard. Experts compress. They skip the checks they do automatically, the exceptions they handle by instinct, and the workaround they built for the system bug three years ago.
So even when documentation does get written, it describes the process as people think it runs, not as it actually runs. That is why new starters are told to 'ignore the manual and watch Sarah'.
The work itself, though, leaves a trail. Screens are clicked in order. Records are created and changed in systems with timestamps. Emails go back and forth in patterns. That trail is a far more accurate starting point than memory.
What undocumented processes cost
| Situation | Cost |
|---|---|
| Someone leaves or is off long term | Knowledge walks out; others reverse-engineer it |
| New starter training | Weeks of shadowing, inconsistent habits passed on |
| Automation project | Time spent discovering the process before building anything |
| Errors and inconsistency | Different people do the same task different ways |
| Audits or accreditation | A scramble to write procedures under pressure |
How we capture the process from the work itself
Our method uses several sources, because each one sees part of the picture:
- Screen recordings. The person does the task as normal while recording their screen and, if they like, talking through what they are doing. No preparation needed.
- System logs and history. Where your CRM, ERP, helpdesk or accounts package keeps an audit trail, we export it and look at the real sequence of steps, how often each path happens, and where work waits.
- Email and ticket patterns. With permission, we look at the shape of conversations, such as which approvals happen by email, rather than their private content.
- AI drafting. We use a large language model (such as Anthropic Claude or OpenAI models, under an agreement that does not train on your data) to turn transcripts, recordings and logs into a draft procedure: steps, decision points, systems used, exceptions.
- Short review sessions. The person who does the work reads the draft and corrects it. Editing a draft is much quicker and more accurate than writing from nothing.
- Publish in a format people use: a searchable internal page, checklists inside the tool where the work happens, or a flow diagram for the process owner.
Where the aim is automation, the same material shows us which steps are rule-based and repetitive, and which need judgement, so we can recommend what to automate and what to leave with people.
Procedures that match reality
You get procedures written from how the work is actually done, confirmed by the people who do it, without anyone losing days to writing. New starters have something accurate to follow. Automation projects start from a real map rather than a guess.
Because the capture method is lightweight, it can be repeated when a process changes. Record the new version, regenerate the draft, review it. Documentation stops being a one-off project that goes stale.
The people who hold the knowledge also tend to find it a relief. Instead of being asked the same questions by every new colleague, they can point to something they checked themselves.
Is this the gap in your business?
- Key processes exist only in the heads of a few experienced people.
- Your written procedures are out of date or missing.
- New starters learn by shadowing rather than from anything written.
- You want to automate but cannot describe the process precisely.
- An audit or accreditation needs documented procedures you do not have.