Delegation of Authority · Approval System
Delegation of Authority & Approval Matrix
What is delegation of authority?
- A table that sets the final decision-maker by matter and amount
- It directly determines how fast your organization makes decisions
- When accountability is unclear, no one signs off on their own
What revising a delegation of authority policy actually changes is not leaders’ attitudes but the time it takes one document to pass through the company. The same KRW 3 million (≈ US$2,240) purchase takes half a day if it is settled at the team lead level, and four days if it goes up to the CEO. So this work is less an organizational culture project than a redesign of how long work takes to get processed, and the moment you move one cell down a level, every document of that type speeds up by the same amount.
When filling in the table, the most common confusion is among final approval, consent, and reporting. Final approval means the document is closed out at that job level; consent means related departments must agree before it proceeds; and reporting means informing others after execution. Adding consent departments creates the same delay as adding approval lines. Three or four amount tiers are enough. To set the cutoffs, lay out last year’s transaction records and aim for 70–80% of transactions to fall in the team lead’s approval tier. Upper tiers have few transactions, so even if the CEO reviews them personally, they do not become a bottleneck.
The boundary between delegation of authority and internal control also needs to be clear. Handing down approval authority does not hand down accountability, so the side that delegates must put in place a way to review decisions after the fact. Often it is enough to pull a monthly list of delegated approvals, sorted by amount. Increasing after-the-fact review as much as you reduce advance approval is the precondition for delegation, and without this pairing, the proposed revision usually falls apart under opposition from finance.
The most common failure in practice is revising the internal policy while leaving the approval-line templates in the e-approval system untouched. If the policy says team leads have final sign-off but the system still names the CEO as final approver, nothing changes. The habit of adding the CEO as a cc “because it is an important matter” has the same effect. A bigger risk is split orders to get around limits, such as breaking a KRW 12 million (≈ US$8,980) construction job into three KRW 4 million (≈ US$2,990) orders. When you revise, add a 30-day cumulative threshold for the same vendor and the same matter. And if you do not set a deadline for post-approval of urgent cases, verbal approvals harden into habit, and when something goes wrong you cannot identify who approved it.
Hwi KimCEO of HRDIST & Talent Development Systems Consultant
John KimJohn Kim, author of B2B Marketing Design and CEO of Nanum ConsultingAs organizations grew and the CEO could no longer make every decision, a management principle of distributing authority by level took hold. In Korean companies it became a formal internal policy, the delegation of authority regulation. Electronic approval systems have made the documented approval process easier to record and trace.
This is the story of Company A, an industrial parts distributor with 140 employees and KRW 48 billion (≈ US$35,912,000) in annual revenue. Hitting client delivery deadlines is critical for them, yet even a KRW 3 million (≈ US$2,240) consumables order had to go up to the CEO for approval, taking four days on average. Sales kept saying, 'By the time we quote and place the order, a competitor has already delivered.' In Q2, the business support team revised the eight-year-old delegation of authority policy. (Hypothetical example)
- The head of Business Support measured the time from submission to final approval for 1,842 e-approval documents from the past three months. The average was 3.8 days, and purchase documents alone averaged 5.2 days.
- The CEO was handling 210 approvals a month, 68% of them consumables and travel expenses under KRW 3 million (≈ US$2,240). After seeing the report, the CEO backed the revision, saying, 'Why was I even looking at these?'
- The task force raised purchasing approval limits to KRW 3 million (≈ US$2,240) for team leads and KRW 30 million (≈ US$22,400) for division heads, and cut the three-department consultation process down to one: the finance team.
- When the finance team lead pointed out a control gap, the company added a monthly review of delegated approvals and a 30-day aggregate threshold per vendor, which stopped orders from being split.
- For urgent cases, they required a written request within 48 hours of verbal approval, and added a clause suspending a team’s urgent-approval authority for the following month if it misses the deadline.
- Three months after the revision, re-measuring the same metrics showed average approval time down from 3.8 to 2.1 days, CEO approvals down from 210 to 74 per month, and purchase-order lead time shortened by 1.9 days.