A service report the whole team can read

At the end of a busy Friday, the manager knows a great deal that nobody else does. Covers were up on last week, the grill fell behind for twenty minutes at eight, two dishes were sent back cold, a table of six left a glowing comment and table nine waited too long for its bill. By Saturday afternoon, most of that will be forgotten, and the team will start the next service without knowing any of it.

A service report fixes that. It is one page, written after each service, that tells the whole team how the service went: the covers, the spend, the ticket times, the voids and comps and one note about what to do differently. Posted where everyone sees it, it turns what the manager knows into something the team can act on.

This guide covers what to put in it, what to leave out, how to write it in ten minutes, where to post it and how to keep the team reading it. Every venue and figure in it is an example.

A service report is a short summary of one service, written for the people who worked it and the people who will work the next one. It records what happened, how it compared with what was expected and the one thing to change next time.

It borrows from the after-action review, a habit armies and hospitals use: what was supposed to happen, what actually happened, why there was a difference and what to do about it. The restaurant version is lighter, but the questions are the same.

One page is a discipline. A report that runs to three pages is written for the manager's own records, and nobody else reads it. A report of one page, with five or six lines of figures and a few sentences of words, is read by the chef on their break and the server before their shift.

It also forces choices. With only one page, the manager has to decide what mattered most about the service, which is itself the most useful part of writing it.

The service report is for the whole team, not only the managers. The kitchen wants to know how the tickets ran and which dishes came back. The floor wants to know how the covers went and what guests said. The bar wants to know how drinks sold and whether they kept up.

Writing for all of them changes the tone. A report for the owner can use shorthand and percentages. A report for the team uses plain words, explains what the numbers mean and says what the team did well as well as what went wrong.

Most service reports need five lines of figures. Covers, against what was expected. Spend per head, against the usual for that service. Ticket times, at the median and at the slow end. Voids and comps, by count and by reason. And a feedback line, with what guests said.

Five lines can be read in under a minute. Each one answers a question the team cares about: how busy were we, how much did guests spend, how fast was the food, what went wrong and how did guests feel about it.

Start with covers, because they set the context for everything else. Seventy covers on a night that expected eighty explains a quiet room; ninety on a night that expected seventy explains slow tickets.

Compare with what was expected rather than only with last week. If the diary said eighty and seventy came, the gap is worth a line: were there no-shows, cancellations or fewer walk-ins than usual? Each points to a different fix.

Spend per head shows how much each guest spent, on average. It moves with the menu, the mix of guests and how well the team recommended drinks, sides and desserts.

Report it against the usual for that service, not against the best night of the year. A Tuesday lunch and a Saturday dinner have very different spends, and comparing them tells the team nothing useful. A small rise or fall from the usual is worth noticing; a large one is worth a sentence explaining why.

Ticket times, how long the kitchen took from order to pass, are the kitchen's line in the report. Report the typical time and the slow end, because the slow tickets are the ones guests remember and the ones that show where the kitchen struggled.

Say when the slow tickets happened and at which station, if you know. "Grill tickets ran slow between eight and half past" is far more useful than "tickets were slow". Our guide to ticket times: the only kitchen metric that moves covers how to read them.

Voids and comps show what went wrong. A void is an item taken off a bill, often because it was entered by mistake. A comp is an item given free, often to make up for a problem. Both cost money, and both tell a story.

Report the count and, more usefully, the reasons. "Three comps: two cold mains, one long wait" tells the kitchen and the floor exactly where the service slipped. A high count with no reasons recorded is a sign the team needs reminding to record them.

Feedback scores show how guests felt. If the venue collects feedback after visits, report the number of responses from that service, any low ratings and a short quote from a comment, good or bad.

A single quote often does more than any number. "The fish was the best I have had this year" or "we waited forty minutes for our mains" puts the guest's voice in front of the team in a way that a rating out of five never quite does.

End with one note: the single thing to do differently next time. Not a list of everything that went wrong, but the one change that would have made the biggest difference.

"Prep a second tray of garnish for the grill before seven" or "check the bills on the terrace every ten minutes after nine" gives the next service something concrete to do. A list of ten things gives it nothing it will remember.

Leave out anything the team cannot act on. Labour cost percentages, food cost and the month's profit belong in the manager's reports, not in the service report. So do comparisons the team has no control over, such as rent or energy.

Leave out names in criticism. If a server made a mistake, talk to them directly. A report posted for the whole team that names someone for a mistake damages trust far more than it improves anything.

A service report should take no more than ten minutes to write. Keep a template with the five lines and the note, fill in the figures from the reports, and write a few sentences about what stood out.

If it takes longer, the template is too long or the figures are too hard to find. Simplify until it takes ten minutes, because a report that takes an hour will stop being written within a month.

Write it straight after service if you can, while the details are fresh. The cold mains, the grill falling behind, the glowing comment: all are clearest in the hour after the last table leaves.

If writing it at close is impossible, write it first thing the next morning, before the next service starts. A report written two days later has lost most of its value, because the team has already worked another service without it.

Post it where the team will see it. A board in the staff area, a group message, the start of the pre-shift briefing: wherever the team already looks. A report filed in a drawer helps nobody.

Many venues read it aloud at the next briefing as well. Two minutes at the start of the shift, going over the last service's report and the one note, makes sure everyone has heard it, including those who do not read noticeboards.

Numbers say what happened; words say why. Each figure in the report deserves a few words of explanation when it moved: covers down because of rain, spend up because the new dessert sold well, tickets slow because the grill was a cook short.

Without the words, the team sees numbers rising and falling and draws its own conclusions, often the wrong ones. With them, the report becomes a short story of the service that everyone understands.

A service report that only records problems becomes something the team dreads. Include what went well: the record covers, the comment praising a server, the kitchen that kept every ticket under fifteen minutes on a full night.

Praise in a report the whole team reads is worth more than praise in private, because everyone sees it. It also makes the report something people want to read, which is the only way the problems in it get noticed too.

Describe problems as things that happened, not as someone's fault. "Two mains went out cold between eight and half past" invites the team to work out why. "The pass let two cold mains through" puts one person on the defensive.

The aim is to fix the problem, not to find someone to blame. A report that treats problems as shared puzzles gets the team suggesting solutions; one that blames gets the team hiding mistakes.

For the kitchen, the most useful lines are the ticket times, the dishes sent back and the dishes that sold most and least. A chef who sees that the special sold out by eight knows to prep more next time; one who sees that a dish came back three times knows to check it.

Keep the kitchen's section short and concrete. Ticket times, returns with reasons, and anything that ran out. The kitchen will read it if it is about their work and takes a minute.

For the floor, the most useful lines are covers, spend per head, the feedback and anything about waits: for tables, for food, for the bill. A server who sees that guests on the terrace waited too long for their bills knows to check the terrace more often.

Include the guest comments that mention service by name, good or bad, with care. Praise by name is welcome in front of the team; criticism by name belongs in a private conversation.

For the bar, the useful lines are drinks sales, waits for drinks and anything that ran out. If drinks orders backed up at the peak, or a popular wine ran out at nine, the bar team needs to know before the next busy night.

Bars are often left out of service reports, because the figures are folded into the totals. A single line for the bar, even just "drinks kept up all night, the house red ran low by ten", tells them their work is noticed.

A shift report and a service report are different documents for different readers. The shift report is for managers: takings, the cash up, the tenders, staffing and incidents. The service report is for the team: how the service went and what to change.

Many venues produce both, from the same figures. Our guide to shift reports a manager reads in two minutes covers the manager's version.

The daily report looks at yesterday from the manager's desk, before today begins: sales, covers, labour and what to change today. The service report is written for the team, after each service. A venue that runs lunch and dinner may write two service reports a day and one daily report.

They feed each other. The service reports give the daily report its detail, and the daily report gathers the day's lessons. Our guide to the daily report: five lines before you open covers the manager's morning version.

At the end of the week, the service reports become the raw material for the weekly review. Reading back a week of one notes shows the patterns: the grill always behind on Fridays, the terrace bills always slow, the new dessert always selling out.

Patterns that appear in several reports deserve a fix that lasts, not another note. Our guide to a weekly review that takes thirty minutes covers how to turn the week's reports into a short list of changes.

Keep the same format, in the same order, every time. The team learns where to look for the line they care about, and the reports become easy to compare from one service to the next.

Change the format only when something in it is not working, and tell the team why. A report that changes shape every week is harder to read and easier to ignore.

Some services are quiet and uneventful, and the report still matters. A line saying covers were below plan because of the weather, ticket times were quick and nothing went wrong tells the team the quiet was expected and the service was well run.

Quiet services are also the best time to try something and report on it: a new dish offered at every table, a different order of service, a new server shadowing an experienced one. The report records the result, so the idea can be judged on more than one person's memory.

The team will act on the report only if they trust its figures. If covers are wrong because walk-ins were not recorded, or comps are missing because nobody entered a reason, the report stops matching what the team saw, and they stop believing it.

Ask the team to record what the report needs: walk-ins at the door, reasons for comps and voids, and dishes sent back. Explain that the report is only as good as what is recorded during the service, and thank those who keep it accurate.

A simple template has six parts:

Add a line of praise and a line for the bar if they fit. Keep it to one page, and the team will read it.

If the team stops reading the service report, ask why. It may have grown too long, become a list of complaints, or stopped changing anything. A note that appears every week without anything happening teaches the team that the notes do not matter.

Fix the cause. Shorten it, add the praise back, read it aloud at briefings and, above all, act on the notes. A report that leads to visible changes is one the team will keep reading.

An invented bistro's manager writes a service report after each dinner. On one busy night: covers 92 against 85 expected, thanks to walk-ins after a nearby concert; spend per head slightly below the usual, because many concert guests ordered one course; ticket times typical at twelve minutes, slowest at twenty-six, all on the grill between eight and half past.

Two comps for cold mains, both from the grill rush. Four feedback responses, one low rating about the wait, one comment praising the new dessert. One note: on concert nights, add a second cook on the grill from half past seven. The report goes on the staff board and is read at the next briefing, and the next concert night runs smoothly.

servearound does not write a service report or send one at close, and it has no end-of-day close of its own. The figures for one are in its reports, set to Today or Yesterday on the venue's own clock. Reservation analytics show covers, bookings and the no-show rate, each against the period of the same length just before, with covers by shift. Payment analytics show revenue by hour and voids and comps by member of staff, and order analytics show the average check and the void and comp rates.

Kitchen analytics show tickets completed, the median and 90th percentile prep times, the share of tickets ready within fifteen minutes of being sent, the remake rate, times by station and the slowest tickets with their dishes. The Feedback tab lists responses for any dates with their overall, food, service and ambience ratings, and its Needs attention view gathers the low ratings to read first. See Analytics and point of sale and kitchen.

A one-page summary of a service for the whole team: covers, spend, ticket times, voids and comps, feedback and one note.

About ten minutes, using a template filled from the reports.

Straight after service, or first thing the next morning at the latest.

Wherever the team already looks: a staff board, a group message or the pre-shift briefing.

Only in praise. Criticism belongs in a private conversation.

A shift report is for managers, with takings and the cash up. A service report is for the team.

One: the single change that would make the biggest difference.

Shorten it, add praise, read it at briefings and act on the notes.

A service report is one page, written after each service, that tells the whole team how it went: covers against the plan, spend per head, ticket times, voids and comps with their reasons, feedback scores and one note about what to do differently. It takes ten minutes, it uses plain words and it is posted where the team already looks.

Keep it consistent, include praise, describe problems without blame and act on the notes, because a report that changes nothing stops being read. Use it alongside the managers' shift reports, gather its lessons into the daily report and the weekly review, and the team will start each service knowing what the last one taught.