← Back to blog

Daily Huddle Agenda: A 15-Minute Template That Works

November 11, 2026
Daily Huddle Agenda: A 15-Minute Template That Works

A good daily huddle agenda is short, fixed and the same every day: a quick priority or safety opener, a check on yesterday's actions, today's plan, blockers, owners for each follow-up, and a clean close. The whole thing fits in 15 minutes or less. Below you get a timed template, the reasoning behind each block, variants for plants, offices and multi-level organizations, and the facilitation habits that keep the meeting from sliding into a status report.

TKD Consulting
Turn Daily Huddles Into Follow-Through
TKD Consulting helps operations teams connect meeting cadence, accountability and on-the-floor execution to their stated goals.
Explore TKD Consulting

TL;DR

  • Run the huddle at the same time and place every day, and keep it to 15 minutes or less. Scrum Alliance puts the daily event at a 15-minute maximum, ideally at the same time daily.
  • Keep the running order identical daily: priority, yesterday's actions, today's plan, blockers, owners, close.
  • Find problems in the huddle and solve them afterward, with one owner and one date per problem.
  • On quiet days, end early. A 7-minute huddle beats a padded 15-minute one.
  • When one team's issues need a higher decision, stack huddles in tiers so escalation happens the same morning.

Table of Contents

The daily huddle agenda, minute by minute

Here is a working template for a team of 5 to 15 people. The timings are our recommendation, built on the structures published by Workhint and LeanSuite, which both use a fixed order of safety or priority, yesterday, today, problems, owners and close.

MinutesBlockWhat gets said
1Opening signalThe single most important priority today. In plants and warehouses, start with safety.
3Yesterday's follow-upDid each action close, move or stay blocked? One line each.
4Today's planWhat must happen today to protect customers, delivery, people and commitments.
4Blockers and risksWhat is stuck, late, unclear, short-staffed or waiting on a decision.
2OwnersEach new problem gets one owner, a due date and a definition of done.
1CloseWhat gets escalated after the huddle, then a clear end signal.

That adds up to 15 minutes. If your team is small, shrink every block proportionally rather than adding blocks.

Why the order never changes

A fixed order is what lets people prepare in 30 seconds before they walk in. LeanSuite describes the agenda as a running order that stays the same every day, so the team leaves in 15 minutes with actions that have owners. When the sequence moves around, the leader ends up improvising and the meeting expands.

The second reason is that blocks protect each other. Yesterday's follow-up comes before today's plan because unclosed actions are the most common source of today's blockers. Blockers come before owners because you cannot assign what you have not named.

The problem log: the one artifact you need

Keep a simple log on a whiteboard, a shared sheet or a visual board. Four columns are enough: problem, owner, due date, status. LeanSuite's template uses the same rule: each problem raised gets one owner and a date, and the owner and the people required solve it after the huddle, not during it.

The log is also what makes tomorrow's first block work. If an item has no owner or no date, it is not an action yet, it is a complaint.

Agenda variants for different teams

A 10-minute version for supervisors on the floor

IndustryWeek reported a manufacturer that standardized a 10-minute huddle agenda for supervisors with four parts:

  1. Safety (3 minutes): yesterday's incidents or near misses, today's biggest risk, and one "what could go wrong?" question.
  2. Quality (3 minutes): one key defect from yesterday, where it showed up, and what to watch for today.
  3. Schedule and staffing (2 minutes): volume for the shift and known constraints.
  4. Voice of the team (2 minutes): one issue or idea captured on the board, with at least two open-ended questions from the supervisor.

The same article describes posting the agenda at every team board and auditing huddles the way managers audited 5S: was the agenda followed, did the supervisor ask questions, did the team leave one issue or idea on the board. That audit habit is what stops a good agenda from decaying within a month.

A healthcare-style version

The Agency for Healthcare Research and Quality lists a standard huddle agenda for ambulatory surgery settings with five items: safety concerns from yesterday, issues flagged for today, review of currently tracked problems, additional staff input, and announcements. The leader starts at a designated time, keeps the agenda on a visual display board, and closes with a clear signal that the huddle is over. That last detail is worth borrowing in any industry. People should know exactly when the meeting ends.

An office or sales-team version

Office teams usually do better with the question set that agile teams use. Atlassian describes the standup as a quick round-robin where each person answers three things: what did I accomplish yesterday, what will I do today, and are there any blockers. For a sales or service team, swap in numbers: pipeline movement, customer commitments due today, and deals or tickets that need help.

One trade-off to know: the round-robin invites everyone to recap their day. Calendar.com recommends blocker-first updates because blockers are actionable while purely informational updates can be handled in writing. If your huddle drifts past 15 minutes, move the informational updates to a chat channel and keep the live time for blockers.

An office or sales-team version

A management-team version

Lucid Meetings' guide describes the huddle for management teams and suggests each person share their top priority, unavailable time, blockers, and opportunities or key learnings. That is a good frame for an executive group of four to eight people. If you want to build in recognition, a short shout-out for a closed action works better than a separate ritual, and a few lines in the style of team appreciation messages can follow up in writing for bigger wins.

How to run a daily huddle, step by step

  1. Pick the time and place and keep them. Parabol advises the same time and place every day for simplicity, and notes many companies hold morning huddles before work starts so issues can be solved immediately.
  2. Start and end on time. Lucid's guide says not to wait for tardy members. If someone misses the huddle, it is their responsibility to find out what they missed and pass on anything they were due to share.
  3. Stand, if the work allows it. It is a simple way to keep people brief. Remote teams can do the same on a call with cameras optional.
  4. Use a visible agenda. A board, a shared screen or a laminated card. The leader should not be reciting from memory.
  5. Manage tangents out loud. ClickUp calls tangent management the facilitator's most important skill, with a line such as "That sounds like a separate conversation. Can the two of you sync after the standup?"
  6. Find problems, don't solve them. Parabol describes the huddle's purpose as identifying and highlighting issues, with solving happening afterward. PMI's daily coordination practice makes the same point: the meeting communicates progress and identifies impediments and is not meant for problem solving.
  7. Close the loop the next day. Yesterday's follow-up block is the accountability mechanism. Without it, the log becomes a graveyard.

Daily huddle vs. standup

The two terms overlap heavily, and most readers can use one agenda for both. The practical differences come from where each meeting grew up.

Daily huddleDaily standup
Typical homeOperations, healthcare, plants, warehouses, field crewsSoftware and agile project teams
Typical focusSafety, quality, staffing, today's priorities, escalationsProgress toward a sprint goal and impediments
Typical formatFixed agenda on a board, often with metricsRound-robin or blockers-first
Length15 minutes or less15 minutes or less

The Scrum Alliance describes the daily scrum, also called the daily standup, as a brief event to inspect progress toward the sprint goal where people surface impediments and coordinate the day. If you run an operations team, borrow the standup's discipline about blockers and the huddle's habit of starting with safety and metrics.

Tiered daily huddles: how problems travel up in one morning

One huddle solves one team's coordination problem. It does not solve the problem of a frontline issue that needs a decision above the team's authority. Tiered huddles do that by stacking short meetings in sequence.

Ohio State's SMART Toolkit describes tiered huddles as daily meetings across multiple tiers of leadership: teams check status, identify problems, take countermeasures such as escalation, and make sure issues are addressed. It gives an example in which hospital leaders learn of patient safety issues by 11:00 a.m. every day.

Two large health systems show the pattern at scale:

  • Intermountain Healthcare: front lines huddle at 7 a.m., the executive team holds its huddle at 10 a.m., and by 10:15 a.m. leaders have a system snapshot covering serious safety events, equipment downtime, capacity constraints and similar categories.
  • Cleveland Clinic: the huddle has six tiers, the sixth meeting at 11:00 a.m. with the executive and broader leadership team. If a team cannot address a problem, it passes it to the next tier. According to KaiNexus, lower-level huddles run under 15 minutes and higher ones under 30.

Scaling the idea to a $5M to $50M company

You do not need six tiers. Most mid-market companies need two or three:

  1. Team huddle (start of shift, 10 to 15 minutes): supervisors and their crews.
  2. Department huddle (30 to 60 minutes later, 15 minutes): supervisors and the department head, taking only what the teams could not resolve.
  3. Leadership huddle (late morning, 15 minutes): the owner or COO and department heads, looking at a one-page snapshot of safety, quality, service, staffing and cash-critical items.

The design rule is simple: each tier hears only what the tier below could not fix, and each tier has the same fixed agenda. If a tier is hearing everything, you have a reporting meeting, not an escalation path. Our guide to visual management boards covers how to set up the boards that carry this information from tier to tier.

What to do when there is nothing to say

This is the most common reason huddles die: the leader feels they have nothing to add, so the meeting turns into a recitation or gets skipped.

First, the leader is not supposed to be the content. The team is. If the agenda is built on yesterday's actions, today's commitments and blockers, the leader's job is to ask questions and keep time.

Second, a quiet day is a good day. ClickUp advises that if nobody has blockers, celebrate that and end early: a 7-minute huddle is better than a padded 15-minute one. Calendar.com offers a blockers-only framing: each person names one blocker or says "clear."

What to do when there is nothing to say

Third, a quiet huddle in a high-risk environment deserves a second look. KaiNexus, describing Cleveland Clinic's approach, notes the principle that no problems identified is itself a problem. In plants, warehouses and service operations, that is usually the moment to swap in a sharper question, such as "what nearly went wrong yesterday?" or "what is the one thing that could stop us shipping today?"

Common mistakes that wreck a huddle

  • Solving in the room. Two people debate a fix while eight wait. Take it offline, give it an owner.
  • No owner, no date. Actions without both do not get done.
  • Changing the format weekly. Novelty is the enemy of a 15-minute meeting. Change the agenda only when the data says a block is not earning its minutes.
  • Using it as a one-way broadcast. The IndustryWeek example above improved when supervisors shifted from one-way reminders to real dialogue. Ask at least two open questions every day.
  • Skipping the follow-up block. Yesterday's actions are where credibility is built.
  • Letting it grow. If it regularly runs long, cut a block or split the group, don't extend the clock.

Once the huddle is stable, connect it to the rest of your management rhythm. Weekly one-on-ones handle the coaching that does not belong in front of the team, and our manager one-on-one agenda shows how to structure them. For a first 90 days of rollout, the implementation roadmap template gives you a one-page plan.

Our perspective

We see the same pattern in nearly every owner-operated company we walk into. Leadership has a strategy, and the SOPs exist on paper, but nothing connects the plan to what a supervisor does at 7:05 on Tuesday. The daily huddle is the cheapest connector there is.

The huddle fails for a predictable reason: it is treated as a meeting instead of a system. A system has an owner, a fixed agenda, a visible board, a log with names and dates, and an escalation path. When any one of those is missing, the meeting drifts and people stop attending.

That is why we build huddles into the implementation runway of our engagements instead of handing over a template and leaving. Our approach is designed so the scorecards, meeting cadences and accountability mechanisms are written for a floor manager to use on Monday morning, and so your team can sustain them after we leave.

If you take one thing from this article: pick the agenda, fix the time, assign the log owner, and run it for 30 days before you change anything. The consistency is the point.

David

Put a working huddle in place with an audit

If your huddles keep fading, or the problems raised on the floor never reach the people who can fix them, the issue is usually the system around the meeting. Our 90-Day Operations Audit is a fixed-price entry point at $3,500 one-off. It maps your people, processes and performance systems against your goals and gives you a prioritized action plan, including the scorecards and meeting cadences that make a daily huddle stick. For more on how we work with $5M to $50M companies, see our operations consulting page.

TKD Consulting

FAQ

How long should a daily huddle be?

Fifteen minutes or less. Scrum Alliance describes the daily scrum as timeboxed to a maximum of 15 minutes, and Parabol says daily huddles usually don't run past 15 minutes. Frontline huddles can be as short as 10 minutes, and on quiet days you should end early.

What should a morning huddle agenda include?

A priority or safety opener, a check on yesterday's actions, today's plan, blockers, an owner and date for each new problem, and a close. The order should stay the same daily. Timings for each block are in the template above.

Who should attend a daily huddle?

The people who coordinate the same work: a shift crew with its supervisor, a department with its lead, or a leadership team. Keep each group small enough that everyone can speak in a minute or two. When more groups are involved, use tiers so each level only hears what the one below could not resolve.

What is the difference between a daily huddle and a daily standup?

Mostly the setting. Standups come from agile software teams and focus on progress toward a sprint goal, while huddles come from operations and healthcare and usually start with safety, quality and staffing. Both are short, timeboxed and built around surfacing blockers, so one agenda can serve either.

What if the team has no updates?

End the huddle early. If problems never surface in a high-risk operation, change the questions, for example by asking about near misses or what could stop today's shipments.

Sources