Why weekly manager reports often teach you nothing

Your weekly reports teach you nothing because they describe impressions ("good week", "motivated team", "nothing to report") that nobody can verify or follow up. A useful report separates four things: dated facts, actions taken, results and open items. It leaves the manager what only they know, and pulls the rest from data that already exists.

Sunday night, five reports

The owner of a five-restaurant group opens the reports that came in. The first: "Good week, smooth service." The second: "Nothing to report." The third is a long text about a scheduling conflict. The fourth has not arrived. The fifth says "team a bit tired."

It takes an hour to read them, produces no decision, and the owner decides to call the third manager. They should have called the fourth: the walk-in cooler there was reported broken on Wednesday, in a message that never made it into the report.

Where the uselessness comes from

The report rewards the absence of problems. A manager who flags a difficulty exposes themselves. The one who writes "nothing to report" is left alone. The format teaches people to stay quiet.

It asks for what already exists. Number of incidents, tasks not done, absences: this information is elsewhere. Re-entering it costs time and introduces omissions.

It mixes fact, feeling and request. "The team is tired" is an impression. "Two services in a row without the evening line cook" is a fact. The same paragraph holds both without telling them apart.

It has no memory. A topic noted in week 3 does not come back in week 4. Each report starts from zero, and commitments evaporate.

It is read too late to act on. Received Sunday night for a week that is over, it feeds an observation, not a decision.

A poor report and a good one, side by side

Section	Version that teaches nothing	Usable version
Mood	"Team motivated"	"Two new hires signed off on the cold station this week"
Incident	"A few issues in the kitchen"	"Walk-in cooler down Wednesday 10 pm, technician called Thursday 9 am, not yet repaired"
Action	"We're working on it"	"Technician booked for Friday, stock moved to the neighboring location"
Open item	(missing)	"Walk-in cooler repair: pending since Wednesday, to review Monday"
Need	"Nothing"	"Need a decision on buying a temperature logger"

The method for a report that informs

1. Remove what you already know

List the sections and cross out the ones fed from elsewhere: checklists, incidents, schedule. The manager no longer re-enters them.

2. Keep four short sections

Key facts, actions and results, open items, needs. Half a page. Empty sections are written "nothing to report," which is an answer.

3. Require a fact for anything that matters

If a point is judged important, it comes with a date and a source: who observed it, and when. Minor points do not need one.

4. Accept "nothing to report"

If you pick apart every "nothing to report," you will get novels. If you take it seriously, the manager saves time and you gain credibility.

5. Bring open items back

An item stays in the report until it is closed, with its opening date. This memory belongs in a tool, not in a re-keyed spreadsheet.

6. Reply within 48 hours

A report with no reply stops being read. A short reply to each open item teaches managers that writing things down is worth it.

Pitfalls to avoid

• Adding sections after every problem you run into.
• Using the report to compare or rank managers.
• Reacting sharply to a reported incident, which teaches people to stop reporting.
• Treating reports as a manager attendance check.
• Never rereading the previous report before reading the new one.

What to measure

• The share of reports containing at least one dated fact on an important subject.
• The number of open items that run across several weeks without being closed.
• The time the manager spends filling it in, and the time you spend reading.

Where Tsuno comes in

Tsuno can pre-fill what is already known: tasks from the typical day done or not, incidents, actions taken, logs. The manager adds only what they alone know. Open items come back until they are closed, dated and searchable, with the provenance of each fact. When data is missing, Tsuno says so instead of filling the gap. It does not grade the manager and does not write a judgment about them on their behalf. See the features page.

Further reading

The underlying reasoning, about what a manager really needs, is in managers do not need another dashboard. For the owner's side of the reading, see Monday at 8am: what a multi-site operator really needs to see. Incidents that come back despite reports are covered in why restaurant incidents keep repeating despite reports, and the use of these facts in a one-to-one in how to prepare an employee conversation with facts, not impressions.

Key takeaways

A report informs when it separates facts, actions, results and open items, and does not ask again for what already exists. Allow "nothing to report," bring back what is still open, and reply quickly.