How to Write Daily Reports for Restaurants: Turning the Reasons Behind Sales Gaps and Customer Feedback into Tomorrow's Next Step

Restaurant daily reports tend to fill up with closing figures: sales, number of covers, average spend per customer.

Numbers matter, but on their own they do not capture why the figure came out that way or what to change tomorrow.

In many restaurants, the places to record things are already split.

Sales go into the register close, temperature and cleaning checks into the hygiene records, and clock-in and clock-out times into the attendance system.

The daily report easily becomes a task of copying the same numbers again.

If it is written in the tired hours after closing and nobody who reads it replies, writers gradually fill in only the minimum fields.

In PDCA terms, the report stops at Do, the record of what happened, while Check and Act fall away.

This article looks at how to reposition the daily report from a copy of the closing figures to a tool.

That tool picks up the day's observations and turns them into a next step for tomorrow's service.

Please read it as a discussion about the system, not about blaming anyone.

A restaurant daily report is easier to keep up when the fields are narrowed to roughly the following.

(1) The gap between expected and actual sales and covers, with a word on why it occurred rather than the number alone.

Such reasons include the weather, a nearby event or how reservations came in.

(2) How the peak hours went, such as slow service, guests kept waiting and how tables turned over.

(3) Whether prep was too much or too little, and anything you noticed about waste and food loss.

(4) Items that ran out or sold out, and anything that caught your eye about stock. (5) Customer feedback, including compliments, requests and complaints.

(6) Anything about equipment or hygiene that felt different from usual, such as a refrigerator display or a smell from the drains.

(7) What you want to change tomorrow.

The key is not to repeat every number that already exists in the register close or other records, but to narrow the report to the gap and its reason.

Some observations are small, such as 'service got stuck during the second lunch seating' or 'a regular asked whether the portions had become smaller'.

Conversely, these appear in no other record and can only be picked up in the daily report.

Too many fields stretch the writing time after closing and end up with more blanks. Start with around five and adjust them while listening to the staff.

Keeping the writing order the same every day removes the guesswork.

In the norolu PDCA format, you write P (today's aim), then D (what you actually did), C (what you noticed), A (what you will do tomorrow) and finally the next day's P.

Writing just one line for P before service and filling in D, C and A after closing makes it easier to compare the aim with the result.

Still, on days when every table stays full or the team is short-handed, there is no energy left to write carefully.

Decide in advance that on such days, three lines are enough: the biggest problem, your guess at why it happened, and the one thing you will do first tomorrow.

For example: 'Drinks were slow around 7 p.m. at dinner. One person was covering both the dish station and drinks.

Tomorrow, set out extra glasses before the peak' (a fictional example for illustration).

Even three lines keep the PDCA cycle moving as long as they include a next step.

On days written in the busy-day format, add a short note saying so, and readers will understand the circumstances.

Here are sample reports by role (all are fictional examples for illustration). Sample 1 is from a floor staff member.

P: 'Make seating for the second lunch round smoother and keep guests waiting less.' D: 'Just after noon, five groups were waiting at the entrance.

Clearing could not keep up, and it took a while to seat guests at the tables that opened up.'

C: 'The same person was handling both clearing and seating, so both came to a halt. Only some of the waiting guests were handed a menu while they waited.'

A: 'Tomorrow, assign one person to clearing for 30 minutes from noon. Hand menus to waiting guests first.' Sample 2 is from a kitchen staff member.

P: 'Cut the prep for the daily special to match last week's orders.'

D: 'After cutting the prep, the special sold out before 2 p.m.' C: 'The daily special seems to sell well on rainy days.

Cutting prep to match the slow days was premature.'

A: 'At tomorrow's meeting, suggest to the manager that we decide prep quantities after checking the weather forecast.'

In both cases, one to three lines per field is enough.

Sample 3 is from the restaurant manager. P: 'Make sure everyone can recommend the new seasonal menu to guests in a single sentence.'

D: 'I explained it before opening, but it had not reached the evening shift. Orders for the seasonal menu were lower at dinner than at lunch.'

C: 'The explanation was given only at the lunch briefing, and there was no moment to pass it on when the evening shift started.

The way staff phrased the recommendation also varied from person to person.'

A: 'Turn the recommendation into a short sentence and read it together at the start of each shift.'

Next day's P: 'Spend one minute reading it together at the start of the lunch and dinner shifts, and check the dinner orders.'

The trick to linking to the next day's P is to write A as one concrete thing to do next, in a form that the next day's report can check.

Rather than 'improve customer service', write 'hand menus to waiting guests first', and you will know tomorrow whether it was done.

This flow, in which yesterday's A becomes today's P, is what builds small improvements in the restaurant one after another.

Notes such as 'a guest pointed out that the dish was cold' or 'a guest asked about allergies and I could not answer right away' sometimes appear in the C field.

Do not let them end in the daily report; connect them to the response procedures the restaurant or company has set.

There are responses to complaints, questions about ingredients such as allergens, and guests reporting that they feel unwell.

These should each follow your company's procedures and the judgment of the person in charge.

When a guest raises anything related to their health or an injury, do not wait until you write the daily report; tell the manager or person in charge on the spot.

The daily report is the point where something is noticed; it is not the response itself.

A short line such as 'reported to the manager' or 'shared with head office' lets the reader confirm that it reached the formal response.

It is also reassuring to keep information that identifies individuals, such as guests' names, contact details or appearance, out of the daily report.

Recording compliments in the same way encourages the staff and shows which good habits are worth keeping.

A restaurant already has established records.

They include hygiene records such as refrigerator temperature checks, cleaning and sanitizing checks and staff health checks.

As well as these, there are the register close and sales totals, and attendance records.

These are kept in their own places, based on the company's hygiene management plan and designated forms, and its accounting and attendance rules.

The daily report does not replace them.

Assume that simply writing 'checked the refrigerator temperature' in a daily report cannot be treated as a hygiene record. The basic split is this.

The established records hold the facts, kept on the designated forms and in line with the designated procedures.

The daily report, meanwhile, holds the team's own actions, observations and next steps. When a daily report mentions these, do not repeat the details.

Add a short note such as 'temperature abnormality entered in the hygiene record' or 'register discrepancy reported to the manager'.

For which items to record and how to keep them, follow your company's rules, the person in charge of hygiene, and guidance from your local public health office or similar authorities.

Drawing this line at the start reduces both the burden of writing things twice and the risk of the daily report being treated as a substitute for other records.

Here are five gaps often seen in restaurant daily reports. The first is numbers with no reason.

Do not stop at 'sales were low'; add a word on the likely reason. The second is ending with 'it was busy' or 'nothing to report'.

Within a busy day, writing just one moment where things got stuck is enough. The third is an abstract A, such as 'do my best' or 'be careful'.

Write it as an action whose completion can be checked tomorrow.

The fourth is observations not being passed between lunch and dinner or between early and late shifts.

Making it a habit to read the previous shift's A at the start of the next shift makes the chain less likely to break.

The fifth is writing in a way that blames individual guests or staff.

Instead of recording it as someone's mistake, write what happened and which part of the system to change.

When you find a gap, rather than blaming the writer, review whether the fields and the writing time fit the way the restaurant operates.

Restaurant managers and area managers read reports from several staff members or locations. Trying to read every one in depth is not sustainable.

So start with A (what you will do tomorrow), then check C (what you noticed) for anything that needs discussion or any customer complaints.

Comments are easier to keep up when they acknowledge one fact and add a single question or next step. For example: 'Good idea to assign someone to clearing.

Let me know how many groups were waiting tomorrow.' Once a week, lay out the week's reports and look back over them.

Discussing them in the KPT format (Keep, Problem, Try) lets you check whether the same time slot keeps getting stuck.

It also lets you check how the ideas you tried worked out. That turns daily observations into improvements for the restaurant.

Where there are several locations, it is also a chance to share an idea that worked at one location with the others.

With the weekly summary in norolu PDCA, you can also look back over a week of observations at once.

In norolu PDCA, AI is an assistant that helps with drafting reports, asking questions to prompt reflection, and writing weekly summaries.

That line does not change in a restaurant. AI can tidy up a staff member's short notes or pick out observations that recur across a week of reports.

But decisions such as whether to change the menu or prep quantities are made by the manager or the person in charge.

So are decisions on how to respond to a complaint, or how to arrange the shifts.

It is also reassuring to keep information that must not leave the company out of the daily report.

That includes guests' personal information, terms with suppliers and food costs.

As for norolu PDCA, it is designed so that daily report data is recorded in the Google Drive (spreadsheet) of the company using it.

That is, the data goes to your own organisation, following a minimal data retention approach that does not accumulate information on our side.

Keep it separate from the established records, use a short format, and keep writing reports that get a reply.

We believe that steady habit is the foundation for turning small observations during service into tomorrow's next step and into improvements for the restaurant.