We value your privacy

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.

Powered by
    TeamAssurance

    What is a tier 2 meeting?

    Short answer

    A tier 2 meeting is a daily stand-up in which team leaders, the area supervisor or manager and support functions such as maintenance, quality and engineering review an area's performance. Held shortly after tier 1, it resolves issues the frontline teams escalated, coordinates resources across teams and passes unresolved issues to tier 3.

    Last updated · TeamAssurance

    Who attends

    Tier 2 is led by the area, department or value-stream manager. The team leaders from each tier 1 team attend, along with representatives of the support functions that teams depend on: maintenance, quality, engineering, planning, safety and sometimes warehouse or HR. Having the people who can act in the room is what makes tier 2 work.

    When and how long

    It runs daily, after all tier 1 meetings in the area have finished, typically 15 to 20 minutes, at an area board on the floor or close to it. Because it is a coordination meeting, it is longer than tier 1 but still time-boxed.

    A standard tier 2 agenda

    1. Area results: safety, quality, delivery and cost for the area as a whole, focusing on misses.
    2. Escalations from tier 1: each team leader presents issues their team could not resolve.
    3. Support function response: owners from maintenance, quality or engineering accept issues and commit to dates.
    4. Open actions: status of previous actions, especially overdue ones.
    5. Escalations to tier 3: agree what needs site-level decisions.

    How escalation works at tier 2

    Tier 2 is where most escalated issues should be solved, because it combines the area manager's authority with the support functions' expertise. Issues move up to tier 3 only when they need site-level resources, capital, policy changes or a decision between competing departments. Equally important is the downward flow: the team leader takes each answer back to their tier 1 meeting the next day.

    Common mistakes

    • Support functions not attending, so issues are noted but nobody accepts them.
    • Repeating every tier 1 metric rather than reviewing area trends and exceptions.
    • Treating tier 2 as a reporting meeting for the manager rather than a problem-solving forum.

    Example

    Two packing teams escalate the same carton jam. At tier 2 the maintenance planner recognises a worn guide rail, schedules the replacement for the weekend and assigns an owner. Because the spare part is not stocked, the purchasing approval is escalated to the tier 3 meeting.

    How TeamAssurance helps

    In TeamAssurance, issues escalated from tier 1 arrive on the tier 2 board with their history and context, so supervisors and support functions can act without chasing details. Embedded reports and live KPIs sit on the same board, and AI agents can find related and recurring activities across lines so a repeat problem is treated as one problem.

    Explore Tiered Daily Management Request a demo

    Frequently asked questions

    What is the difference between a tier 1 and tier 2 meeting?

    Tier 1 is one frontline team reviewing its own shift. Tier 2 brings several team leaders and support functions together to solve the issues those teams escalated and coordinate resources across the area.

    How long should a tier 2 meeting last?

    Usually 15 to 20 minutes. Detailed problem solving should be taken offline with an owner and a date rather than done in the meeting.

    ← Back to the glossary