Acting on feedback: the Monday meeting item

A restaurant collects feedback diligently. Every guest receives a short survey after their visit, servers note comments at the table and the manager reads the online reviews. At the end of the month, there are two hundred comments, an average rating and a vague sense that the service is sometimes slow. Nothing changes. The next month, the same comments arrive.

Collecting feedback is the easy part. Acting on feedback is where most venues stop, because two hundred comments feel overwhelming, the manager is busy and nobody owns the job of turning comments into changes. Feedback that is collected and never acted on is decoration: it looks good, and it does nothing.

This guide covers how to turn a month of guest feedback into two changes the team can make, the weekly habit that keeps it going, how to count complaint patterns rather than skim them and how to tell guests and staff what changed. Every venue and figure in it is an example.

Feedback becomes decoration for three reasons. There is too much of it to read properly, so it is skimmed. Nobody owns it, so it is everyone's job and nobody's. And there is no regular moment to act on it, so it waits for a quiet week that never comes.

The fix for all three is a weekly habit: one item on the Monday meeting's agenda, with an owner, a simple method and a rule that every week ends with a decision.

Make guest feedback a standing item on a weekly meeting, such as the Monday meeting where the manager and senior staff review the past week. Give it fifteen minutes, every week, whatever else is on the agenda.

A standing item turns feedback from something that happens when there is time into something that happens every week. Our guide to a weekly review that takes thirty minutes covers how to fit it alongside the other numbers.

One person should own the feedback item: usually the general manager or an assistant manager. They read the week's feedback before the meeting, prepare a short summary and make sure each decision is followed through.

Ownership matters more than method. A venue with a simple method and a clear owner acts on feedback; one with a sophisticated method and no owner does not.

Feedback arrives from many places: surveys after the visit, comments at the table, complaints to the manager, online reviews, messages on social media. Bring it together once a week, in one place, so the patterns can be seen.

A simple sheet is enough: the date, the source, what the guest said and the topic. Our guide to guest feedback you can actually act on covers collecting it in a form that is easy to use.

A simple sheet is all the method needs. One row per comment, with columns for the date, the source, the service, a short summary, the topic and whether it was praise or a complaint. At the foot, a count for each topic.

Keep the list of topics short and stable, so this month's counts can be compared with last month's: food quality, food temperature, speed of service, staff, atmosphere, noise, value, the bill, cleanliness and anything else that keeps appearing.

The most important step is counting. Read each comment and give it a topic: slow service, food temperature, noise, a particular dish, the bill, a member of staff, value. Then count how many comments fall under each topic.

Counting turns a pile of comments into complaint patterns. "Several people said the service was slow" becomes "fourteen comments this month mentioned waiting for the bill". The second is something you can act on; the first is a feeling.

Count praise as well as complaints. Knowing what guests love tells you what to protect.

A single complaint may be bad luck. The same complaint four times in a month is a pattern. Look for the themes that appear again and again, especially across different sources: the same comment in surveys, at the table and in reviews is very likely to be real.

Look for patterns by time too. A complaint that appears mostly on Fridays, at lunch or in one section of the room points to a cause: staffing, a menu item or the layout.

Not every theme is equal. A comment about an allergy handled badly matters more than ten comments about the music, because it is about safety. Put safety and serious complaints first, then the themes that appear most often, then the rest.

A theme that appears often but costs nothing to fix, such as slow water, is worth acting on quickly. One that appears rarely but would be expensive to fix, such as the layout of the room, may need to wait for the right moment.

Split the themes by service and by day. A complaint about slow food that appears mostly on Saturday nights points to a staffing or kitchen problem on Saturdays, not to slow food in general. A comment about noise that appears only at lunch may point to a particular group of tables.

The split turns a general theme into a specific cause, and a specific cause is something you can fix.

Feedback scores, such as the average overall rating or the ratings for food and service, are useful as a trend, not as a single number. Track them week by week and month by month, and look at the direction rather than the exact figure.

A falling service score over three months tells you something is slipping; a rise after a change tells you the change worked. Look at the number of responses alongside the score, because a score from five responses means far less than one from fifty.

In a group, compare feedback across venues: the same topics, the same scale, the same period. A venue whose service scores lag the others may need help; one whose food scores lead may have something worth sharing.

Compare fairly. A busy city venue and a quiet neighbourhood one will attract different comments. Look at each venue's trend as well as its position against the others.

Sometimes a theme points at one member of staff: several comments about the same server, good or bad. Praise should be shared with them and the team. Criticism should be handled privately and fairly, looking at the whole picture before drawing conclusions.

Never read out a guest's criticism of a named colleague at the team meeting. Deal with it one to one, with support and a chance to improve.

From the month's patterns, choose two changes, no more. One change is often too few to keep momentum; five are too many to do well. Two is enough to make a difference and few enough to finish.

Choose the changes that address the biggest patterns and that the team can actually make. "Bring the bill within two minutes of being asked" is a change; "improve the service" is not. Each change should be specific, have an owner and have a date.

The best changes become service standards: specific actions the team takes every time. If guests complain about waiting for water, the change becomes "offer water within two minutes of seating". If they complain about cold food, it becomes "plates leave the pass within a minute of being ready".

Writing the change as a standard makes it stick, because it becomes part of how the team works rather than a one-off effort. Our guide to service standards written as actions, not values covers how to write them.

When you make a change because of feedback, tell the team why. Share the pattern: "Fourteen guests this month mentioned waiting for the bill." Explain the change and what it should fix. A team that understands why a change matters takes it seriously.

Share good feedback too. A kitchen that hears that guests loved a new dish, or a server who hears they were praised by name, works with more pride. Feedback is not only about problems.

A month after a change, check whether it worked. Did the complaint pattern shrink? Did the relevant score rise? Did the team keep to the new standard?

If it worked, keep it and choose the next change. If it did not, look at why: was the change not followed, or did it not address the real cause? Adjust and try again. That loop, plan, act, check and adjust, is the same idea as the PDCA cycle used in many businesses.

Some changes can be made the same week: a new standard for water, a second runner on Fridays, a dish's seasoning adjusted. Others need time or money: a new extraction system for a smoky dining room, a change to the layout, a new supplier.

Choose at least one quick win each month, so the team and guests see feedback turning into action. Plan the bigger changes separately, with a date and a budget.

Food feedback belongs with the kitchen. Share the food themes with the head chef every week: which dishes are praised, which are criticised and why. Let the chef decide how to respond, whether by changing a recipe, a portion or the timing on the pass.

A kitchen that hears guests' feedback regularly, good and bad, improves faster than one that only hears about complaints.

Some guests ask to be contacted about their feedback. Reply to them, promptly and personally, especially when they had a poor experience. A sincere reply, with what you have done, often turns an unhappy guest into a returning one.

Keep the reply short and specific. Thank them, acknowledge what went wrong, say what you have changed and invite them back. Do not send a template that ignores what they said.

When a change comes from guest feedback, it is worth telling guests. A line in an email, a note on the menu or a reply to a review saying "you told us the wait for the bill was too long, so we have changed how we bring it" shows guests that their feedback matters.

Guests who see feedback acted on are more likely to give it again, and more likely to forgive a bad night, because they trust that the venue listens.

Staff see problems guests never mention: a section that is always short-staffed, a dish that is hard to cook at peak, a till that slows down orders. Their feedback belongs in the same weekly item.

Ask the team each week what is getting in their way. Many of the problems guests complain about start with something the team already knows. Combining guest and staff feedback gives a fuller picture than either alone.

Feedback is not only about problems. Look at what guests praise most often, and protect it: the dish everyone mentions, the server whose name keeps appearing, the warmth of the welcome. Tell the team, and make sure any change elsewhere does not damage what guests love.

A Monday item that only ever discusses complaints becomes a chore. One that also celebrates what works becomes something the team looks forward to.

Keep a short record of each change: the pattern that prompted it, the change, the owner, the date and the result. Over a year, it becomes a history of how the venue has improved, and a guide for new managers.

It also stops the same change being made twice, or a change that did not work being tried again by someone who did not know it had been tried.

Sometimes feedback conflicts: some guests say the music is too loud, others that it is too quiet; some want larger portions, others smaller prices. Conflicting feedback usually means different guests want different things, and you cannot please everyone.

Look at which guests are saying what, and which guests you most want to serve. Decide based on your venue's style and your best guests, not on whoever complained most recently.

Track how long it takes from spotting a pattern to making a change. If a theme has appeared for three months before anything changes, the process is too slow. Aim to act on a clear pattern within a month of spotting it.

Speed matters because guests who complained are deciding whether to return. A change made quickly may win them back; one made a year later reaches a different set of guests.

Some feedback never arrives as a comment. Guests who cancel, do not show up or stop coming are telling you something too. Where you know why a guest cancelled, record it with the rest of the feedback.

A pattern of cancellations for the same reason, such as difficulty parking or a booking time that was not available, belongs on the Monday agenda alongside the comments.

Real guest comments make powerful training material. Share a few each week, good and bad, with names removed: what guests said about the welcome, the wait, the food and the staff. New staff learn more from a real comment than from a rule.

Use praise especially. A comment about a server who made a guest's evening shows the whole team what good service looks like.

Every quarter, look back over the record of changes: what you changed, why and whether it worked. Some changes will have fixed their problem for good; others will have faded and need reinforcing.

The quarterly look back also shows whether the Monday item is working. If the same themes keep returning, the changes are not sticking, and the habit needs strengthening.

Fifteen minutes is enough for the Monday item if the owner prepares: the counted themes, the scores against last month, the follow-ups sent and a suggestion for the two changes. The meeting decides; it does not read every comment together. A short, prepared item survives busy weeks.

An invented brasserie collects a large amount of feedback and acts on almost none of it. The owner adds a fifteen-minute feedback item to the Monday meeting, owned by the assistant manager, who reads the week's surveys, table notes and reviews and counts the themes.

In the first month, two patterns stand out: waiting for the bill, mentioned fourteen times, and lukewarm main courses on Fridays, mentioned nine times. The brasserie makes two changes: a standard to bring the bill within two minutes of being asked, and a second runner at the pass on Fridays. Both are explained to the team.

A month later, comments about the bill have fallen to two, and comments about lukewarm mains to one. The service score rises. The brasserie chooses its next two changes, and the Monday item becomes the part of the meeting the team looks forward to.

In servearound, the team sees every guest feedback response in one place, with the number of responses, the average rating and how many guests are happy to be contacted, and each response shows its overall rating, its ratings for the food, the service and the ambience, its comment and whether the guest wants a reply. Guests who asked to be contacted can be sent a follow-up email from servearound, while those who chose privacy stay anonymous, and each follow-up is kept in the response's history.

servearound does not sort comments into themes or read online reviews, so the counting in this guide is done by the person who owns the Monday item, from the comments and from each platform. Feedback also sits on each known guest's profile, next to their visits and the team's notes. See Guest CRM.

There is too much to read, nobody owns it and there is no regular moment to act on it.

Every week, as a standing item on a regular meeting.

One manager, who reads the week's feedback before the meeting and follows through on each decision.

Give each comment a topic and count how many fall under each one, across every source.

Two a month: enough to make a difference, few enough to finish.

Write it as a service standard, explain why to the team and check after a month whether it worked.

Yes. Guests who see their feedback acted on are more likely to give it again.

Look at which guests are saying what, and decide by your venue's style and your best guests.

Acting on feedback is where most venues stop. Make it a standing fifteen-minute item on the Monday meeting, with one owner who gathers the week's feedback from every source, gives each comment a topic and counts the themes, so complaint patterns become clear.

Track feedback scores as a trend, choose two specific changes a month, turn them into service standards, tell the team why, check after a month whether they worked, follow up with guests who asked, tell guests what changed and keep a record of every change.