The cost of undocumented processes

Key takeaways

The cost of undocumented processes is the time, errors and risk that come from work existing only in people's heads. Each person does the task differently, new starters take longer to learn, questions interrupt others, and when someone leaves, the method goes with them.

• Undocumented work is done differently by each person, every time.
• 15 minutes of questions a day is about 57 hours a year per person.
• The biggest cost arrives when the person who knows it leaves.
• Start with the 5 processes that would hurt most if they stopped.

What is an undocumented process?

An undocumented process is a recurring piece of work with no written description of how it should be done. The knowledge is real, but it is held by individuals. A documented process, often called a standard operating procedure, sets out the steps, the standard and what to do when something goes wrong.

• The hidden costs of doing everything in-house
• Key person dependency: when one person holds it all

What does it cost day to day?

Day to day it costs questions, inconsistency and slow training. If each person spends 15 minutes a day asking or answering how to do something, that is about 57 hours a year each. At a loaded £19.81 an hour, a team of eight loses roughly £9,000 a year.

Inconsistency costs more quietly. Customers receive different answers depending on who they reach, and errors cannot be traced to a cause because there is no standard to compare against.

• The cost of poor quality in a small business

What does it cost when someone leaves?

When someone leaves, an undocumented process must be rediscovered. The replacement learns by trial and error, colleagues reconstruct steps from old emails, and some tasks are simply missed until a customer or supplier complains. Notice periods are usually too short to capture years of unwritten habit.

• Employee handover checklist for small teams

How do you document without it taking over?

Document the few processes that matter most, in the lightest form that works. One page each is enough to start.

• List processes and rank by what breaks if they stop.
• Have the person who does the task record or narrate it once.
• Write the steps, the standard and the common exceptions.
• Get someone else to follow it and fix the gaps.
• Store it where the team already works, and date it.

• Document your processes before you outsource

When is documentation not worth it?

Documentation is not worth it for one-off tasks, for work that changes every time, or for judgement that cannot be reduced to steps. Document the routine around the judgement, not the judgement itself.

Which processes should you document first?

Rank processes by two questions: how bad is it if this stops, and how many people can do it today? Anything critical that only one person can do goes to the top.

• Payroll and paying suppliers.
• Raising invoices and month-end close.
• Handling a new enquiry from first contact to quote.
• Onboarding a new customer.
• Backups, renewals and system administration.

• The cost of missed deadlines for a small business

What does good documentation look like?

Good documentation is short, current and findable. One page per process is usually enough: what triggers it, the steps in order, what a correct result looks like and what to do in the two or three common exceptions. Screenshots or a short screen recording help more than long paragraphs. Put the date and the owner's name at the top.

Store it where people already work, such as the shared drive or the task tool, not in a manual nobody opens.

What does it cost to write?

Writing a one-page procedure takes one to two hours, including a test by a second person. Five critical processes therefore cost about a day of staff time, roughly £150 to £250 at typical loaded rates. Set against the hours lost each year to questions, inconsistency and rediscovery, it is one of the cheapest fixes available to a small business.

What mistakes do businesses make when documenting?

The usual mistakes are trying to document everything at once, writing long manuals nobody opens, describing how the process should work instead of how it does, and never testing the document with a second person. Start with five processes, keep each to a page, and treat the first version as a draft that the next person to use it will improve.

What does this look like in practice?

A pattern we see at month end: one person closes the books using a sequence nobody else knows. They have not taken a holiday in the last week of any month for years. Writing the sequence down takes two hours and removes the constraint.

• See client work
• BPO Solutions for UK businesses

Process documentation checklist

Aim to finish this in a month.

• List your recurring processes.
• Mark the five most critical.
• Write one page for each.
• Test each with a second person.
• Set a yearly review date.

• The hidden cost audit: score your business in an hour

Next step

Tell us which process would hurt most if its owner were away for a month. We will show you a one-page format for it in a 30-minute call.