How to know which restaurant needs you tomorrow

To know which restaurant needs you tomorrow, rank what comes in by severity, recurrence and lack of follow-through, not by message volume. The location that calls you ten times is not always the one that needs you most. The one that stays quiet may be doing very well, or may have stopped reporting. The facts should settle it, with their source visible.

Sunday, 9 pm, four locations

You run four restaurants. Tomorrow you have a free half day. Your phone shows three messages from the second location's manager, one from the fourth, none from the first or the third. You decide to go to the second: it wrote the most.

On Wednesday you learn that the third location has had no front-of-house lead for ten days and nobody mentioned it. The second location's manager wrote a lot because they like to keep you informed. Their site was running very well.

Why you pick the wrong location

Message volume measures temperament, not severity. Some managers write everything, others write nothing. Ranking by noise favors the first group and hides the second.

Signals are scattered. An incident sits in a message, an absence in the schedule, a missing log on a sheet. Nobody lays them side by side, so no location stands out.

The latest event overshadows everything else. A recent customer complaint dominates your thinking, while an older, more repeated problem stays invisible.

"No problem" and "no information" are not told apart. This is the costliest one, because it creates a false sense of security.

Three questions to ask yourself every evening

1. What is serious, in the sense that a decision must be made within 24 hours?
2. What keeps recurring at the same location, even if each occurrence looks minor?
3. What was requested or decided and has not been dealt with?

The third is the one people forget. Commitments that are not kept signal a location under strain before customers see it.

A grid for sorting what comes in

Category	Definition	What you do
Urgent	Food safety risk, safety, short-staffed for the next service	Decide today, go in person or make a targeted call
Follow-up	Open item with a due date or an owner	Check it on the due date, without going through the phone
Information	A finding with no action expected	Read, file
Silence	No data received on an expected item	Go and find out what is missing before concluding all is well

The "silence" row is the most useful. A temperature log that was expected and is missing is not the same thing as a compliant log.

A five-step method

Define what must be reported

Decide once, with your managers, what gets flagged and how: incidents, absences, tasks from the typical day not done, missing logs. Format: a short list posted in the back office.

Record facts at the source

Each fact is logged by the person who sees it, with the date. No rewording by a third party. A fact has a provenance: measured, reported, observed.

Read it the evening before or in the morning

Ten minutes of reading, always at the same time. The habit matters more than the tool.

Decide, then write down why

If you go to the third location rather than the second, note the reason in one sentence. In three months, you will know why.

Check after the visit

A follow-up closes when the fact is dealt with, not when you have been there. Come back to it on the planned date.

A fictional example of sorting

Three locations, one evening: the first has two messages about an oven breakdown already repaired (information), the second has an opening task left undone three days in a row (follow-up, recurring), the third has sent no temperature log for two days (silence). You visit the third first, then the second.

Common mistakes

• Doing a purely calendar-based round that ignores the signals.
• Reading every summary without being able to open the facts behind it.
• Treating the manager who writes little as a manager with nothing to say.
• Traveling to fix by hand something that should be settled by message.
• Never noting the reason behind a decision to visit.

What to measure

• The share of your visits that respond to an identified fact, as opposed to a routine visit.
• The number of open items with no due date, per location.
• The delay between a fact observed at a location and the moment you become aware of it.

Where Tsuno comes in

Tsuno keeps dated, searchable records of observed facts, actions taken and what has not been dealt with, along with their provenance. In the morning, you can ask: "What deserves my attention today?" or "What have my managers not dealt with?", from Tsuno or from your own AI. The answer is short and lists the items behind it. When data is missing, Tsuno says so instead of making something up. It does not rank managers and does not decide for you: it prepares, you choose. See the solution page.

Further reading

The overall logic is in how to manage multiple restaurants without being everywhere. To build your start-of-week review, read Monday at 8am: what a multi-site operator really needs to see. If you are wondering whether to hand this work to someone, see when does a restaurant group need a multi-site supervisor. And to understand why drift is discovered late, why restaurant owners discover cost drift too late.

Key takeaways

Choosing where to go tomorrow means sorting by severity, recurrence and lack of follow-through, and treating silence as a question rather than good news. Keep the source of each fact, and write down the reason behind your visits.