Accountability Framework: How to Build One That Works

An accountability framework is the set of agreements that tells everyone in your business who owns which outcome, what decisions they can take alone, how progress is checked and what happens when something slips. It has four working parts: an accountability chart, a delegation matrix, a measure for each role and a regular rhythm of review. This guide shows how to build each part for a small or mid-sized UK business, with a worked example you can copy.

A note on scope. Searching this phrase also returns formal schemes, such as the Department for Education’s framework for apprenticeship training providers and the supply chain framework for forests and human rights. Those are regulatory or sector standards. This article is about the internal kind: how a founder-led or growing business makes ownership clear.

TL;DR

• An accountability framework answers four questions: who owns the outcome, who can decide what, how it is measured and when it is reviewed.
• Build it in this order: outcomes, accountability chart, delegation matrix, measures, review rhythm. Skipping straight to meetings or software is the usual failure.
• One person is accountable for each outcome. Several can be responsible for the work, but accountability is never shared.
• CIPD data links clear objectives, monitoring, feedback and accountability with better self-reported performance, but it works best as a dialogue, not an audit.
• You can have a first working version on one page within a week.

Table of Contents

• What an accountability framework is, and what it is not
• Why smaller businesses feel the gap first
• Step 1: write down the outcomes
• Step 2: draw the accountability chart
• Step 3: build the delegation matrix
• Step 4: attach a measure to every role
• Step 5: set the review rhythm
• A worked example: a 12-person recruitment firm
• How to delegate work so it stays delegated
• Common mistakes
• Our perspective
• How we can help
• FAQ
• Sources

What an accountability framework is, and what it is not

It is not a blame mechanism. When people hear “accountability” they often hear “who gets in trouble”. A framework built that way produces defensive behaviour: people avoid ownership, hide problems and wait for instructions. A good framework does the opposite. It makes ownership explicit so that problems surface early and the owner has the authority to fix them.

It is not a performance appraisal scheme either, though the two connect. Appraisals look at an individual over a period. A framework describes how the business as a whole assigns and checks ownership, week by week.

In practice it is made of four pieces:

1. Outcomes. What the business needs to be true, written so that you can tell whether it is.
2. Ownership. Who is accountable for each outcome, shown on an accountability chart.
3. Decision rights. What each owner can decide, and what they must consult on or escalate, shown in a delegation matrix.
4. Review. The measures and meetings through which you see progress and correct course.

If one is missing, the others weaken. Owners with no decision rights wait for permission. Decision rights with no measure cannot be judged. Measures with no review are just a spreadsheet.

Why smaller businesses feel the gap first

In a team of five, ownership is informal and works because everyone sits within earshot. Somewhere between ten and thirty people that stops working. The founder is still the default owner of everything, new managers are unsure what they may decide, and two people each assume the other is handling a client issue.

The symptoms are consistent:

• The founder is copied into every decision and is the bottleneck for approvals.
• Work gets done twice, or not at all, because nobody is sure whose it is.
• Managers pass things upwards instead of deciding.
• Reviews happen once a year and surprise everyone.
• Delegation keeps failing: work comes back half-done and gets taken back by the founder.

That last symptom is the one most owners recognise. The cause is rarely the person’s ability. It is usually that the outcome, the boundaries and the check-in points were never stated.

Step 1: write down the outcomes

Start with what the business needs, not with job titles. List the five to ten outcomes that matter over the next twelve months. Phrase each as a result, not an activity.

• Weak: “Do marketing.”
• Better: “Generate 25 qualified enquiries a month from target sectors.”
• Weak: “Look after clients.”
• Better: “Retain at least nine in ten clients at renewal.”

The figures above are examples of the format, not benchmarks. Use your own numbers, drawn from what you currently achieve and what you are aiming for. If you do not yet have a growth plan to anchor them, our guide to building a growth roadmap that gets delivered covers how to set them.

Step 2: draw the accountability chart

An accountability chart looks like an organisation chart but answers a different question. An org chart shows who reports to whom. An accountability chart shows which function exists, who owns it and which roles sit inside it. Two rules make it work.

One owner per function. A function can have many contributors, but one name sits against it. If you cannot choose between two people, the function is probably two functions, or the decision about who leads has not been made.

Structure first, names second. Draw the functions your business needs now, then place people. Otherwise the chart ends up mirroring existing personalities and the awkward gaps stay hidden.

For a 15-person professional services firm, the functions might be:

The common finding at this stage is that one person, usually the founder, holds three or four seats. That is not a failure. It is information. You now know which seats to hand over first, and which hire or promotion would release the most capacity.

Step 3: build the delegation matrix

The chart says who owns what. The delegation matrix says how far each owner can go without asking. The most widely used format is the responsibility assignment matrix, often called RACI. Each task or decision is a row, each person or role a column, and each cell holds one of four codes: Responsible, Accountable, Consulted or Informed.

• Responsible: does the work.
• Accountable: owns the result and has the final say. One per row.
• Consulted: gives input before the decision, two-way.
• Informed: is told afterwards, one-way.

A matrix of this kind can become heavy, so keep it to the decisions that cause friction. Here is an example for a small consultancy:

The 10% and £500 thresholds are placeholders. Set limits that suit your margins and your risk appetite. The point is that thresholds turn vague trust into a rule people can act on. A delivery lead who knows she can adjust scope up to a stated limit will do so, without a message to the founder.

Three levels of delegation

Many owners find a simple three-level scale easier than a full matrix when they first start:

1. Decide and tell me. The person acts and informs you afterwards.
2. Recommend, then act. The person proposes a course and goes ahead unless you object.
3. Ask first. You decide. Reserve this for decisions that are expensive, irreversible or reputational.

Write the level next to each recurring decision. Revisit it every quarter. As someone proves reliable, move decisions from level three to two to one. That progression is what delegation actually is: a sequence of widened boundaries, not a single handover.

Step 4: attach a measure to every role

Each accountable role needs one to three measures that show whether the outcome is on track. More than three and nobody remembers them.

Good measures share three traits:

• The owner can influence them. Judging a delivery lead on the founder’s sales figures is unfair and demotivating.
• They move often enough to review. A measure that changes once a year cannot support a weekly conversation. Pair a lagging result (renewals) with a leading indicator (client check-ins completed).
• They are simple to collect. If gathering the figure takes a day, it will stop being gathered.

Be wary of tying measures straight to pay. CIPD’s analysis notes that performance-related pay often makes little difference to performance, health or wellbeing, while regular, constructive conversations between manager and employee have a clear positive effect. If you have limited budget, investing in managers’ ability to hold those conversations will usually return more than adjusting bonus schemes.

Step 5: set the review rhythm

Ownership that is checked once a year is not accountability. It is an annual surprise. The framework needs a rhythm short enough that a missed target is seen while it can still be fixed.

A workable pattern for a small business:

Our article on how often each meeting should happen goes through the purpose and agenda of each, so that you do not simply add meetings. When something does go wrong, an after action review lets you learn from it without turning the conversation into a hunt for fault.

Keep the tone developmental

The CIPD’s research with the UK Civil Service points to a strengths-based approach, in which managers concentrate on how people can improve rather than only auditing the past. Its earlier review of what works found that forced distribution ratings reliably generate negative reactions, and that employee voice in appraisal discussions and a focus on future development are more productive.

In a review meeting, that means asking three questions in order: what did you commit to, what happened, and what do you need to change or from whom? The third question is where most of the value sits.

A worked example: a 12-person recruitment firm

Imagine a founder-led recruitment business. The founder still approves every candidate shortlist, writes every job advert and handles every client complaint. Fees are healthy but she works evenings, and two consultants have said they feel they do not own their desks.

Outcomes chosen: placements per quarter, time to shortlist, client retention, and cost per hire.

Chart: the founder owns leadership and business development. A senior consultant becomes accountable for delivery. An office manager owns operations. Previously all three sat with the founder.

Matrix: shortlists are “decide and tell me” for the senior consultant. Adverts are “recommend, then act”. Client complaints with fee credits over a set value remain “ask first”. Where AI tools are used to screen or draft, that decision sits with the delivery owner, and our piece on where AI earns its place in recruitment is a useful basis for setting the rules.

Measures: time to shortlist and candidate-to-interview ratio for delivery; enquiries and win rate for business development.

Rhythm: a 15-minute Monday stand-up, a weekly measures review, and a monthly leadership session.

The result is not that the founder disappears. It is that her involvement moves to the decisions that need her, and everyone else knows where their authority starts and stops.

How to delegate work so it stays delegated

Most delegation fails at the brief, not at the execution. Before handing something over, state five things:

1. The outcome, in a sentence, including what good looks like.
2. The boundaries: budget, deadline, what is off limits.
3. The decision level from the scale above.
4. The check-in points, set in advance, not triggered by your anxiety.
5. The support available: who to ask, what information exists.

Then resist the urge to take it back. If the work is returned at the first stumble, the person learns that ownership is conditional. If it is returned with a conversation about what to try next, they learn that it is theirs.

Where the work spans customer-facing teams, ownership gaps are most costly at handover points. The customer lifecycle management guide shows how to name an owner for each stage, and the customer success playbook covers health scores that give those owners something concrete to track.

Common mistakes

Shared accountability. “Jo and Sam own this” means neither does. Name one, and make the other responsible or consulted.

Accountability without authority. If an owner cannot spend, hire, or change a process, they are only a messenger. Match the matrix to the chart.

Too many measures. Twenty indicators per role means none gets attention. Cap it at three.

Treating it as a one-off document. Roles change as the business grows. Review the chart and matrix quarterly.

Starting with tools. Software can hold a chart and track measures, but it will not decide who owns what. Agree it on paper first.

Using it to find fault. The first time someone is publicly blamed for a missed number, the data stops being honest. Keep reviews about learning and adjustment.

Our perspective

We work with small and mid-sized businesses and founder-led professional services firms, and the pattern we see is that accountability problems are really capability problems. The owner knows what needs to happen. The business lacks the structure, habits and skills to make it happen without them in the room.

That is why we build capability in stages instead of handing over a document. A framework on paper changes nothing. It starts to work when direction is clear, the first version is in use, it has been adjusted after real weeks of running it, and the habits are embedded so that the business keeps them when we are not there. Our own approach moves through Build, Iterate, Optimise, Embed and Grow for exactly that reason.

We would also say start small. One page, five outcomes, one chart, a handful of delegation rules and a weekly review will do more than a thirty-page policy. Then use it, notice where it chafes, and improve it.

— Chris

How we can help

If you want a working version of this in place without carving out weeks of your own time, our Foundation stage is designed to give you a launch-ready base in four weeks. You can read how we deliver a launch-ready Foundation and see the stages on how it works. Ongoing support is available through Managed Capability at £999 per month, £2,850 per quarter or £10,000 per year, and the full options are on our pricing page. If you would rather talk it through first, you can book a discovery call.

FAQ

What is the difference between an accountability chart and an org chart?

An org chart shows reporting lines. An accountability chart shows the functions the business needs, the single owner of each and the roles within it. It often reveals that one person holds several seats, which an org chart hides.

What is the difference between accountability and responsibility?

Responsibility is doing the work, and several people can share it. Accountability is owning the result and answering for it, and it sits with one person. In a RACI matrix these are the “R” and “A” respectively.

How long does it take to set up an accountability framework?

A first version, with outcomes, a chart, a short delegation matrix and a weekly review, can be drafted in about a week for a small business. Expect to refine it over the next quarter as you find where the boundaries are wrong. Treat the quarterly review as part of the framework, not an afterthought.

Do we need a delegation matrix if we only have a few staff?

Not a full one. If you have fewer than ten people, a list of eight to ten recurring decisions, each marked “decide and tell me”, “recommend, then act” or “ask first”, is enough. Expand it when decisions start to stall or people ask who can approve things.

Sources

• CIPD: Impact of performance management on employees
• CIPD: Performance conversations report
• CIPD: Could do better? Assessing what works in performance management
• Institute of Project Management: What is the responsibility assignment matrix

Recommended

• After Action Review: How to Run One That Changes Results
• AI Governance for Leaders: Five Stages to Put Principles to Work
• Judgement before execution