Observable condition
Ask the operational teams what holds them back and a familiar answer emerges. The technicians are ready, but the job card has not been issued. The goods are packed, but the delivery paperwork is not done. The client has said yes, but the contract is still being prepared. The work is complete, but the invoice has not gone out. Across the business, things wait for the office.
The office, meanwhile, is working flat out. The administrators are not slow or careless; they are handling a volume of forms, approvals, checks, documents and exceptions that has grown steadily for years. Each new requirement, from a client's onboarding pack to a compliance form to an extra approval step, added a little more work. None was large enough on its own to trigger a rethink. Together they have made administration the narrowest point in the business.
An illustrative example: a Mpumalanga electrical contracting firm with about sixty staff found that its field teams could complete more jobs than the office could open, document and invoice. Each job needed a quote, a site safety file, a job card, materials requisitions, a completion certificate and an invoice with supporting documents, prepared largely by hand across several templates. During busy months, completed jobs waited for invoicing, and new jobs started late because their paperwork was not ready.
Realisation
Every business has a constraint: the step that limits how much the whole operation can produce. The Theory of Constraints Institute puts it plainly: every system has a limiting factor. In many service and project businesses, managers assume the constraint is skilled labour, equipment or sales. Over time, administrative complexity can quietly take that place.
When administration is the constraint, the usual signs of capacity problems appear in an unusual place. Work queues before the office rather than before the workshop. Lead times are set by paperwork, not by delivery. Hiring more technicians or salespeople produces little extra output, because they simply add to the queue. And the administrators themselves are overloaded, which the Lean Enterprise Institute calls muri: overburdening people beyond their natural capacity, which leads to errors and breakdowns.
Realisation prompt: in your business, where does completed or ready work most often wait, and who is it waiting for?
Identification
This is a pattern of an administrative constraint: the volume and complexity of paperwork, approvals and coordination has become the factor that limits the business's total output. The visible symptom is work waiting for the office while other teams have spare capacity. The common assumption is that the office is understaffed. The structural cause is accumulated administrative complexity, in the form of too many steps, templates, approvals, exceptions and manual checks per unit of work, concentrated in a small team.
It overlaps with when work sits waiting more than it moves, which looks at waiting time across a process. This Pattern looks specifically at administration as the limiting step, and at how complexity, rather than volume alone, creates that limit.
Diagnosis
- Steps accumulate without review. Each new form, approval or check is added for a reason, but steps are rarely removed, so the administrative content of each job grows over time.
- Work is assembled by hand. Documents are built from templates, previous files and copied information rather than generated from data already captured, so effort scales with each document.
- Approvals queue behind a few people. Where many documents need a manager's sign-off, the manager's availability sets the pace. The effect is explored in why approval processes become bottlenecks.
- Exceptions consume disproportionate time. A small share of jobs with unusual requirements can absorb a large share of administrative effort.
- Work arrives unevenly. Month-end, project milestones and seasonal peaks create surges. The Lean Enterprise Institute calls this unevenness mura, and it makes an already tight constraint fail at exactly the busiest moments.
- The constraint is invisible on reports. Operational dashboards track jobs, sales and revenue. Few track how long work waits for administration, so the constraint is felt but not measured.
Commercial impact
The commercial value at stake is capacity, revenue, cash flow and growth.
Capacity elsewhere in the business is wasted because it cannot be used until the administrative constraint releases work. Revenue is deferred or lost when jobs start late or quotes go out after a competitor's. Cash flow suffers directly when completed work waits to be invoiced, the condition described in the cash-flow cost of late invoicing. Growth is capped, because selling more simply lengthens the queue. Staff wellbeing and retention in the administrative team also suffer under sustained overload, which can tighten the constraint further when experienced people leave.
Common misidentification
The most common response is to hire another administrator. Sometimes that is the right answer, but if the complexity remains, the new person absorbs the current backlog and the constraint returns with the next increase in volume.
The other common mistake is to invest in the wrong part of the business. Adding sales capacity or field staff when administration is the constraint increases work-in-progress without increasing output. The Theory of Constraints Institute's five focusing steps put the order clearly: identify the constraint, exploit it, subordinate everything else to it and only then elevate it by adding resources.
Possibility
In a better state, the business knows administration is its constraint and manages it deliberately. The administrative team spends its time only on work that genuinely needs it. Documents are generated from data captured once. Approval rules are proportionate, with routine items pre-approved within limits. Exceptions are handled separately so they do not hold up standard work. Other teams provide complete information up front, so administrators are not chasing it. Waiting time for administration is measured and visible.
For the electrical contractor, that might mean a single job record from which the quote, job card, completion certificate and invoice are generated, with materials and safety information captured once by the field team on a mobile form, and invoices issued automatically when the completion certificate is signed off.
Intervention
- Confirm the constraint. Measure where work waits. If completed or ready work regularly waits for administrative steps, administration is likely the constraint.
- Count the administrative content of a typical job. List every form, document, approval and check from start to finish, and estimate the time each takes. Process mining tools, as IBM describes them, can reveal variations and bottlenecks from system logs where data allows.
- Exploit the constraint. Remove anything the administrative team does that does not need to be done, or does not need to be done by them. Move simple data capture to the people who generate the information.
- Subordinate the rest. Require complete information before work reaches the office, and smooth peaks where possible so the constraint is not swamped at month-end.
- Simplify and generate. Reduce templates, merge forms and generate documents from data already held.
- Elevate last. Only once the work has been simplified, decide whether more people or new systems are needed. The Insight how to decide what technology problem to solve first can help frame that choice.
Diagnostic questions
- Where does ready or completed work wait longest in your business?
- How many separate forms, documents and approvals does a typical job require?
- Would more salespeople or field staff increase output, or only lengthen the office queue?
- How much administrative effort goes on a small number of unusual jobs?
- Do you measure how long work waits for administration?
Bottom line
Administrative complexity becomes a capacity problem when paperwork, approvals and exceptions set the pace for the whole business. The office is overloaded, other teams wait and adding people elsewhere makes little difference. Recognising administration as the constraint, removing unnecessary work from it, generating documents from data captured once and only then adding capacity restores the business's ability to grow.
Sources and further reading
- Five Focusing Steps, a Process of On-Going Improvement (last verified 10 October 2026)
- Muda, Mura, Muri - Get a Quick Introduction - Lean Enterprise Institute (last verified 10 October 2026)
- What is Process Mining? - IBM (last verified 10 October 2026)
Related Mellorca reading
- When Manual Exceptions Become the Normal Process
- When Copy-and-Paste Becomes Part of the Job Description
- Why High-Value Employees Become Human Middleware