The Founder Approval Audit: What Should Still Need You?

A capable team can still become highly dependent on the founder when the business has never defined which decisions can move without approval.

The symptom is easy to recognise. Messages arrive throughout the day asking you to check, confirm, review or decide. Each request may take only a few minutes, but together they interrupt strategic work and slow the team while it waits.

This is not always a confidence problem. It is often a decision-design problem.

Why approvals keep returning

Approvals usually return for one of four reasons:

• the decision genuinely affects direction, risk, revenue or a key relationship

• the quality standard has not been made clear

• the situation falls outside the normal process

• the founder has always approved it, even though the business no longer needs that structure

The approval audit makes those reasons visible.

How to complete the audit

For five working days, record every request for founder approval. Do not change the process yet. Capture what the decision was, who brought it to you and what would have happened if you were unavailable.

Then place each request into one of four categories.

Direction

These decisions change an offer, client relationship, financial commitment, legal or reputational risk, or a strategic priority. They may rightly remain founder-led.

Standard

These decisions should be made against an agreed quality standard. The team may need a checklist, example, brand guideline, budget limit or definition of “done”.

Exception

These situations fall outside the usual process. The team needs an escalation rule: what makes the situation exceptional, who should be involved and how quickly a decision is required.

Habit

These requests come to the founder because they always have. There may be no current operational reason for the approval to remain.

What to change first

Begin with Habit. Reassign the decision clearly and communicate what ownership now includes.

Then review Standard. Ask what the team would need in order to make the same quality decision without waiting. Build that into the process.

For Exception, document the trigger and the expected escalation pathway.

Keep Direction decisions visible and intentional. The goal is not to remove the founder from every decision. It is to protect founder attention for decisions that genuinely require leadership judgement.

Delegation needs decision rights

Delegating a task without delegating any of the decisions inside it creates only partial ownership. The team can begin the work, but the founder remains responsible for moving it across the finish line.

Clear decision rights explain:

• the outcome the person owns

• the decisions they can make

• the standards they should use • the exceptions they should escalate

• where the final decision is recorded

This is what turns task support into operational capacity.

If your team is capable but approvals still fill your day, our Breathe & Discover Call is a place to look at the structure behind it. We can identify whether the next step is clearer processes, OBM oversight, additional VA capacity, stronger systems or a connected mix of support.