Nobody decides to build a business that spends a fifth of its week on admin. It accumulates. A form is added after one bad incident. A weekly report is requested once and never cancelled. A new system is introduced alongside the old one. Each addition is reasonable on its own, and each takes a few minutes. Across a team of ten, those minutes become a standing workload that no one planned, budgeted or can easily see.
This article explains how repetitive admin builds up, why it is so hard to notice, and how to start reversing it before it becomes the reason you hire another person.
Admin rarely grows because of one big decision. It grows because adding a step is easy and removing one needs someone to own the decision.
The accumulation mechanisms
Steps are added after incidents and never retired
After a payment goes to the wrong supplier, a second approval is introduced. After a missed deadline, a tracking spreadsheet appears. The control made sense at the time. Two years later the original problem has been fixed in another way, but the step remains because nobody remembers why it exists and nobody is asked to review it. Over time, the process becomes a record of past incidents instead of a design for current work.
New tools are added without old ones being switched off
A team adopts a new system but keeps the old spreadsheet "just in case". Now two places need updating. This is the pattern described in how duplicate software creates duplicate work, and it often goes unnoticed because each update is quick. Multiply by the number of people and the number of days, and the cost is real.
Information is re-entered between systems
When systems do not share data, a person becomes the connection. Details from an email go into the CRM, then into the quoting tool, then into the accounting package. We examine this in why copying data between systems is more expensive than it looks. Because the work is spread across many people, no one sees the full total. Each person experiences it as a small annoyance.
Reports and updates are requested but not retired
Someone asks for a weekly status update. It becomes a Friday habit. The person who asked has left, but the update continues, and nobody dares to stop sending it. Management information collected by hand tends to outlive its audience, a problem related to why your team keeps chasing information.
Growth adds volume faster than structure
A process designed for 20 orders a week is stretched to 200. It still works, but only because people absorb the extra effort. The business adds headcount to carry the load instead of redesigning the process, a dynamic explained in why growth breaks systems that worked when the business was smaller.
Workarounds become standard practice
When a system does not quite fit, people invent a workaround. The workaround is copied by colleagues, then taught to new starters as the correct way to work. The cost is invisible because it is now simply "how we do it", a sign described in why repeated workarounds are a warning sign.
Why it stays invisible
Three features keep accumulated admin out of sight.
- It is fragmented. Five minutes here and ten minutes there, divided across many people, never appears as a single line item.
- It is not tracked. Time sheets record projects and clients, not the invisible work of reconciling, re-keying and chasing.
- It is personally absorbed. Capable people compensate quietly, working through lunch or in the evening. The business sees the output and not the effort behind it.
The scale is often underestimated. A useful way to think about it is through the idea of a constraint: in Goldratt's theory of constraints, the performance of a system is limited by its tightest point. When admin consumes the time of the people who also do the valuable work, such as your best salesperson or your most experienced technician, it effectively becomes the constraint on the whole business. The Theory of Constraints Institute describes the five focusing steps as a way of identifying that limit and deciding how to relieve it.
How to measure it without a big project
- Run a one-week log. Ask each team member to note, in a shared sheet, every repetitive task they do and roughly how long it takes. Keep it to a simple list with a task name, minutes and frequency. Do not ask for precision.
- Group the entries. Look for the same task appearing under different people. Those are the ones accumulating across the team.
- Multiply. Weekly minutes times people times 46 working weeks gives an annual figure. Convert to Rand using a loaded hourly cost. The method is covered in how to calculate the real cost of a repetitive task.
- Look at the gap. Compare the total with what you thought the team's admin load was. The difference is usually the surprise.
More ideas for finding this work are in how to find the manual work nobody is measuring and how much manual work is hiding inside your business.
What to do once you can see it
Sort each recurring task into one of four buckets.
- Stop. The step exists for a reason that no longer applies. Remove it, and tell people it has gone.
- Combine. Two reports, two lists or two checks cover the same ground. Merge them.
- Fix at the source. The task exists because information arrives incomplete or in the wrong place. Improve the form, field or handoff so the task disappears.
- Automate. The task is stable, frequent and rule-based. Only after the first three should this bucket be considered.
The order matters. Many businesses jump straight to automation, and end up automating steps that should have been removed. The distinction between necessary and avoidable work is drawn in the difference between necessary human work and avoidable manual work.
An illustrative example
The following is a hypothetical case. A Bloemfontein accounting practice with twelve staff feels permanently behind despite steady client numbers. A one-week log shows seven different people each spend between two and four hours a week on tasks that include re-typing client details from engagement letters into the practice system, compiling a weekly status email for partners, and manually checking that SARS correspondence has been filed against the right client.
Totalled, the log comes to about 45 hours a week, close to a full extra person. Reviewing the items, the practice stops the weekly email because partners can read the same status in the practice system, merges two overlapping tracking spreadsheets, and changes the onboarding form so client details are captured once and flow into the system. Roughly a third of the load disappears without any new software, and the partners stop asking for another administrator.
Keeping it from coming back
Admin builds up again unless the habits that created it change. Three practices help.
- Attach an owner and a purpose to every recurring task. If nobody can say who uses a report, it should not be produced.
- Review quarterly. A short session asking which recurring tasks still earn their time is enough.
- Treat every new step as a trade. When a control or report is added, ask what it replaces.
Accumulated admin is not a sign of a weak team. It is the cumulative result of reasonable decisions without a mechanism for removal. Building that mechanism is among the highest-value things a manager can do, because it returns capacity to the business without recruiting anyone.
Sources and further reading
- Five Focusing Steps, a Process of On-Going Improvement (last verified 10 October 2026)
- Value Stream Mapping Overview - Lean Enterprise Institute (last verified 10 October 2026)
- Measure and communicate the business value of Power Platform solutions - Power Platform (last verified 10 October 2026)
Related Mellorca reading
- How Bad CRM Data Gets Created
- How to Find the Real Bottleneck in a Digital Operation
- Why Work Gets Lost Between Teams