Guides

What a meal delivery dashboard should actually show

The test of a dashboard is whether anyone opens it before noon. Reports get opened monthly; operating tools get opened daily, and the difference is entirely in what they show.

Report versus operating tool

A reportAn operating tool
Revenue last month.Selections still empty before tonight’s cut-off.
Total customers.Terms expiring in the next fortnight.
Deliveries completed.Stops that failed and have not been actioned.
Meals produced.Allergen conflicts on today’s production.
Churn rate.Customers paused for more than sixty days.

Everything on the right has a deadline

That is the whole principle. An item earns dashboard space when acting on it today produces a different outcome from acting on it next week. Everything else is a report, and reports belong somewhere you visit deliberately.

Applied honestly, this shrinks most dashboards considerably — which is the point. A screen with forty tiles is a screen nobody reads.

Two numbers worth keeping anyway

Recurring revenue and meals per week, provided both are derived from live plan records rather than from last month’s invoices. Derived, they move the same week a wave of pauses lands, which makes them operational rather than historical.

Reported from invoices, they tell you in arrears what you could have seen at the time, and they belong with the rest of the reporting.

Design it for the worst morning, not the best

The dashboard that matters is the one someone opens on a morning where two people called in sick and a supplier delivered short. On that day nobody reads a chart; they want to know what will go wrong today unless somebody intervenes.

That is a useful design constraint. If a tile would not be looked at on the worst morning of the month, it is competing for attention with the tiles that would be, and it should move to the reporting screen.

It also argues for plain numbers over visualisation. A count of unresolved failed stops is read in a second; the same figure rendered as a sparkline is decoration on a day when seconds matter.

Common questions

What earns a place on an operations dashboard?
Anything where acting today produces a different outcome from acting next week. If the answer is the same either way, it is a report and belongs somewhere you visit deliberately.
Should revenue be on the dashboard?
Only if it is derived from live plans rather than historic invoices. Derived, it moves the week a wave of pauses lands; reported from invoices, it tells you in arrears.
How many items should a dashboard have?
Fewer than most have. A screen with forty tiles is one nobody reads, and the deadline test usually removes most of them without losing anything anyone acted on.

See how this works in practice

The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.