# Measuring guest experience without surveys nobody answers

*Guides · Mays Team · October 12, 2026*

![Mays cover card: Measuring guest experience without surveys nobody answers — Seven signals you already have, one fix a week](https://mays-uploads.s3.us-east-2.amazonaws.com/site/blog__measuring-guest-experience-without-surveys__cover.00f2dec05b.png)

*This is part 6 of our 7-part series* Guest experience at a café or restaurant. *Earlier:* [*steps of service*](https://www.mays.app/blog/steps-of-service-cafe-restaurant)*,* [*the first 30 seconds*](https://www.mays.app/blog/greeting-wait-times-host-stand-restaurant)*,* [*large parties*](https://www.mays.app/blog/large-parties-groups-cafe-restaurant)*,* [*serving guests with disabilities*](https://www.mays.app/blog/serving-guests-with-disabilities-restaurant-staff) *and* [*special requests*](https://www.mays.app/blog/special-requests-dietary-needs-restaurant)*.*

You print a QR code, tape it to the counter, and wait. A handful of people scan it in a month, most of them either delighted or furious. It's hard to run a café on that.

Surveys have their place: our [feedback card and QR survey template](https://www.mays.app/blog/customer-feedback-card-qr-survey-template) shows how to make one worth filling in. But you don't have to wait for guests to tell you how they feel. Most of what you need to know is already happening in front of you, in things your team can count in seconds.

This post sets up a one-page weekly scorecard built from those signals.

## The idea: count what guests do and what the team sees

A guest's experience leaves traces. A drink that's wrong gets remade. A long wait shows up as a quote that slipped. A disappointed regular asks for a manager, or doesn't come back. Each of those can be written down by the person who saw it, without asking the guest anything.

Three rules make these signals useful:

1. **Count them the same way every week.** A remake is a remake whether it was the guest's fault or the bar's. Decide the definition once.
2. **Compare with yourself, not with someone else.** There's no reliable "good" number for remakes or comps that fits every café. Your own last four weeks are the baseline.
3. **Look for patterns, not single bad days.** One bad Saturday is a story. The same problem three Saturdays running is a fix.

## Seven signals you already have

### 1. Complaints and compliments

Write down every complaint, and every unprompted compliment, with the day, the time and what it was about: the food, the wait, the staff, the place. Our post on [handling complaints](https://www.mays.app/blog/handling-customer-complaints-restaurant) covers the log. Compliments matter as much: they tell you what to protect when you change something.

### 2. Remakes

A remade drink or plate means the first one missed. Log the reason as well as the count: wrong order taken, made wrong, too slow, guest changed their mind. Our post on [order accuracy and remakes](https://www.mays.app/blog/cafe-order-accuracy-remakes) has a log that takes seconds.

### 3. Comps, voids and refunds

Every comp is a small apology. The reason codes on your [comps and voids log](https://www.mays.app/blog/comps-voids-discounts-log-manager-approval) tell you what the apology was for.

### 4. Wait quotes vs. reality

If you quote waits, write down the quote and the actual time, as in our post on [the first 30 seconds](https://www.mays.app/blog/greeting-wait-times-host-stand-restaurant). Count how many quotes ran over. At a counter, the equivalent is ticket time if your POS or kitchen screen reports it.

### 5. Review themes, not stars

The star average moves slowly and says little. Instead, read each new review and tag what it mentions: wait, accuracy, friendliness, cleanliness, value, a named team member. A theme that keeps coming up is a signal, whether the star rating is 2 or 5. Our guide to [your first 50 Google reviews](https://www.mays.app/blog/first-50-google-reviews-replying-when-new) covers replying, and our post on a review that names an employee (coming Dec 18) covers the hardest kind.

### 6. Ten minutes on the floor

Once a week, during a busy stretch, a manager watches the floor for ten minutes with the [steps of service](https://www.mays.app/blog/steps-of-service-cafe-restaurant) page in hand and ticks which steps happened. It's the only signal on this list that catches problems guests never mention, like a greeting that's slowly disappeared.

### 7. What the team heard

At the end of a shift, ask the closing lead one question: "What did guests say today?" Write down one line. Your team hears much more than any survey: the regular who said the music was too loud, the family who couldn't find a high chair.

## The weekly scorecard

Put the seven signals on one page and fill it in once a week. Keep the last four weeks next to each other.

| Signal | How we count it | Wk 1 | Wk 2 | Wk 3 | Wk 4 |
| --- | --- | --- | --- | --- | --- |
| Complaints | entries in the complaint log |  |  |  |  |
| Compliments | unprompted, written down |  |  |  |  |
| Remakes | log entries; top reason |  |  |  |  |
| Comps and refunds | count; top reason code |  |  |  |  |
| Quotes that ran over | out of quotes written down |  |  |  |  |
| Review themes | top theme this week |  |  |  |  |
| Floor check | steps seen out of steps on the page |  |  |  |  |
| What the team heard | one line |  |  |  |  |

The numbers will be small, and that's fine. You're not looking for statistics. You're looking for the line that moves, or the reason that keeps topping the list.

Two cautions:

- **Don't turn the scorecard into a target for the team.** If people are judged on the number of remakes, remakes stop getting logged. Praise honest logging.
- **Watch for busy-week effects.** A week with twice the guests can have twice the complaints and still be a better week. If you want, divide by the number of transactions from your POS, but keep the raw count too.

## One fix a week

The scorecard is only useful if it changes something. At the weekly manager meeting (see our post on [the weekly restaurant manager meeting](https://www.mays.app/blog/weekly-restaurant-manager-meeting)):

1. **Read the scorecard top to bottom** in five minutes.
2. **Pick one problem**, the one that moved most or has repeated longest.
3. **Name one fix and one owner.** "Read-back before payment at the register, Ana trains it in the huddle this week."
4. **Check it next week** on the same line.

One fix a week adds up. Ten fixes at once usually means none of them stick.

## When you do want to ask guests

The signals above tell you what happened; they don't always tell you why. Use direct questions sparingly and well:

- **Ask at the table, not on a form.** "Was everything how you wanted it?" after the first bites, with time to listen to the answer, is the oldest guest survey there is.
- **A short card or QR survey** a few times a year, as a check on what the scorecard says. Our [feedback card template](https://www.mays.app/blog/customer-feedback-card-qr-survey-template) keeps it to five questions.
- **A mystery shop** when you want a full visit seen through a guest's eyes. See [how to mystery-shop your own café](https://www.mays.app/blog/mystery-shop-your-own-cafe).

## Where Mays fits

- **Complaints and compliments in one place:** managers write them in the **Logbook** under **Customer**, tick **Needs follow-up** where something is owed, and find flagged entries on the **Follow-ups** tab. The logbook shows one day at a time, so add up the week's **Customer** entries for the scorecard day by day. See [Manager logbook](https://www.mays.app/help/scheduling/manager-logbook).
- **Review themes:** with your Google Business Profile linked to your locations, the **Reviews** page lists reviews for every store, with filters for 3 stars or fewer and for unanswered reviews. See [Google reviews](https://www.mays.app/help/reviews-disputes/google-reviews).
- **The scorecard and the floor check as forms:** build a "Weekly guest scorecard" or "Floor check" form under **Tasks → Types** with **Number** and **Text** fields, fill it in from the phone app, and put the weeks side by side with **Export CSV** on the task data page. See [Building custom forms](https://www.mays.app/help/tasks-checklists/custom-form-task-types) and [Task Data](https://www.mays.app/help/tasks-checklists/task-data-export).
- **A reminder that it's scorecard day:** in **Automation**, a **Scheduled** rule can create a task every week, such as "Fill in the guest scorecard and pick one fix", at a time you choose. See [Automation rules](https://www.mays.app/help/ai-automation/automation-rules).

Mays doesn't survey guests or read your POS for remakes: the counting starts with the people on shift.

## Your guest experience scorecard checklist

- Seven signals, each counted the same way every week
- Your own last four weeks as the baseline, not someone else's number
- Patterns over single bad days
- Logging praised, never punished
- One problem, one fix and one owner each week, checked the next
- Direct questions at the table, with surveys and mystery shops now and then

## Measure what guests already tell you

Count the signals your team already sees, and make one thing better every week.

[**Start your free trial**](https://go.mays.app/register): 30 days, every module, no card needed. Next in this series: training the team on hospitality, with role-play scripts and a two-week plan.

## Related help articles

- Scheduling: [The manager logbook](https://www.mays.app/help/scheduling/manager-logbook) — A daily journal for each location — handoff notes, incidents and maintenance, with comments, follow-up flags, who's read what, and how your team rated their shifts.
- Reviews & disputes: [Google reviews and replies](https://www.mays.app/help/reviews-disputes/google-reviews) — The Reviews page lists your Google Maps reviews for every location, filters the low-rated and unanswered ones, and posts your reply on Google.
- Tasks & checklists: [Building custom forms (Task Types)](https://www.mays.app/help/tasks-checklists/custom-form-task-types) — Build your own task forms, like a cash count, a temperature log or a waste log, under Tasks → Types. Staff fill them in the app, and every answer lands in Task Data, ready to export.
- Tasks & checklists: [Task Data: viewing and exporting form answers](https://www.mays.app/help/tasks-checklists/task-data-export) — Tasks → Data lists every answer submitted on a custom form, like a cash count or temperature log, one row per submission, and downloads them as a CSV file.
- AI & automation: [Automation rules](https://www.mays.app/help/ai-automation/automation-rules) — Automation rules do routine follow-ups for you. When something happens, like a task rejected, a deadline near or a fridge too warm, Mays checks your conditions and runs your actions.

Canonical: https://www.mays.app/blog/measuring-guest-experience-without-surveys