Complaint patterns: the same thing four times

On Monday, a guest says their pasta was lukewarm. On Wednesday, a different manager hears that a risotto arrived cold. On Friday, an email mentions a "tepid" main course. On Saturday, a review says the food was "not hot". Each complaint was handled politely and put right on the spot. Nobody noticed that it was the same complaint four times. Complaint patterns like this one are invisible when every complaint is treated as a one-off.

Handling complaints one by one is necessary: each guest deserves a quick, sincere response. But it is not enough. A venue that only handles complaints will keep handling the same ones, week after week, because the cause behind them never changes. A venue that counts them by cause can see what keeps going wrong, fix it once and stop the complaints before they happen.

This guide covers why patterns get missed, how to record and count complaints by cause, the two causes that repeat in almost every venue, how to read feedback for patterns and how to turn a pattern into a fix that lasts. Every venue and figure in it is an example.

A single complaint tells you that one guest had a problem. A pattern tells you that the venue has one. The difference matters, because the response is different. A single complaint calls for an apology and a fix at the table. A pattern calls for a change in how the venue works.

Most venues are good at the first and weak at the second. Managers handle complaints well, but each complaint lives only in the memory of whoever heard it. Without a record, nobody can see that the same thing has happened four times, and the fifth guest has the same experience as the first.

Patterns hide for simple reasons. Complaints arrive through different channels: at the table, by email, by phone, in online reviews. Different managers handle them on different shifts. Memory fades within days. And a complaint that was resolved on the spot feels finished, so nobody thinks to write it down.

Busy venues are especially prone to this. On a full night, a manager handles three complaints and forgets two by the morning. Spread across a week and several managers, a dozen complaints about the same cause can pass without anyone connecting them.

The fix is a simple log. For every complaint, record the date, the time, the table, what the guest said, what was done about it and who handled it. Add a cause, from a short list, so complaints can be counted later. It takes a minute, and it can be done at the end of the shift if not on the spot.

Keep the log in one place that every manager uses: a shared sheet, a notebook at the host stand, a note on the guest's profile. The format matters less than the habit. A log that only some managers fill in will show patterns only on their shifts.

The most useful log records causes, not just symptoms. "Cold food" is a symptom. The cause might be plates waiting at the pass for a server, cold plates, a long walk to the terrace or a kitchen firing dishes too early. Each cause needs a different fix.

You will not always know the cause when the complaint arrives. That is fine: record the symptom, and look into the cause when the same symptom appears more than once. The second or third time a symptom appears is the moment to ask why.

Keep the list of causes short, so it is quick to use. Something like: waiting for a table, waiting for food, waiting for the bill, food temperature, food cooking or seasoning, portion size, wrong or missing dish, service manner, cleanliness, booking mistakes, billing mistakes and the room itself, such as noise or temperature.

Ten or twelve causes are enough. A longer list slows people down and scatters complaints across too many headings to see a pattern. If a cause keeps being written as "other", add it to the list. If a heading is never used, remove it.

Once a week, count the complaints by cause. Even a rough tally is revealing. A week with fourteen complaints might show six about waiting for food, three about temperature and one each about five other things. The six are the pattern; the ones are noise.

Compare each week with the last few. A cause that rises from one or two a week to five or six is a new problem worth investigating. A cause that falls after a change shows that the fix worked. The tally turns complaints into information.

In most venues, two causes come up again and again: waiting, and food that does not arrive as the guest expected, most often not hot enough. They are not the only complaints, but they are the ones that appear in almost every log, in every kind of restaurant.

Both are system problems rather than people problems. Waiting comes from how the room is paced, how the kitchen is loaded and how the floor and pass communicate. Temperature comes from how plates travel from the pass to the table. Neither is fixed by telling staff to try harder. Both are fixed by changing how the service runs.

Waiting complaints take many forms: waiting for a table, for menus, for drinks, for food, for the bill. Count them separately, because each has a different cause. A rise in complaints about waiting for the bill points to a floor problem. A rise in complaints about waiting for food points to the kitchen or the pacing of the room.

The most common fix is earlier communication. Guests who are told about a delay before they notice it complain far less. Our guide to a late main course and a table that has noticed covers the moment a table starts to wait.

The second repeating cause is food that does not match the guest's expectation: not hot enough, overcooked, underseasoned, smaller than expected or different from the description on the menu. Temperature is the most frequent, because it depends on the journey from the pass to the table, not just on the cooking.

Look at that journey. How long do plates wait at the pass before a server collects them? Are plates warmed? How far is the furthest table? A kitchen that cooks perfectly can still produce complaints about cold food if plates wait two minutes for a runner.

In most venues, a few causes account for most complaints. It is an example of the Pareto principle, the observation that a large share of effects often comes from a small share of causes. The exact proportions vary, but the shape is almost always the same.

That is good news. You do not need to fix everything to cut complaints sharply. Fix the top two or three causes, and the total falls a long way. Then look at the new top two or three, and repeat.

Complaints are only part of what guests tell you. Feedback also includes praise, suggestions and comments that are neither. Treating complaints and feedback together gives a fuller picture: a dish that draws both complaints and praise may be inconsistent, while one that draws only praise is worth protecting.

Use the same list of causes for complaints in feedback forms, emails and reviews as for complaints at the table. A pattern is easier to see when every source is counted the same way. A complaint about slow service in a review and one made at the table are the same signal.

Average feedback scores are useful, but they move slowly and hide detail. A venue whose average rating stays steady at four out of five may still have a growing problem with one dish or one night, because a few unhappy guests are balanced by many happy ones.

Read the comments behind the scores. A score tells you how guests felt on average; the comments tell you why. A steady score with a rising number of comments about waiting is a pattern the score alone would never show.

Once a week, read every comment guests have left, and add each complaint to the tally under its cause. It takes a little time, but it is the most reliable way to see what guests are really saying.

Look for specific words that recur: "cold", "slow", "waited", "rude", "noisy", "small". When the same word appears in several comments from different guests in the same week, you have found a pattern. Our guide to guest feedback you can actually act on covers how to ask for feedback that is useful.

Most unhappy guests never complain. They eat, pay, leave and do not come back. So each complaint you hear stands for others you do not. A cause that produces three complaints a week may be affecting many more guests who said nothing.

That makes every complaint more valuable than it looks. It is a free report on something other guests also experienced. And it means that a falling number of complaints is good news only if it comes from fixing causes, not from guests giving up on telling you.

Online reviews are complaints made in public, and they belong in the tally too. Read them each week, add any complaints to the log under their causes and respond to them in the usual way. A review that mentions cold food is the same signal as a guest who mentioned it at the table.

Reviews often arrive days after the visit, from guests who said nothing at the time. They can reveal patterns that never reached a manager in the room. Our guide to responding to reviews in four sentences covers how to reply.

Acting on feedback works best as a fixed weekly habit rather than a reaction to a bad review. A short item on the weekly meeting's agenda, looking at the tally, the top causes and what is being done about them, keeps patterns visible and fixes moving.

Keep it short and practical: what were the top causes this week, did last week's fix work and what will we try next? Our guide to acting on feedback: the Monday meeting item covers how to run it in a few minutes.

When a pattern appears, find its root cause before changing anything. Ask why the food arrived cold, then why the plates waited at the pass, then why no runner was free. The third or fourth "why" usually reaches something you can change, such as how runners are assigned at the peak.

Then make one change, give it one owner and set a date to check whether it worked. Several changes at once make it impossible to tell which one helped. A fix with no owner tends to be forgotten within a week.

A fix lasts when it becomes a standard. If the cause of cold food was plates waiting at the pass, the standard might be "plates leave the pass within one minute, and any server passing collects them." Written as an action rather than a value, it is easy to train and easy to check.

Add the new standard to training, the pre-shift briefing and the way managers watch the floor. Our guide to service standards written as actions, not values covers how to write standards that change behaviour.

After making a change, watch the tally for that cause. If complaints about it fall over the following weeks, the fix worked; keep it, and turn your attention to the next cause. If they do not, the root cause was something else, and it is time to dig deeper.

Give each fix long enough to show its effect, usually a few weeks, because complaints vary from week to week. A single quiet week proves little. A cause that has fallen for a month, while others stayed the same, is a fix that worked.

Complaints often cluster in ways that point to their cause. They may come mainly from one night, one part of the room, one station or one shift. Complaints about cold food that come mostly from the terrace suggest a distance problem. Complaints about waiting that come mostly on one night suggest a staffing or booking problem.

Note the night, the time and the table in every log entry, so these clusters can be seen. A pattern that looked like a general problem often turns out to be a specific one, which is much easier to fix.

Share the patterns with the team, without blame. A pattern is almost always about how the service runs, not about one person. "We have had six complaints about cold food this month, mostly from the terrace" invites the team to help find a fix. "Someone keeps serving cold food" invites defensiveness.

Teams often know the cause already. A server may point out that the terrace is the furthest walk and runners are scarce at eight o'clock. Involving them in the fix makes it more likely to work and more likely to last.

Patterns appear in praise too. If guests keep mentioning a particular dish, a particular server's warmth or the speed of the bill, that is something the venue does well, repeatedly. It deserves as much attention as the complaints.

Protect what guests praise. Do not change a much-loved dish without good reason, recognise the staff guests mention by name and make sure what works on one shift becomes the standard on every shift. Patterns in praise show what to keep; patterns in complaints show what to change.

An invented bistro starts logging every complaint, with a cause from a list of ten. After a month, the tally shows that complaints about food temperature are the largest group, and that most come from tables on the terrace. Looking into it, the manager finds that terrace plates often wait at the pass while the one runner is busy indoors.

The bistro makes one change: at the peak, a second server runs terrace plates, and plates leave the pass within a minute. The manager owns the change and checks the tally each week. Over the next month, complaints about temperature fall to almost none, and the team turns to the next cause on the list, waiting for the bill.

servearound does not group complaints by cause: the feedback questions are fixed, with no themes or tags, and there is no feedback panel in Reports, so the tally in this guide is one you keep yourself. What it collects is the raw material. After a completed visit, the guest receives an email with a link to the feedback form, and the table's QR menu offers Give feedback once an order is in. Guest insights lists each response with its overall rating and the guest's comment, with the number of responses, the average rating and how many guests allow a follow-up, for each venue and for the whole network.

Where a guest agreed, staff can send a follow-up email from servearound, with an anonymous guest's address kept hidden, or reveal the number of a guest who asked for a call back, and follow-ups are kept as history. On the till, comps, voids and remakes can carry a reason, so the gestures behind complaints can be counted too: payment analytics show voids and comps by member of staff, and kitchen analytics show the remake rate. See Analytics and the guests module.

The same cause behind several complaints, often from different guests on different days.

Complaints arrive through different channels, are handled by different managers and are rarely written down.

The date, time, table, what was said, what was done, who handled it and a cause from a short list.

In most venues, waiting and food that does not arrive as expected, most often not hot enough.

Weekly, with the tally on the agenda of a short weekly meeting.

No. Averages move slowly and hide detail. Read the comments behind them.

Find the root cause, make one change, give it an owner and check the tally a few weeks later.

Yes. They are complaints made in public, and they often come from guests who said nothing at the time.

Complaint patterns are invisible when every complaint is handled as a one-off. Keep a simple log of every complaint, with its cause from a short list, from every channel: the table, email, feedback forms and reviews. Count the log by cause each week, and read the comments behind your feedback scores rather than relying on the average.

Expect the same two causes to lead in most venues: waiting, and food that does not arrive as expected. Find the root cause of the top patterns, make one change at a time, give it an owner, write it into your service standards and check the tally a few weeks later. Share patterns with the team without blame, and protect the things guests keep praising.