Hospitality Management

Restaurant Performance Reviews Without the Yearly Form

A yearly restaurant performance review asks a manager to grade twelve months of shifts from memory. Sections change nightly, people move between stations and the busiest weekend in March is long gone by December. What the manager remembers is usually last week, and the server who had a rough final month carries it onto the form. In my experience the result is a guess about a year nobody really remembers, delivered too late to change anything.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering, where feedback that arrived months late was rarely useful. Today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco, where I built Regular, the hospitality operating system, one service at a time. This is how I think about reviews: small, frequent coaching that adds up to a fair picture. You can find me on Instagram.

Why the Annual Review Fails on the Floor

The yearly form was built for office jobs with quarterly projects. A restaurant runs on hundreds of short, repeated moments: the greeting, the first drink, the read on a table that wants to linger. Those moments vanish by the end of the night unless someone writes them down.

Picture a server whose wine recommendations got noticeably better all autumn, then had one double-sat Saturday in November that went badly. If the review happens in December, that Saturday often becomes the review. The improvement is gone because nobody recorded it.

Turnover makes it worse. Many hospitality hires leave or change roles before they reach a full year, so the annual review never happens for them at all. They get no structured feedback during the months when they need it most.

Managing a post-sales team as it grew from about 20 people to more than 150 taught me that memory does not scale and written notes do. In a restaurant I replace the yearly form with five smaller pieces: a coaching note after a shift, an optional weekly check-in, a monthly scorecard, 30, 60 and 90-day reviews for new people, and a quarterly review built from everything before it.

Coaching Notes in Under a Minute

The coaching note is the foundation. It is written the same night, it takes less than a minute, and it is about one specific thing the person did. If it takes longer than that, managers skip it after the first busy week.

Here is the routine I suggest for your next service:

  1. Before service, pick two people you will watch for one thing each, such as table check-backs or how they handle the pass.
  2. During service, notice one moment for each. Do not write on the floor; remember it.
  3. At close, write one sentence per person: what they did, at which table or stage, and what to keep or change.
  4. Tell them in person before they leave, or at the next pre-shift, in under thirty seconds.
  5. Leave it there. One note per person per shift is plenty.

Technology should make step three fast on the phone and attach the note to the right shift, so it is there when the scorecard is due. It should not write the judgement for you, and it should not put a screen between you and the floor during service. For pacing notes, I use the stage-by-stage view from Server Performance, which I cover in how to coach the stages of a table.

The Weekly Check-In That Stays Optional

Coaching notes run from manager to staff. The weekly check-in runs the other way, and I keep it voluntary on purpose. A required form turns into a chore people fill in with "all good." An optional one gets used by the people who have something to say, which is the point.

Keep it to three questions:

  • What went well for you this week?
  • What got in your way?
  • Is there anything you want to get better at next week?

It should take about five minutes. The manager's job is to read it within a few days and answer anything that needs answering, even if the answer is "I can't change the Friday schedule, but here is why." A check-in that disappears into silence teaches people to stop writing them.

The monthly scorecard then pulls the month together: the coaching notes, the check-ins the person chose to send, and the service numbers that are theirs to see. I write two or three sentences on top. It is a summary of things already said, not a surprise.

30, 60 and 90 Days for New People

New hires need the most feedback and usually get the least. I use three short reviews in their first quarter, each with a different question.

Day 30: Can they run their station? Menu knowledge, steps of service, allergy handling, where things live. This review is mostly about gaps in training, and many of those gaps are the restaurant's fault, not theirs. Fix the training and write down what changed.

Day 60: Can they handle a full section on a busy night? Look at pacing, how they recover when the kitchen is slow, and how they work with the people next to them. Pull the coaching notes from the last month; the pattern is usually obvious.

Day 90: Where are they going? Decide together what the next quarter looks like: more sections, training on the bar, a mentor role for the next new hire. If it is not working, this is the honest conversation, and it should not be a shock because days 30 and 60 already said so.

After day 90, people move onto the quarterly cycle. Performance Reviews in Regular is built around exactly this sequence: shift notes, an optional weekly check-in, a monthly scorecard, 30, 60 and 90-day reviews and quarterly reviews.

Keeping Reviews Fair

Frequent coaching only works if staff trust it. In my experience three rules matter most.

First, keep reviews separate from anonymous feedback. If a server reports a problem with a manager, or answers a survey honestly, that must not show up in their scorecard. In Regular, feedback, concerns and answers to Team Pulse never feed a review, and I would hold to that rule with or without software. I wrote more about why in anonymous employee feedback in a small restaurant team.

Second, let people see their own numbers, and only their own. A server should know their pace and check averages. They should not see a colleague's, and team figures should only show for groups large enough that nobody is singled out.

Third, check every quarterly review against the notes. If a review says someone is slow but the last ten notes say otherwise, the review is wrong. Read it back before you deliver it and ask whether each sentence has a note behind it.

If you want to see how this runs inside one system, you can book a Regular demo. Either way, start with one coaching note tonight.

Frequently Asked Questions

How often should restaurants do performance reviews?

In my experience a yearly review is too slow for restaurant work. A better rhythm is a short coaching note after a shift, an optional weekly check-in, a monthly scorecard and a quarterly review built from those notes. New hires get extra reviews at 30, 60 and 90 days, because the first quarter is when feedback changes the most and when people are most likely to leave.

What should a server performance review include?

A useful server performance review covers a few concrete areas: steps of service, pacing through each stage of the table, menu and allergy knowledge, teamwork with the kitchen and neighbouring sections, and guest care. Each point should be backed by a coaching note or a number the server can see. If a sentence in the review has nothing behind it, cut it or go and observe again.

What is a 30, 60 and 90-day review for a new restaurant hire?

It is three short reviews in a new hire's first quarter. At 30 days, check whether they can run their station and fix any training gaps. At 60 days, see how they handle a full section on a busy night. At 90 days, agree on what comes next, or have the honest conversation if the role is not working out.

How long should a coaching note take to write?

Under a minute. A coaching note is one sentence about one specific moment: what the person did, at which table or stage, and what to keep or change. Write it at close the same night and tell the person in under thirty seconds. Longer notes tend to get skipped once service gets busy, and frequent short notes are worth more than occasional long ones.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.