Managers are still doing this by hand

Every Monday, somewhere in your group, somebody rebuilds the same report.

Sales out of the POS. Labor out of the time clock. Invoices out of a folder. A line about what went sideways on Saturday. It all goes into a sheet shaped like last week's sheet, because that is the shape the meeting expects.

I have done this. I built tools for my own managers so they would stop having to. Not because the meeting is pointless — the meeting is where you catch a food cost move before it becomes a period — but because rebuilding the packet is not the meeting. It is the hour spent not talking to the people who could fix the number.

Assembly is not analysis

This is the one I get asked about most, and the one where the pitch gets laziest. Nobody needs another dashboard. Ask around your group how many dashboards already exist and how many get opened on a Monday; the second number is usually zero.

What people need is the same three numbers, in the same place, pulled from the systems they already log into, without a person acting as the pipe.

The tell is copy-paste. If somebody is the connection between three logins and one sheet, you do not have a reporting problem. You have an assembly problem wearing a reporting costume, and buying a better report will not touch it.

The version of this I have seen most: the first twenty minutes of the numbers meeting go on "give me a second, it is still pulling." Nobody in that room thinks the packet is the problem. They think they need a better analyst.

Three numbers, not fifteen

Name the three the meeting actually argues about. Not the fifteen that would be interesting. For most groups it is food cost against theoretical, labor against forecast, and whatever the current fire is.

Pull those three. Check them against the source once, properly, so the room trusts them. Then stop adding columns.

The columns people add "while we're in here" are how a useful packet turns into another thing nobody believes. If a number never changes what anybody does on Tuesday, it does not earn a row.

Worth being honest about the size of this: it is usually a standing export and some glue, not a platform. If your reporting add-on can already schedule it, that is the whole project and it is an afternoon. Unglamorous. It is also the difference between a district manager starting Monday at the variance or starting it at a login screen.

Who still owns the call

The packet is assembled. The reading is not.

Nothing here decides whether a labor overage was a bad schedule or a genuinely busy Saturday. Nothing here decides whether to call the vendor about a price. That is the meeting, and the meeting is the job — this only gets people to it with the numbers already on the table.

If anything ever starts drawing conclusions in that document, take it out. A confident wrong sentence in a packet the room trusts is worse than no packet, because it gets repeated.

Somebody's name on Monday

One person owns the refresh. Not "ops," not "the office." A name.

Same rule I use for anything we set up together: if it only survives while I keep asking about it, it did not work. Write down who runs it, what it looks like when it is right, and what they do when it is not.

The way you know it worked is not a chart. It is that the meeting opens on the variance, because the packet was already there when everyone sat down.

---

If you cannot say for certain where your managers' hours are going, take the free check. Eight questions, no email, and you get the two things I would fix first in your group.