What it means
The formal concept comes from the sociologist Max Weber, who described bureaucracy as a system of hierarchy, written rules, specialised roles and impersonal decision making. Its purpose was to replace favouritism and improvisation with something predictable.
Every approval matrix, expenses policy and delegated authority schedule in a modern company is a descendant of that idea. The benefits are genuine and easy to forget when you are waiting for a signature.
Written procedures mean that a task survives the departure of the person who invented it, that two customers in similar situations get similar treatment, and that an auditor can see who approved what and when. In regulated sectors these features are not optional extras but legal requirements.
The costs are equally real and are usually paid in time and attention. Every additional approver adds delay, consumes management hours and dilutes accountability, because when six people sign something, nobody feels responsible for it.
Slow internal processes also have an invisible cost: the good ideas that are never proposed because the process is exhausting. The way to manage this is to scale control to risk rather than applying one rule to everything.
A $400 software subscription and a $4,000,000 factory purchase do not need the same approval chain, and a sensible delegated authority schedule reflects that with rising thresholds. Reviewing which controls still earn their place is a normal part of good financial management.
Bureaucracy also grows quietly, because each rule is usually added in response to a specific incident and almost none are ever removed. A useful discipline is to attach a review date to new procedures, and to ask periodically which rule is still preventing which risk.
Anything that cannot answer that question is administration rather than control.
In practice
Real-world examples.
Example
A bank runs a five stage client onboarding process that takes eleven working days, covering identity checks, sanctions screening and source of funds review. Commercial staff find it frustrating, but each step exists because a regulator requires it. Here the bureaucracy is the cost of holding a banking licence, not waste.
Example
A software scale-up that grew from 20 to 200 staff introduces a rule that any spend above $500 needs approval from the chief financial officer. Within a year that one person is reviewing dozens of small requests a week and has become the bottleneck for routine purchases. The threshold was set for a much smaller company and was never revisited.
Example
A hospital trust requires three written quotes for any purchase above $25,000 to demonstrate fair use of public money. For unusual specialist equipment with only one supplier, the rule produces weeks of delay and two token quotes that nobody takes seriously. The procurement team introduces a documented single-supplier exception to keep the control meaningful.
Formula
Calculation
Annual cost of an approval step = Number of requests x Approvers per request x Hours per approver x Loaded hourly cost
Worked example: a mid-sized company processes 1,200 purchase requests a year. Each request needs 4 approvers, each spends 30 minutes reviewing and signing, and the loaded cost of an approver's time is $90 an hour.
Approver hours per request = 4 x 0.5 = 2 hours
Cost per request = 2 x $90 = $180
Annual cost of the approval process = 1,200 x $180 = $216,000
The finance director proposes reducing the chain to 2 approvers for requests under $10,000, which covers 900 of the 1,200 requests, while keeping 4 approvers for the remaining 300 larger items.
Small requests = 900 x 1 hour x $90 = $81,000
Large requests = 300 x 2 hours x $90 = $54,000
New annual cost = $81,000 + $54,000 = $135,000
Annual saving = $216,000 - $135,000 = $81,000Case study
Seen in the real world.
Halden Instruments is a fictional and purely illustrative maker of laboratory equipment whose capital expenditure process had grown to nine sequential approval steps. The process had been designed after an expensive machine purchase went wrong a decade earlier, and each subsequent incident had added another signature.
By the time engineers wanted to replace a worn testing rig, the average approval cycle was 34 days for items of any size. Production managers had started splitting purchases into smaller pieces to stay under thresholds, which defeated the control entirely and made spending harder to see rather than easier.
The finance director rebuilt the schedule around risk. Purchases under $50,000 dropped to four steps and averaged nine days, while anything above $250,000 kept the full chain and gained a proper business case template. The illustrative outcome was faster routine decisions and, because the splitting behaviour stopped, better visibility of exactly the large commitments the original rules had been written to catch.
Watch out
Common mistakes.
- Treating all bureaucracy as waste, and removing controls that exist to prevent fraud, satisfy regulators or provide evidence for auditors.
- Adding an approval step after every incident without ever removing one, so the process accumulates layers that no longer match the risks.
- Applying the same approval chain to a $400 purchase and a $4,000,000 purchase, which wastes senior time on trivia while barely improving control of the large item.
Questions
People also ask.
How do you tell useful control from pointless bureaucracy?
Ask what specific risk the step prevents, how often that risk has actually materialised, and whether a later check would catch it more cheaply.
Does more approval mean more accountability?
Usually the opposite, because responsibility becomes diffuse when many people sign, whereas a single clearly named approver with a defined limit tends to review more carefully.
Is bureaucracy always a sign of a large organisation?
No, small companies can be heavily bureaucratic if rules pile up, and large ones can be fast where authority is clearly delegated and thresholds are sensible.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%