Andrew Ritson & Co. All articles
Operations & Technology

The Decision Waiting Room: Written Approval Limits for Founder-Led UK Firms

Andrew Ritson & Co.
The Decision Waiting Room: Written Approval Limits for Founder-Led UK Firms

Growth rarely breaks a UK owner-managed firm in one dramatic moment. More often, it slows it down. A client asks for a modest discount, a manager wants to order equipment, a contract needs a small amendment, and everyone waits for the same person to respond. The founder is not deliberately obstructive. The firm has simply never written down who can decide what.

That is the decision waiting room: the space between a reasonable request and a response that should have been routine. As headcount, client numbers and contractual complexity increase, the queue gets longer. The founder becomes a bottleneck, and the business becomes more dependent on one or two people than its growth justifies.

A delegation authority matrix is the antidote. It is not a lengthy governance manual. It is a short, practical schedule that sets out which roles may approve which decisions, at what value, and when a second signature is required.

The queue behind the founder

In a ten-person firm, the founder can reasonably sit in most decisions. At thirty or fifty people, the same habit becomes a constraint. Staff learn to escalate rather than exercise judgement. Clients experience delay without understanding why. Capable managers become frustrated, and the founder spends hours on matters that should never have reached their desk.

There is a risk dimension too. If only the founder can commit the business, approvals stop when the founder is travelling, unwell or absorbed in a transaction. Lenders, insurers and acquirers may ask who else can bind the firm. A culture of informal escalation is not a control system; it is a single point of failure with a diary.

A matrix, not a moat

The purpose of an authority matrix is to delegate decisions, not to remove the founder from the business. Material matters should still be reserved. The matrix simply distinguishes between decisions that need founder judgement and those that need a competent manager, a budget check and a clear audit trail.

It should be role-based rather than personality-based. The question is not whether a particular individual is trusted this month, but what the finance manager, operations director or client services lead is authorised to approve as part of the job. Consultation can be separated from approval: a manager may need to consult the founder, but the decision itself can still sit within a written limit.

Five areas to map

Most authority matrices can be built around five practical categories.

Spend and commitments

Set limits for operating expenditure, capital expenditure, software subscriptions, professional fees and purchase orders. Use annual or cumulative value as well as one-off value, otherwise a series of small commitments can bypass the threshold. Include an emergency route for urgent operational spend, with retrospective approval and a clear record.

Contracts

Define who may sign standard terms and who must refer non-standard terms for review. Triggers should include contract value, duration, renewal rights, termination rights, liability caps, indemnities, intellectual property, data protection and exclusivity. A low-value contract with an unlimited liability clause is not a low-risk contract.

Hiring and people

Cover new roles, salary offers, contractor engagements, settlement agreements and changes to working arrangements. Salary bands should link to budgeted headcount, not simply to the seniority of the person making the request. Where employment law advice is needed, the matrix should make that trigger explicit rather than leaving it to chance.

Pricing and commercial concessions

Pricing is where informal delegation often causes the most damage. A sales lead may be allowed to offer a small discount, but not to extend payment terms, waive a deposit or accept additional scope without approval. Set caps by percentage and absolute value, and require escalation where concessions become cumulative or where they affect a strategically important client.

Client commitments

Delivery dates, service levels, warranties, references and bespoke reporting can all become contractual commitments in practice. The matrix should identify who may promise what, and when a proposed commitment needs delivery, finance or legal review. This is particularly important for professional firms whose margins depend on scope discipline.

Thresholds that people can actually use

A common mistake is to make the matrix so detailed that no one consults it. Start with materiality, not hierarchy. A useful threshold combines value, risk and duration. A £5,000 purchase may be routine; a £5,000 contract with a three-year term and an uncapped indemnity is not.

A simple structure often works best. Front-line managers approve low-value routine matters. Senior managers approve within their budget and role. Above that, a second signature is required, typically from a finance lead, operations director or managing director. Reserved matters — borrowing, guarantees, major leases, equity changes, sale of the business or material brand commitments — remain with the founder or board.

The second signature should be substantive, not ceremonial. It should be recorded in the finance system, contract file or approval register, with the date, decision and basis. If an approval is given by email, it should be retrievable. The aim is not bureaucracy; it is a defensible trail that protects both the firm and the individual who made the call.

A 60-minute workshop

An authority matrix does not need a long consultation to get started. A focused session with the founder, finance lead, operations lead and a senior commercial representative can produce a workable first version.

Use the hour as follows. Spend ten minutes listing decisions that stalled in the previous quarter. Spend twenty minutes grouping them into the five categories above. Spend fifteen minutes agreeing thresholds and second-signature rules. Spend ten minutes naming approvers, backups and the exception route. Spend the final five minutes agreeing where the matrix will be stored, how exceptions will be logged and when it will be reviewed.

Bring examples, not principles. A list of real requests — a discount, a contract amendment, a contractor hire, a software renewal — will expose gaps faster than a theoretical discussion about governance.

Keep it alive

An authority matrix fails if it is signed once and filed away. It should sit alongside the finance policy, be embedded in approval workflows where possible, and be explained to new managers during induction. Key suppliers and regular clients do not need to see the document, but they should experience its effect: faster responses and fewer unexplained delays.

Review the matrix quarterly for exceptions and near misses. If managers are routinely escalating matters that should be within their authority, the thresholds may be too low. If exceptions are frequent in one category, the rule may be unclear. If no exceptions are ever recorded, the matrix may simply not be in use.

The test is straightforward. Can a competent manager commit the firm within a clear limit without chasing the founder? Can the founder see the exceptions that matter? If the answer to both is yes, the firm has delegated without losing control. If not, the decision waiting room is still open.

All Articles

Related Articles

Automate Less, Automate Well: A Five-Step Audit for UK Firms Weighing AI Admin Tools

Automate Less, Automate Well: A Five-Step Audit for UK Firms Weighing AI Admin Tools

The Renewal Trap: Seven Questions UK Firms Should Ask Before Another SaaS Contract

The Renewal Trap: Seven Questions UK Firms Should Ask Before Another SaaS Contract

Before the Administrator Calls: A Credit-Control Playbook for UK Professional Firms

Before the Administrator Calls: A Credit-Control Playbook for UK Professional Firms