Why Routine Admin Expands as the Business Grows

Observable condition

As organisations scale, routine administrative work—onboarding, approvals, data entry, expense processing, and compliance checks—tends to proliferate. What began as a handful of quick handoffs becomes a maze of handoffs, forms, and gates that slow decisions and dilute accountability. Frontline teams experience friction not because people are unproductive, but because the supporting scaffolding for coordinating activities grows in tandem with headcount, product lines, and geographic reach. In many firms, this manifests as duplicate forms, multiple approvers with overlapping authority, and siloed data trails that require manual reconciliation.

Realisation

Growth creates complexity, and complexity invites process toggle-switches. Without deliberate governance, each department reflexively builds its own routines to cope with volume, urgency, and risk. The consequence is a drift from a shared operating model toward a constellation of ad hoc routines. The realisation is not that people are failing; it is that the supporting processes have not kept pace with the scale and cadence of the business. The signal is consistent: longer cycle times, wasted rework, and a blurry line between what is essential versus what is ritualised to appease multiple stakeholders.

The most expensive version of this is when the business responds by hiring. Each new administrator absorbs the overflow for a while, but the underlying routines remain, so admin headcount tracks revenue rather than flattening. We look at that dynamic in why revenue growth requires more admin staff and its financial effect in the cost of scaling by adding headcount.

A worked example

A Pretoria-based facilities maintenance company grows from 30 to 120 employees over four years, opening branches in two more provinces. At 30 people, a new technician was onboarded by the office manager in an afternoon: a form, a phone, a vehicle allocation. At 120, onboarding involves an HR form, a separate payroll form that repeats half the same fields, a vehicle request emailed to fleet, a tools request on paper at the branch, a safety induction tracked in a spreadsheet, and system access requested by message to the IT contractor. Each branch has slightly different versions. New technicians regularly wait days for a vehicle or system access, and three different people re-key the same name, ID number and banking details. Nobody designed this; every step was added to solve a specific problem at a specific time.

Identification

Primary identification: administrative overhead growth accompanying business expansion; proliferation of roles and systems without centralised governance; lack of a shared data model and standard operating logic across functions.

Warning signs worth watching for:

Staff regularly ask who needs to approve something, or approve "to be safe"; see when staff need to ask who approves what.
The same person's or supplier's details are captured on more than one form.
Branches or departments run the same routine in visibly different ways.
Requests are tracked in inboxes, and status checks are done by phone.
Admin roles are added after each growth spurt, but nobody can say which tasks they removed.

Diagnosis

Root mechanisms: the diagnosis centres on governance gaps and information fragmentation. When onboarding, approvals, and record-keeping rely on dispersed tools, you gain local effectiveness at the expense of global visibility. Data becomes inconsistent, handoffs multiply, and the same information is rekeyed across systems. The diagnosis also implicates human factors: unclear ownership, incomplete handbooks, and inconsistent training that allows local routines to persist unchallenged. Effective diagnosis requires mapping the real workflows end-to-end, identifying bottlenecks, and clarifying who owns which data at which stage of a process.

Mapping the real workflow is where most efforts go wrong, because the map drawn in a workshop reflects how people believe the process works. Where systems record events, process mining can help: it extracts event data from systems of record to visualise how processes actually run, identify bottlenecks and determine root causes of inefficiency. Where data is thin, a simpler method works: follow five real cases from start to finish, recording every form, approval, wait and re-entry.

It also helps to separate three kinds of step:

Step type	Example	Typical action
Judgement	Approving an unusual expense	Keep, clarify who decides
Control	Checking a supplier's bank details	Keep, standardise, record evidence
Transport	Re-keying a name into a second system	Remove or automate

Commercial impact

The commercial value is clear: admin bloat raises cost, reduces speed to market, and increases risk of noncompliance. Cycle times lengthen as approvals cascade through more hands, burdens shift to growing teams rather than product development, and data quality degrades when information is held in silos. The impact ripples to customer experience if delays in order processing, vendor onboarding, or expense reimbursements translate to slower response times or misaligned commitments. Conversely, disciplined governance can restore velocity and improve decision quality, enabling scale without sacrificing control.

In the maintenance company above, each day a new technician waits for a vehicle is a day of paid time that cannot be billed, which is a direct and measurable cost. The broader reasons that systems which worked at smaller scale stop working are covered in why growth breaks systems that worked when the business was smaller.

Possibility

Opportunity window: there is a real possibility to align routine admin with growth through a small set of governance levers: map end-to-end processes, standardise data definitions, and create a centralised admin capability with clear ownership. By introducing common templates, single sources of truth for key records, and an accountable governance cadence, a growing business can preserve speed while improving accuracy.

Intervention

Practical steps:

Create a lightweight Admin Governance Charter with clearly defined owners and decision rights across onboarding, approvals, and data management.
Map core administrative workflows end-to-end and identify non-value-adding steps to remove or automate.
Introduce a shared data model and common forms/templates to reduce rekeying and reconcile records in a single system of truth.
Consolidate redundant tools into a standardised stack or a central administrative hub (shared services or a single owner for procurement, HR, and finance tasks).
Adopt a RACI-like framework to clarify ownership for data, approvals, and records, with regular governance reviews.
Invest in automation for repetitive tasks (routing, notifications, approvals) while preserving human oversight for exception handling.
Establish a simple measurement set: cycle time, rework rate, data quality, and cost per administrative transaction.

On approvals specifically, be deliberate about the rule, not just the routing. Workflow tools such as Power Automate support different approval patterns, for example requiring everyone to approve, accepting the first response, or sequential approval in a set order. Each choice has a different effect on cycle time. Requiring everyone where one accountable approver would do is a common source of delay; see why approval processes become bottlenecks.

Trade-offs

Centralising admin can create a new bottleneck if the central function is under-resourced, and standard templates can frustrate branches with genuinely different needs. Allow controlled variation where the business reason is real, and document it. Automation also has limits: automating a badly designed routine simply makes the bad design run faster, so remove unnecessary steps first.

Practical diagnostic questions

Which admin steps do not uniquely require human judgement, and can be automated or templated?
Where do data definitions diverge across departments, causing rework?
Who owns the master data for core admin records (employees, vendors, contracts)?
What is the longest-running admin bottleneck, and which step causes it?
How many tools are used to perform a single routine task, and is there overlap?

What to do first

Choose the one routine that touches the most people, often onboarding or supplier set-up.
Follow five recent cases end to end and count re-entries, approvals and waiting days.
Agree one owner and one intake form for that routine.
Remove the transport steps before automating anything.
Measure cycle time before and after, then move to the next routine.

Bottom line

Routine admin expansion is a natural corollary of growth, but it is not an inevitability. By defining governance, standardising data, and selectively automating, a growing business can maintain velocity while improving accuracy and resilience.

Sources and further reading

Overview of process mining in Power Automate - Power Automate (last verified 10 October 2026)
Get started with Power Automate approvals - Power Automate (last verified 10 October 2026)