Control Room · Ops

Daily Delivery Operations Meeting: How to Build the Ritual (Standup, Weekly and War Room)

A daily delivery operations meeting is a short, fixed ritual where a multi-branch team reviews live delivery numbers and decides what to move today. The best setup is layered: a 10-minute daily standup for the day's fires, a weekly review to compare branches by trend, and a war room activated only when a metric crosses a threshold. Each layer needs a closed agenda, one owner, and a trigger number so the meeting ends in actions, not excuses.

By Control Room · 2026-08-23 · 4 min read

Running delivery across several branches without a fixed meeting rhythm means you find out about problems when the rating already dropped or the cancellations already piled up. The fix isn't more meetings, it's the right layer of meeting at the right moment. A layered cadence gives you a short daily for today's fires, a weekly for trends between branches, and a war room reserved for real emergencies. Below is how to build each layer so it closes in decisions.

Why a layered cadence beats one long meeting

A single daily hour-long meeting collapses under its own weight: too broad to fix today's problems, too frequent to spot real trends. The layered model separates jobs by time horizon.

• Daily standup — solves what is on fire right now: late prep times, a branch that stopped accepting orders, a stock-out on a top seller.
• Weekly review — compares branches by trend: which location is drifting on delivery time, which rating is slipping week over week.
• War room — an exception, not a schedule. It fires when a number crosses a threshold you defined in advance.

Each layer answers a different question. Mixing them is how meetings turn into venting sessions.

The daily standup: 10 minutes, fires only

A daily operations standup is a fixed, standing meeting of no more than 10–15 minutes to align on today's operation. It happens at the same time every day, ideally before the first peak, and it runs on a closed agenda.

Who should be there

Keep it small: the ops lead (owner of the meeting), and one voice per function that touches delivery — kitchen, front/dispatch, and whoever watches the apps. In a multi-branch setup, branch managers report their one headline number, not a full story.

The 10-minute agenda

1. Yesterday's misses (2 min): orders that went wrong, why, and whether it's resolved.
2. Today's risks (3 min): staffing gaps, stock at risk, expected volume, any branch already paused.
3. Live numbers check (3 min): prep time, acceptance, cancellations, rating trend.
4. Actions (2 min): each action gets one owner and a time. No owner, no action.

If a topic needs more than two minutes, it doesn't belong in the standup — it becomes a follow-up or, if serious, triggers the war room.

The weekly review: compare branches by trend

The weekly is where you stop firefighting and look at direction. The core job is comparing branches on the same metrics so you see who is drifting before it becomes a fire.

What numbers to bring

• Delivery and prep times per branch, versus last week.
• Cancellation rate and the main reasons.
• App rating and the volume of complaints, plus recovery done.
• Stock-outs on top items and how often branches went offline.

The rule: every metric is shown the same way for every branch. A branch that's an outlier gets a named owner and a target for next week. The weekly produces a short list of bets, not a report nobody reads.

The war room: an exception, not a habit

A war room is a focused, temporary meeting activated when a single metric crosses a pre-defined threshold — for example, cancellations above a set percentage in a shift, rating dropping below a floor, or a branch offline for too long. It is not a recurring meeting.

What makes it work is defining the trigger before the crisis: the number, who convenes it, and who must attend. A war room runs until the metric is back under control, then it closes. If your war room never ends, it's really a broken weekly.

Common mistakes that kill the ritual

• No trigger number. Meetings without a metric turn into opinion contests.
• No single owner per action. "The team will look into it" means nobody will.
• Numbers gathered by hand. If someone spends 30 minutes in Excel before the meeting, the data is already stale.
• Same meeting for everything. Daily fires and weekly trends need different rooms.
• No follow-up. Yesterday's actions must be the first thing checked today.

A copyable agenda template

Use this as your starting point and adjust the thresholds to your operation:

• Daily (10 min): misses → today's risks → live numbers → actions with owner + time.
• Weekly (30–45 min): branch-by-branch trends → outliers → 3 bets for the week with owners.
• War room (on trigger): confirm the breach → root cause → containment action → close when metric recovers.

Making it stick

A ritual survives because it's short, predictable, and always ends in owned actions. Start with the daily standup this week, add the weekly once it holds, and only define war room triggers after you know your normal ranges. The goal is simple: never operate blind, and never leave a meeting without knowing who moves what by when.

Frequently asked questions