Tiered Accountability Meetings

The meetings that make everything else possible.

Most organisations have too many meetings and not enough decisions. The same problems appear week after week. Actions are raised and not closed. The people closest to the work stop raising things because nothing moves.

Tiered Accountability Meetings are not more meetings. They are a different kind of meeting, short, structured, and connected. Each tier reviews what it needs to review, resolves what it can, and passes up what it cannot. The tier above removes what the tier below cannot remove. That is the whole system.

Done well, a problem raised at the line at 7am has a named owner and a close-out date before 10am. Done poorly, it is still on a list at the end of the week, if recorded at all.

What Tiered Accountability Meetings are

A tiered meeting system is a structured daily and weekly cadence that connects the levels of the organisation into a single information and decision flow. Each tier has a defined purpose, a defined agenda, a defined duration, and a defined escalation path. The tiers are interlocked: what cannot be resolved at one level moves to the next. Nothing sits without an owner.

The number of tiers depends on the size and structure of your organisation. A small single-function team may need two. A large multi-line manufacturing site typically needs four. The principle is the same at any scale: the meeting closest to the work is Tier 1. Each tier above it exists to support the one below.

This guide is in two parts. The first part explains what the system is, why each element matters, and how to design it for your site. The second part covers how to build it, step by step, with a clear output at each stage. If you are setting up the system for the first time, work through it in sequence. If you are reviewing a system that is already running, the audit standard in Step 7 is the most useful starting point.

For a multi-line manufacturing site — a recommended starting point:

The four-tier model below works well for a site with multiple production lines, a maintenance function, and a site leadership team. Use it as a starting point. Adjust the number of tiers, the names, and the attendees to reflect your actual structure.

Meeting design — consistent but not identical

All Tier 1 meetings across a site should follow the same format. Not because consistency is a goal in itself, but because a consistent format is what makes gaps visible.

If every Tier 1 meeting follows the same structure, same agenda sequence, same board layout, same action standard, then a leader attending any Tier 1 meeting anywhere on the site can immediately see what is working and what is not. They are not learning a new format. They are reading a familiar one. The gap stands out because everything around it looks the same.

A Tier 1 meeting in the maintenance department and a Tier 1 meeting on a production line will have different content. The safety issues are different. The hypercare processes are different. The performance measures are different. But the structure, safety first, yesterday's performance, today's plan, hypercare review, open actions, escalations, is the same. In that order. Every day.

The same principle applies to Tier 2 and Tier 3. Consistent format. Relevant content.

How many tiers does your site or function need?

Start by asking how many real decision-making levels exist between the person doing the work and the person who sets the direction. Each level where a problem can be resolved, or must be escalated because it cannot be resolved there, is a tier.

These are starting points, not rules. A planning function that runs three tiers because it has three genuine decision-making levels is right to do so. A manufacturing site that runs three tiers because the fourth adds no decision-making value is also right.

Why the structure matters

The structure is not bureaucracy. Each element of it exists for a reason. Remove any one of them and the system degrades.

Short meetings at fixed times.

A meeting that runs long is a meeting that will eventually be skipped. A meeting at a variable time is a meeting that will eventually be missed. The discipline of a fixed time and a fixed duration is what makes the system reliable. The team knows when it happens. The leader knows what to prepare. The agenda does not drift.

At the board, not in a room.

Tier 1 and Tier 2 meetings happen at the visual management board, the place where performance is tracked, actions are recorded, and the standard is visible. Not in a meeting room. Not on a screen. At the board. The board is the agenda. The board is the record. If the board is not current, the meeting cannot run properly, and that is the first finding.

Information flows up, decisions flow down.

The frontline team raises what they see. The department leader resolves what they can and passes up what they cannot. The site leader removes what the department cannot. This is the only direction that works. A system where information flows down and decisions flow up is a system where the people closest to the work are waiting to be told what to do about what they already know.

Named owners and close-out dates, every time.

An action without an owner is a wish. An action without a close-out date is a wish with a label. Every action raised in a tiered meeting gets a named owner and a close-out date before the meeting ends. Not eventually. Before the meeting ends.

The default close-out date is tomorrow. Not next week. Not end of month. Tomorrow. If tomorrow is not achievable, the action needs to be broken into a smaller step that is.

Leaders attend the tier below, on a schedule.

The tiered meeting system is not just an information flow. It is a confirmation system. Senior leaders attending the tier below them, on a defined frequency, is how the organisation knows the system is working, not just running.

The Tier 3 lead attends Tier 2 meetings. The Tier 4 lead attends Tier 3, and occasionally Tier 2 and Tier 1. This is not oversight. It is process confirmation applied to the management system itself.

When a senior leader attends the tier below, they are asking three questions:

• Are the right things being reviewed?
• Are decisions being made at the right level, or are problems sitting without an owner?
• Are gaps understood, and do actions have named owners with close-out dates that will be checked tomorrow?

Hypercare Processes — what gets reviewed every day

Not everything needs daily review. But some things do. These are the processes where a single day of drift can produce a loss that takes a week to recover from, or cannot be recovered at all.

These are often called hypercare processes. They sit at the centre of the Tier meeting agendas. They are reviewed every day, at every relevant tier, until the site is confident the standard is holding without daily oversight.

What qualifies as a hypercare process:

• The consequence of missing the standard for one day is significant, a quality failure, a safety incident, a schedule gap, a compliance breach.
• The process is new, recently changed, or known to be at risk of drifting.
• The process is directly connected to the site's current strategic objectives.

Common hypercare processes in manufacturing:

How to build your tiered meeting system

Work through the following steps in order. Each step has a clear output. Do not move to the next step until you have it.

Step 1 — Define your tiers

Before you fix times or design agendas, establish how many tiers your site or function actually needs.

Work through these questions:

How many genuine decision-making levels exist between the frontline and the site or function leader? Each level where a problem can be resolved, or must be escalated because it cannot be resolved there, is a tier. If two levels have the same authority and the same information, they are one tier.

Where does the work happen? That is where Tier 1 is. Not where the leaders sit. Where the work happens.

What is the smallest number of tiers that connects the frontline to the top of the function? Start there. You can always add a tier if a genuine gap appears. It is much harder to remove one once it is established.

For most multi-line manufacturing sites, four tiers is the right answer. For a single-function support team, two is often enough. For a large planning or supply chain function, three is typical.

Capture at this step:

The "Decisions they can make" and "What they escalate" columns are deliberate. If you cannot fill those columns, the tier is not yet defined well enough to run.

Step 2 — Set the fixed points

Fix the time and location for each tier before you design the agenda. The time must be consistent — same time every day, every week. The location must be at or near the visual management board for Tier 1 and Tier 2.

The tiers must be sequenced so that information can flow upward in a single morning. A typical sequence for a four-tier manufacturing site:

• Tier 1: 07:00–07:15
• Tier 2: 07:20–07:40
• Tier 3: 08:00–08:30
• Tier 4: Weekly — Monday morning or as agreed

Also agree the cross-tier attendance schedule:

Senior leaders attending lower-tier meetings is how the organisation confirms the system is working, not just running. This is process confirmation applied to the management system itself.

These are minimums. A site that is new to the system needs more cross-tier attendance, not less. Reduce frequency only when the system is demonstrably stable. Cross-tier attendance is part of Leader Standard Work. Build it into your LSW schedule before the system goes live.

Step 3 — Design the agenda for each tier

Each tier has a standard agenda. The agenda does not change from day to day. What changes is the content, the numbers, the actions, the escalations. The structure is fixed.

Standard Tier 1 Agenda: The same format for every Tier 1 on the site:

Total: 15 minutes maximum.

Standard Tier 2 Agenda:

Total: 20 minutes maximum.

Standard Tier 3 Agenda:

Total: 30 minutes maximum.

Standard Tier 4 Agenda:

Total: 60 minutes maximum.

What the attending senior leader is confirming:

When a senior leader attends a lower-tier meeting, they are not there to add agenda items or answer questions. They are there to confirm four things:

After attending, the senior leader feeds back to the tier owner, not in the meeting, but in a brief conversation afterwards. The feedback is specific: what was working, what was not, and what one thing would make the meeting more effective.

What makes any tier meeting easy to audit:

Because every meeting at the same tier follows the same format, a leader attending any meeting on the site can assess it against the same standard. The audit is not subjective. It is a format check followed by a content check.

A leader who attends a meeting in an unfamiliar area can complete this check during the meeting itself. They do not need to know the content. They are reading the format.

Step 4 — Build the visual management board

The board is not a decoration. It is the agenda. Every item in the meeting has a place on the board. If it is not on the board, it is not in the meeting.

The board is organised into four columns. This structure is the same for every tier, every function, every site.

The daily scorecard

The daily scorecard sits in the Do column. It is the single document that makes the tiered meeting system work. It is not a report. It is a live record, updated every day, reviewed every day, visible to every tier.

Each row is one measure. Each column is one day. The result for each day is recorded as a number, a tick, or a cross, green if the standard was met, red if it was not. No commentary in the cell. The colour tells you the status. The meeting provides the explanation.

The scorecard is organised by area, Safety, Quality, Service, Finance, in that order. Safety and quality issues are reviewed before service and cost. Every day. Without exception.

Example content for a daily scorecard:

The specific measures depend on the site, the function, and the current strategic objectives. The structure, area, measure, frequency, unit, daily result, is fixed.

The action list

The action list is the running record of every open action across the site. It is not the same as the board's daily action strip. The board shows today's actions. The action list shows everything, open, closed, and overdue, across all functions and all tiers.

It is reviewed at the upper tiers. It is the document that makes cross-functional accountability visible.

Minimum content for a site action list:

Step 5 — Define your hypercare list

Before the first meeting runs, agree the hypercare list for your site or area. This is the list of processes that will be reviewed every day at the frontline and department tiers.

Use these criteria to decide what goes on the list:

• A one-day deviation produces a significant loss, quality, safety, schedule, or compliance.
• The process is new, recently changed, or known to be at risk.
• The process is directly connected to a current strategic objective.

Step 6 — Run the first meetings

Run the first meeting with the full team present. Walk through the agenda item by item. Do not skip sections because there is nothing to report, a green status is still a status. The team needs to know that the standard is being met, not just that it is not being missed.

After the first week, review how the meetings ran:

• Did they start and finish on time?
• Was the board current before the meeting started?
• Were actions raised with named owners and close-out dates?
• Were close-out dates set for tomorrow, not next week?
• Were open actions from yesterday reviewed first?
• Were escalations passed up the same day?
• Did the tier above respond to escalations before the next meeting?
• Did any senior leader attend a lower-tier meeting this week? What did they find?

Step 7 — Sustain and improve the system

The meeting system is itself a process. It needs a standard, an owner, and a regular review.

Monthly review — ask these questions:

What a functioning system looks like — the evidence standard:

The monthly review is not a conversation about whether the meetings are happening. It is a check against observable evidence. For each domain, there is a guiding statement and a set of evidence criteria. If the evidence is not present, the element is not in place, regardless of what the attendance record shows.

Capture at this step:

What this gives you

Leadership behaviours

The meeting system only works if the leaders who run it behave in a specific way. The structure creates the conditions. The behaviour is what makes it real.

• Arrive prepared. The leader who walks into a Tier 1 meeting without having reviewed the board is not leading the meeting. They are attending it. Board review is preparation, not part of the meeting.
• Ask about the process, not just the result. "Why did we miss the target?" is a result question. "What happened in the process that produced that result?" is a process question. The second question is the one that leads somewhere.
• Act on what you find, in the room. A meeting that identifies a problem and assigns no owner has not solved anything. Every gap needs a named owner and a close-out date before the meeting ends. Not after. Before.
• Escalate the same day. A problem that cannot be resolved at Tier 1 goes to Tier 2 today. Not at the end of the week. The speed of escalation is the speed of the system.
• Close the loop visibly. When the tier above acts on an escalation, the tier below needs to know. A frontline team that escalates a problem and hears nothing back will stop escalating. Close the loop before the next meeting, at the board, where the team can see it.
• Attend the tier below on a schedule. This is not optional and it is not micromanagement. It is the mechanism by which the system is confirmed to be working. When a senior leader attends the tier below, the team sees that the system matters. When they stop attending, the team draws the correct conclusion.

Common pitfalls

Key Links

This guide depends on:

The tiered meetings are the fixed points that Leader Standard Work is built around. Cross-tier attendance belongs on every leader's LSW at a defined frequency.

This guide connects to:

What the tiered meetings find, Process Confirmation acts on, and vice versa. Process Confirmation is the structured check that feeds the meeting system with reliable information about whether standards are being followed.

The hypercare processes reviewed in the meeting system need defined standards to be confirmed against. Process improvement is how those standards are set and improved.