Practical guide · Lean leadership and employee engagement
Meeting cadence: how to set one, with example schedules for a plant
Short answer
A meeting cadence is the fixed rhythm of a team's recurring meetings: which meetings happen, how often, how long they last, who attends and in what order. In a plant it usually runs from a short daily huddle on each line up to a weekly plant review and a monthly business review, each one feeding the next.
A good cadence gives every level one meeting, at a fixed time and place, with a fixed agenda and the few KPIs that level can act on. The meetings are staggered so a problem raised on the line at 7:00 reaches the area review by 9:00 and the plant review the same week. Every meeting ends with decisions and actions on record, and what a level cannot settle goes up to the next meeting with its history.
Last reviewed:
What is a meeting cadence?
Cadence means rhythm. A meeting cadence is the rhythm of a team's recurring meetings: the daily, weekly, monthly and quarterly meetings, how long each one runs, who is in it, and how they connect. It answers one question for everyone in the building: when, and where, does this kind of problem get decided?
In manufacturing the cadence is usually built on tiered meetings. Tier 1 is the team on the line, tier 2 the area or department, tier 3 the plant, and tier 4 the business. Each tier meets on its own rhythm, looks at its own numbers and passes up what it cannot fix. Together with leader standard work and gemba walks, the cadence is the backbone of a plant's management operating system.
A cadence is not the same as a calendar full of meetings. The test is whether each meeting has a decision it exists to make. A meeting with no decision to make is a report, and a report can be read.
An example meeting cadence for a manufacturing plant
This is a common shape for a single plant running two or three shifts. The names, times and lengths are an example. What matters is that every level has one meeting, and that each meeting knows what it decides.
| Meeting | Who | How often | Length | What it decides |
|---|---|---|---|---|
| Shift handover | Outgoing and incoming team leaders | Every shift change | 5 to 10 min | What the next shift must know: open problems, machines down, material short |
| Tier 1 huddle | Team leader and the line | Daily, start of shift | 10 to 15 min | Today's plan, yesterday's safety, quality, delivery and cost results, actions the team can take today |
| Tier 2 area review | Supervisors, area manager, maintenance, quality | Daily, after the tier 1 huddles | 20 to 30 min | Blockers the lines cannot remove, help across shifts, what goes to the plant |
| Tier 3 plant review | Plant manager and department heads | Weekly (some plants daily) | 45 to 60 min | Priorities and resources, repeat problems that need a project, answers sent back down |
| Monthly business review | Plant or site leadership, finance | Monthly | 60 to 90 min | Results against plan for the month and the year, projects started or stopped |
| Quarterly strategy review | Site and business leaders | Quarterly | Half a day | The year's goals and how they cascade to each plant and area |
Lengths are typical, not rules. A huddle that runs past 15 minutes has usually turned into problem solving, which belongs in its own session.
A daily timetable: how to stagger the meetings
The order matters more than the times. Each meeting should start after the one below it has finished, so the numbers and escalations are fresh. An example for a plant whose day shift starts at 6:00:
| Time | Meeting | Feeds |
|---|---|---|
| 5:50 | Shift handover at each line | The tier 1 huddle |
| 6:30 | Tier 1 huddles, one per line or cell | The tier 2 area review |
| 8:00 | Tier 2 area reviews, one per area | The tier 3 plant review |
| 9:00 (Monday) | Tier 3 plant review | The monthly business review and the answers back to tier 2 |
Leave at least an hour between tier 1 and tier 2 on a plant with many lines, so supervisors can walk the huddles before their own meeting.
Keep the times fixed. When a meeting moves around the calendar, people stop preparing for it and start attending it, and the meeting turns into reading the numbers for the first time.
How the cadence changes with shifts and sites
| Operation | What changes |
|---|---|
| One shift, one plant | Tier 1 and tier 2 can run back to back in the first hour. Tier 3 often runs weekly, with a short daily stand-up for the plant manager's staff. |
| Two or three shifts | Every shift gets its own tier 1 huddle and a handover. Tier 2 runs once a day, on the day shift, and reads the night shifts' boards first. Escalations from nights wait on the board, not in someone's memory. |
| Several plants | Each plant keeps its own tiers 1 to 3. A tier 4 review compares sites weekly or monthly, on the same KPI definitions, and sends standard actions back to every plant. |
| Continuous process (24/7) | Handovers carry more weight than huddles. A short daily review at a fixed hour covers all crews, and the weekly review reads the full week, not just the day shift. |
How to set a meeting cadence in six steps
- 1
List the decisions, not the meetings
Write down the decisions that have to be made every shift, every day, every week and every month: who covers a missing operator, which order runs first, whether a line gets a capital fix. Each decision belongs to the lowest level that can make it.
- 2
Give each level one meeting, one owner and one time
One tier 1 huddle per team, one tier 2 review per area, one plant review. Name an owner for each and fix the time and the place. Do not add a meeting for a decision an existing meeting can make.
- 3
Stagger them so problems move up the same day
Tier 1 before tier 2, tier 2 before tier 3. Leave enough time between them for a supervisor to walk the huddles. Put the weekly and monthly reviews on fixed days.
- 4
Fix the agenda and the KPIs for each meeting
Write the agenda once and keep it. Choose only the KPIs that level can act on, each with a target. A huddle reads yesterday and the month so far; a plant review reads the week, the month and the year.
- 5
End every item with a decision, an action or an escalation
Actions get a name and a date before the meeting ends. Anything the level cannot settle goes on the next level's agenda with its history, and the answer comes back to the meeting that asked.
- 6
Review the cadence after a month
Drop a meeting nobody decides anything in, shorten one that always runs over, and move one people keep missing. A cadence is a standard: improve it like any other.
A standard agenda for each meeting
Tier 1 huddle (10 to 15 minutes)
- Safety: anything from the last 24 hours, and today's risks
- Yesterday's results against target: safety, quality, delivery, cost, people
- Today's plan and staffing
- Open actions: done, late or blocked
- New problems: fix today, or escalate
Tier 2 area review (20 to 30 minutes)
- Safety across the area
- The lines' boards read together: where is the area red
- Escalations from tier 1: decide, assign or escalate
- Cross-shift and cross-line actions
- What goes to the plant review
Tier 3 plant review (45 to 60 minutes)
- Safety and people
- Plant KPIs against plan for the week and the month
- Escalations from the areas
- Repeat problems: start a project or an A3
- Decisions on priorities and resources, and the answers sent back down
Free printable versions: the daily huddle agenda, the tier 2 meeting agenda and the monthly business review.
Signs your meeting cadence needs fixing
- The same red comes back week after week and nobody owns it: the escalation path is missing.
- Supervisors hear about night-shift problems in the corridor: the handover is not written down.
- The plant review spends its first half hour building the numbers: the KPIs are not ready before the meeting.
- Actions are agreed but never checked: nobody reads open actions at the start of the next meeting.
- People skip a meeting and nothing changes: that meeting has no decision to make.
- Tier 2 starts before tier 1 has finished: the timetable is not staggered.
Running the cadence in LeanSuite
In LeanSuite each level's meeting is a series in Daily Standard Work with its own cadence, purpose and agenda, and each agenda item has an owner and its minutes. Owners prepare their item before the meeting: highlights, lowlights, issues, priorities and the support they need. Their KPIs fill in by themselves, met or missed against target. In the room you go item by item, turn a request for support into an action, and actions from earlier meetings come back until they are ticked off. The tier boards run in Lean Studio, and anything a tier cannot fix is escalated to the next one with its history. See how a meeting runs.
Structured Meetings
Run every level's meeting on its cadence in LeanSuite
LeanSuite keeps every level's meeting as a series, with each item's KPIs filled in before anyone walks in and the open actions carried from week to week.
Go deeper
This page is the short version. These guides cover each part in full.
- Tier boards: cascading daily management explainedWhat goes on the board at each tier and how the boards connect.
- Leader Standard Work: Daily Leader RoutineThe leader routines that sit around the meetings: gemba, checks and follow-up.
- What is a stand-up meeting?How to keep the daily meeting short and standing.
- How to perform an effective gemba walkThe walk supervisors take between the tier 1 huddles and their own review.
All our articles on this subject are in the lean leadership and employee engagement topic.
Free templates and tools
- Daily huddle agendaA 15-minute start-of-shift stand-up in six timed blocks, with yesterday's SQCDP results, today's plan, actions and escalations.
- Tier 2 meeting agenda and escalation sheetA 15-minute tier 2 agenda in ten timed blocks, fixed roles and rules, escalation triggers with time limits, and a log that ages every escalation and sends the answer back down.
- Monthly business review template (operations review agenda)A 90-minute operations review in nine timed blocks: who speaks when, the KPIs each block reviews with red or green, a prep checklist for every presenter and a log of decisions and actions.
- Shift handover templateSafety, production against plan, holds, downtime events, materials and people, and the open actions the next shift takes over.
- Escalation matrix templateWho is called for each type of issue and after how long, with severity rules, contacts and an escalation log.
- Leader standard work templateA team leader's daily, weekly and monthly routine with a box per day, follow-ups and a weekly review.
Doing this in LeanSuite
Structured Meetings
Each level's meeting as a series with its own cadence and agenda. Owners prepare their item, KPIs fill in against target, and actions carry over to the next meeting.
See Structured MeetingsTiered Meetings
Run huddles on live data in Lean Studio and escalate what a tier cannot fix to the next one, with its history.
See Tiered MeetingsSQDC board software
A tier board that colours safety, quality, delivery and cost red or green by day from the KPIs.
See SQDC board software
See it on your own lines
Bring the problem you are working on to a 45-minute demo. Or look around with sample data first, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.
FAQ
Questions about meeting cadence
The fixed rhythm of a team's recurring meetings: which meetings happen, how often, how long they last, who attends and in what order. In a plant it usually runs from a daily huddle on each line to a weekly plant review and a monthly business review.
A short handover at every shift change, a 10 to 15 minute tier 1 huddle at the start of each shift, a 20 to 30 minute tier 2 area review once a day after the huddles, a weekly tier 3 plant review and a monthly business review. Adjust the times and lengths to your shifts.
Tier 1 every shift or every day, tier 2 every day or every week depending on how fast the area's problems move, tier 3 weekly in most plants and daily in some, and tier 4 monthly. The rule is that each tier meets often enough to answer what the tier below sends up.
Ten to fifteen minutes, standing at the board. If it runs longer it has usually turned into problem solving, which should be its own session with the people who can fix the problem.
Frequency is how often one meeting happens. Cadence is the whole rhythm: every recurring meeting, its length, who attends, and the order they run in so that each one feeds the next.
Problems raised on the line reach the right level the same day or the same week, actions are checked at the next meeting, the same red does not come back for weeks, and nobody spends the first half of a review building the numbers.
Related guides and tools
More method guides
- The 6 Ms of production
- Poka-yoke
- Model area 90-day plans
- Moving from Excel to one system
- Reducing machine downtime: a worked month
- Andon
- Cycle time vs lead time, worked through
- Root cause analysis
- How many operators a line needs
- Reducing scrap and rework: a worked month
- Unsafe acts and unsafe conditions
- Just culture
- Stop-work authority
- Material review board (MRB)
- Nonconformance and NCRs
- Problem solving methods
- Quad chart
- OEE calculation
- Quality assurance vs quality control
- SOP meaning and format
- Job hazard analysis
- Near miss reporting
- Fishbone diagram
- Pareto chart
- Histogram
- Control chart
- What is a gemba walk
- What is lead time
- What is operational excellence
- How to improve product quality
- Preventive vs predictive maintenance
- Kanban
- FMEA
- PDSA cycle
- Safety moments
- Just-in-time manufacturing
- Kaizen
- 5S
- Total quality management (TQM)
- CAPA (corrective and preventive action)
- Layered process audit (LPA)
- Lean tools
- Lockout tagout (LOTO)
- A3 problem solving
- Preventive maintenance
- APQP
- High reliability organization (HRO)
- Manufacturing KPIs
- Quality metrics
- Practical problem solving
- CMMS
- Risk assessment
- Production efficiency
- Total productive maintenance (TPM)
- Reliability-centered maintenance (RCM)
- Hierarchy of controls
- Personal protective equipment (PPE)
- Emergency action plan
- Safety signs
- Warehouse safety
- ISO 9001
- SIPOC diagram
- Rolling action item list (RAIL)
- Pugh matrix
- Flowchart
- Project charter
- ISO 9001:2026
- Fleet maintenance
- IATF 16949
- AS9100
- ISO 14001
- ISO 45001
- One point lesson
- Standard work
- Lean manufacturing principles
- Toyota Production System
- 5W1H
- 5 Whys
- Continuous improvement
- Takt time
- DMAIC
- PDCA
- 8D problem solving
- Prioritization matrix
- Gemba walk questions
- 5W1H questions
- Layered process audit questions
- 5S audit questions
Or browse the topics, the full library and the lean glossary.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

