Control Room · Ops

The Morning Metrics Checklist for Multi-Location Delivery Operations

The morning metrics to check first in multi-location delivery are the ones that break the fastest: prep and delivery times, cancellation and rejection rates, app ratings and open complaints, and stock or item availability. Scan them per location in one view, flag anything outside your normal range, and turn each red number into a single owner and action before the lunch rush starts.

By Control Room · 2026-08-09 · 5 min read

Running delivery across several locations means you can't watch every kitchen at once. The first hour of the day sets the tone: either you catch what's already broken and fix it before lunch, or you find out at 2 p.m. when the ratings drop and cancellations pile up. A tight morning checklist — the same numbers, in the same order, every day — is how ops teams stay ahead instead of reacting. This is what to look at, in what order, and how to read it without drowning in spreadsheets.

Why a morning ritual beats a dashboard

A dashboard shows you everything. A ritual tells you what to do. The goal of a morning scan is not to admire charts — it's to answer three questions in under ten minutes: What's abnormal today? Which location owns it? What moves before the rush?

Multi-location delivery fails quietly. One store's prep time creeps up by four minutes, another rejects a handful of orders during a short-staffed shift, a third runs out of a hero item. None of these are dramatic on their own, but stacked across locations they quietly bleed rating and revenue. A consistent checklist forces the abnormal to surface next to the normal, so you compare instead of guess.

The five metrics to check first

These are ordered by how fast they hurt you. If you only have five minutes, this is the sequence.

1. Prep and delivery times

Time is the first thing that breaks and the first thing customers feel. Check average prep time and total delivery time per location against your normal band. A store trending high before noon usually means understaffing, a slow station, or a menu item that's jamming the line. Flag anything more than a few minutes over baseline — it compounds fast once volume climbs.

2. Cancellations and rejections

Cancellations and store-side rejections are pure lost money plus a rating hit. Separate who cancelled: customer, platform, or store. Store rejections are the ones you control — they usually signal the location turned off items, couldn't keep up, or paused without telling anyone. A spike here at one location is your loudest early warning.

3. App ratings and open complaints

Ratings on the delivery apps are a lagging number, but new complaints are live. Scan for fresh 1- and 2-star reviews and unresolved messages per location. A cluster of complaints about the same thing — missing items, cold food, long waits — points straight at a process, not bad luck. This is where recovery starts: respond fast, and fix the cause upstream.

4. Item and stock availability

An item marked unavailable is an order you never got the chance to lose. Check what's turned off per location and why. Sometimes it's a genuine stockout; often it's a store that paused an item on a busy night and never turned it back on. Unavailable hero items quietly cap your revenue all day.

5. Order volume and acceptance pace

Finally, glance at volume versus a normal day and how quickly orders are being accepted. A location accepting slowly is about to rack up cancellations and rating damage. Low volume at a store that's usually busy can mean it's accidentally offline, throttled, or showing as closed on an app.

How to compare locations without living in Excel

The Excel trap is real: someone exports data from three apps, pastes it into a sheet, colors some cells red, and by the time it's ready the shift is half over. That's reporting, not operating.

To compare locations fast, apply three rules:

• Same metrics, same order, every day. Consistency is what makes an outlier obvious. If the layout changes daily, your brain re-learns it instead of reacting.
• Baselines, not raw numbers. A 22-minute prep time means nothing until you know that store's normal is 15. Compare each location to its own recent normal, then to its peers.
• Rank by exception, not by name. You don't need to read every store's numbers. Surface the ones outside their band and ignore the rest. Green stores don't need your morning.

The point is to spend your attention on the two or three locations that are off, not to audit all of them. If your current process makes you read everything to find the exceptions, the process is the problem.

Turn each red number into one action

A metric only matters if it ends in a decision. For every flag on your morning scan, name a single owner and a single next move. Some examples of dato-to-action:

1. Prep time high at Store 3 → message the manager to check station load and pull someone to expo for the next two hours.
2. Store rejections spiking at Store 1 → confirm they're actually staffed and open; find out what got paused and why.
3. Cluster of "missing item" complaints at Store 5 → tighten the bagging/checklist step for the shift and reply to the affected customers now.
4. Hero item unavailable at two stores → confirm real stockout vs. accidental pause, and set a rule to re-enable at open.

One number, one owner, one action, one deadline. That's the whole discipline. Without it, a morning checklist becomes another report nobody acts on.

Common mistakes that quietly cost you

• Checking too late. A 1 p.m. review catches problems after they've already damaged the lunch service. The window that matters is before the rush.
• Watching averages that hide the outlier. A company-wide average delivery time looks fine while one location is on fire. Always break it down per location.
• Confusing lagging and live signals. Ratings tell you what already happened; times, rejections and complaints tell you what's happening now. Act on the live ones.
• No owner. A red cell with no name attached gets seen, nodded at, and forgotten. Every flag needs a person.
• Rebuilding the view every morning. If your first 20 minutes go to exporting and formatting, you're doing data entry, not operations.

Make it a ritual, not a heroic effort

The teams that run delivery well don't have better data than everyone else — they have a shorter, more consistent way of reading it. Run the same five-metric scan at the same time every morning, compare each location to its own baseline, and close every flag with an owner and an action. Do that daily and the war room becomes rare, because you're catching problems while they're still four-minute creeps instead of two-star reviews.

Frequently asked questions