Skip to content

Free template

Updated

Tier 2 meeting agenda and escalation sheet

A tier 2 meeting is the short daily stand-up where an area supervisor or area manager, the team leaders and the support functions (maintenance, quality, materials) go through what each tier 1 team escalated that morning, decide who owns each problem, and send up to tier 3 what the area cannot fix. It sits between the team huddles and the value stream or plant meeting, and it is where escalations most often stall. This template gives the meeting a 15-minute agenda in ten timed blocks, fixed roles and eight rules, the escalation triggers and time limits for each tier, and a decision for every escalation: own it at tier 2, take it to tier 3, or send it back to tier 1 with what the team needs. Page 1 of the PDF is the agenda, page 2 how the tiers connect, page 3 a blank action and escalation log, page 4 a metric card and a meeting check, and pages 5 and 6 a filled-in example. The Excel version ages every escalation, keeps the first due date and counts the days late, flags items over the tier 2 limit, repeats of the same problem and answers not given back, and sums up the week by tier 1 board, with an SQDCP metric card and a meeting discipline score.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the tier 2 meeting agendaFields for area, date, leader and start time, a table of ten timed blocks from safety to close with what to cover and who speaks, a box for what goes up to tier 3, the attendee roles and the eight meeting rules.
15-minute agendaFixed rolesMeeting rulesEscalation triggersAction and escalation logAge and days lateRepeat counterSQDCP metric cardMeeting check

When to use it

When to use a tier 2 meeting agenda

  • Every working day, straight after the last tier 1 huddle in an area with several teams.
  • When tier 1 teams escalate problems and never hear back, or the same problems come up week after week.
  • When the area meeting runs long, reads out every number and ends without owners or dates.
  • When setting up tiered meetings, to agree what goes up, how fast and what comes back down before the first meeting.

How to fill it in

  1. 1

    Set the time and the people

    Hold tier 2 at the area board once every tier 1 huddle in the area has finished, at the same time every day. Name the leader, a team leader from each team, the maintenance, quality and materials reps, a scribe and a timekeeper.

  2. 2

    Agree the triggers and the limits

    Write down what goes from tier 1 to tier 2 and from tier 2 to tier 3, and how fast. In the template's example, tier 1 escalates what it has not fixed by its next huddle, and tier 2 sends up anything open more than 3 days or beyond its authority. Safety risks and quality holds go by the escalation matrix and never wait for a meeting.

  3. 3

    Run the ten blocks to the clock

    Safety, quality, delivery, cost and productivity, and people take 6 minutes, reds only. Then 4 minutes for the escalations from tier 1, 2.5 for the action review and the last 2.5 for what goes to tier 3 and the read-back.

  4. 4

    Decide every escalation in the meeting

    Own it at tier 2, take it to tier 3, or send it back to tier 1 with what the team needs. Write one owner and one due date on the log. The due date is never moved: a late item shows its days late.

  5. 5

    Send every answer back down

    The team that raised it hears the answer at its next tier 1 huddle; write the date on the log. Take escalations to tier 3 the same day, written as the problem and the ask.

  6. 6

    Review the week

    Once a week read the summary: what is over the limit or overdue, what repeats, which board escalates most, and the meeting check score. A repeat gets one owner finding the cause, not another action.

The agenda

The 15-minute tier 2 agenda, block by block

Ten blocks in a fixed order. The first five run the business and cover reds only; the last five are the escalations, the actions and what goes to tier 3. The minutes are example values: change them, keep the total.

  • Safety

    Minutes
    1
    What to cover
    Any injury, near miss or hazard in the last 24 hours, and open safety actions. A hazard still open gets an owner now.
    Who speaks
    Area supervisor
  • Quality

    Minutes
    1.5
    What to cover
    Reds only: first pass yield, scrap, holds and complaints against target, by team.
    Who speaks
    Quality rep, team leaders
  • Delivery

    Minutes
    1.5
    What to cover
    Plan against actual by team, the cause of each miss, and today's risk to the schedule.
    Who speaks
    Team leaders
  • Cost and productivity

    Minutes
    1
    What to cover
    Red lines only: downtime, OEE, overtime, material usage.
    Who speaks
    Team leaders, maintenance rep
  • People

    Minutes
    1
    What to cover
    Today's staffing: absences, who moves between teams to cover, training due.
    Who speaks
    Area supervisor
  • Escalations from tier 1

    Minutes
    4
    What to cover
    Each new escalation in under a minute: the problem, the ask, then a decision (own at tier 2, up to tier 3, back to tier 1), one owner and a due date.
    Who speaks
    Team leader who raised it
  • Action review

    Minutes
    2.5
    What to cover
    Overdue actions first, then those due today. Done or not done. A late action keeps its due date and gets a new forecast.
    Who speaks
    Each owner
  • New escalations to tier 3

    Minutes
    1
    What to cover
    What goes up today, written as the problem and the ask, and who takes it to the tier 3 meeting.
    Who speaks
    Area supervisor
  • Help needed from tier 3

    Minutes
    0.5
    What to cover
    Answers due from tier 3, and decisions or resources the area is waiting for.
    Who speaks
    Area supervisor
  • Close

    Minutes
    1
    What to cover
    Read back every new owner and due date, and the answer each tier 1 team gets at its next meeting.
    Who speaks
    Scribe

Rules and escalation triggers

The meeting rules, and what goes up, how fast

Eight rules for every meeting, then the triggers for each step up and the time limit for the answer back down. The time limits (one shift, 3 days, 14 days) are example values this template sets: agree yours with the people in each role. Anything that cannot wait goes by the escalation matrix, not the meeting.

Meeting rules

Every meeting

  1. 1Stand at the area board. Start on time even if someone is late, and stop at 15 minutes.
  2. 2Team leaders update the board before the meeting: their results, misses and escalations.
  3. 3Reds only. Greens are not read out.
  4. 4Problems, not stories: what, where, how much, since when, and what is needed.
  5. 5No problem-solving in the meeting. Assign it; the people needed meet straight after.
  6. 6One owner (a name, not a department) and one due date per action. The due date is never moved: a late action stays late and gets a new forecast.
  7. 7Overdue actions are reviewed first, then the ones due today.
  8. 8Every escalation gets a decision in the meeting: own it at tier 2, take it to tier 3, or send it back to tier 1 with what the team needs.

Do not wait for the meeting

Call now, as the escalation matrix says, then log it

  1. 9Someone is hurt, or could be hurt by a hazard that is still there.
  2. 10A quality hold, or suspect product that may have shipped.
  3. 11A customer shipment is at risk today.

Escalate from tier 1 to tier 2

Raised at the next tier 2 meeting, about one shift or 24 hours after it was found

  1. 12It is not fixed by the next tier 1 meeting.
  2. 13It needs another department, spend, overtime or authority the team leader does not have.
  3. 14It affects another team's work.
  4. 15The same problem has come up twice in 14 days.

Escalate from tier 2 to tier 3

Raised at the same day's tier 3 meeting

  1. 16It has been open more than 3 days at tier 2.
  2. 17It needs spend over the area's limit, capital, headcount or a priority call between areas.
  3. 18A customer delivery or customer quality is at risk.
  4. 19The same problem shows up in two or more areas.

Send the answer back down

Every escalation, whatever the decision

  1. 20Tier 2 answers each tier 1 escalation by that team's next tier 1 meeting.
  2. 21Tier 3 answers each tier 2 escalation the same day.
  3. 22The team leader gives the answer at the team board, and the log records the date it was given.

A filled-in example

Illustrative, not a benchmark

An example: one week of tier 2 escalations in a molding and assembly area with four tier 1 boards (illustrative, the same as the Excel worked example).

The example week's 9 escalations

  • Owned and closed at tier 2: 6 escalations
  • Sent to tier 3, answered: 1 escalation
  • At tier 3, due tomorrow: 1 escalation
  • Open past the limit, not sent up: 1 escalation

Days open, against the 3-day limit

  1. Leak tester giving false fails4 daysover the limit
  2. Worn robot gripper (at tier 3)2 daysinside the limit

Of 9 escalations from four tier 1 boards, 6 were owned and closed at tier 2, 1 went to tier 3 and was answered, 1 is at tier 3 and due tomorrow, and 1, a leak tester giving false fails, has been open 4 days against the 3-day limit with no decision to send it up.

Closed this week: 7, 6 of them at tier 2. The leak tester is past the limit with no decision: tier 2 either owns it with a date or sends it up.
  • 9 escalations came up from the four boards. 6 were owned at tier 2 and closed within 2 days: short shots, a broken pallet jack, a failing hot runner heater, cover for the leak test station, and the central dryer alarm, twice.
  • 2 went to tier 3: a carton shortage that needed the purchasing manager, answered in 2 days, and a worn robot gripper over the area's spending limit, still waiting and due tomorrow.
  • 1 is flagged: a leak tester giving false fails, open 4 days against the 3-day limit and 2 days past its due date, with no decision to send it up.
  • The dryer alarm came back on a second press 2 days after it was fixed, so the sheet counts a repeat, and that answer has not yet gone back to the team.
  • Meeting check: 23 of 30 checks met (77%). On Tuesday the meeting ran 18 minutes, the board was not ready and a problem was solved in the meeting.

Closed this week: 7, of which 6 at tier 2 (86%), and 6 of 7 by the original due date. Average age at closing 10 ÷ 7 = 1.4 days; the 2 open items average (4 + 2) ÷ 2 = 3.0 days. The metric card shows 21 of 30 days on target (70%), with OEE red on Friday.

Common mistakes

  • Re-running tier 1

    Tier 2 hears each team's reds and escalations. Reading every team's numbers again fills the 15 minutes before the first escalation is heard.

  • Solving problems in the meeting

    Eight people watching two solve one problem is how 15 minutes becomes 40. Give it an owner; the people needed meet straight after.

  • Moving due dates

    A date that moves every time it is missed hides the late work. Keep the first date, show the days late, and write the new forecast beside it.

  • Answers that never come back

    A team that never hears what happened to its escalation stops raising problems. Record the date the answer was given at the team board.

  • A repeat treated as a new action

    The same problem twice in two weeks needs one owner finding the cause with 5 whys or an A3, not another reset or another reminder.

  • The manager running the area meeting

    When the tier 3 leader runs tier 2, the area leader stops owning it. Visit, listen, and talk to the area leader afterwards.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite tiered meetings run on Lean Studio boards: owners and due dates are assigned during the meeting, an unresolved item is escalated to the next tier with its photos, notes and history, and the reply is sent back down to the tier that raised it.

See it in a 45-minute demo

FAQ

Tier 2 meeting agenda and escalation sheet: common questions

More free templates

All templates
Browse all 189 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.