What a Weekly Restaurant Analytics Digest Should Include

A lot of weekly restaurant reports end up being skimmed once, mildly interesting, and then ignored the next week because there's no clear connection between the numbers and what to actually do about them. A digest worth reading is built backward from the decisions it's meant to support.

What belongs at the top

Lead with movement, not totals. A static number, this dish sold 40 times, is less useful than a comparison, this dish's orders dropped 20% from last week. Owners are busy, and the first line of a digest should answer, in a glance, whether anything needs attention this week or whether things are steady.

The core sections worth including

• Dishes with a notable change in order volume or reorder rate, up or down
• Verdict trends for your top and bottom performing dishes
• Any allergen tags still sitting unconfirmed in a sign-off queue
• A short note on overall guest engagement with the menu, not just sales
• One or two specific, suggested actions, not just raw numbers left for you to interpret

What to leave out

Resist the urge to include everything measurable just because it's available. A digest with fifteen metrics gets skimmed and forgotten. A digest with four or five that consistently point toward a decision gets read every week. If a metric hasn't led to a single decision in two months, it probably doesn't belong at the top of the report, even if it's interesting in theory.

Make it something you'd actually act on

The real test of a weekly digest is whether reading it changes what you do that week, even in a small way, adjusting a description, checking in on a dish that's slipping, confirming an allergen tag that's been sitting unreviewed. If a digest never changes a single action, it's just noise with a nice layout.

A sample digest, laid out the way it should actually read

A useful digest for a mid-size restaurant might read something like this: two dishes trending up in reorder rate this week, worth noting but not urgent. One dish's like rate dropped noticeably compared to its usual pattern, worth a kitchen check this week. Three allergen tags are sitting unconfirmed and need sign-off before the weekend rush. Overall guest engagement with the menu is steady compared to last week. That's four sentences, each pointing at something specific, rather than twenty rows of numbers with no clear next step attached to any of them.

Who should actually receive it

In a small restaurant, the digest usually just goes to the owner. In anything larger, it's worth deciding deliberately who else sees it, a head chef probably cares most about the verdict and spice-related sections, while a manager handling service probably cares more about allergen sign-offs and guest engagement trends. Sending the same full report to everyone often means each person skims past the two lines that were actually meant for them, buried among sections meant for someone else's role.

How this differs from a monthly deep dive

A weekly digest and a monthly review aren't the same document doing the same job. The weekly version should be short and focused on what changed since last week. A monthly review has room for slower-moving questions, whether it's time to retire a dish for good, whether a broader repositioning across the menu is worth testing, whether pricing needs a second look. Trying to cram monthly-level analysis into a weekly digest is usually what makes people stop reading it after a few weeks.

A good habit is to treat the weekly digest as the thing that flags candidates, and the monthly review as the place those candidates actually get decided on, rather than trying to make every weekly read end in a final decision.

TasteGraph's reporting is built around this same principle, surfacing dish-level movement and pending allergen sign-offs clearly, so a weekly check-in gives you something specific to act on rather than a wall of numbers to scroll past, with the option to go deeper in a monthly view when a slower-moving decision actually calls for it.