Many restaurant managers I meet run their week on adrenaline. They fix the walk-in, cover a server who called out, comp a table that waited too long, and go home feeling useful and exhausted. The problem is that next week looks the same. In my experience good hospitality management is not a series of rescues. It is a routine: a short list of things you review, at fixed times, with one change coming out of it each week.
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 weekly cadence is how you keep customers. Today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco, and I built Regular inside it, one service at a time. This is the manager's week I think works, from Monday morning to the last note after close.
Management Is a Routine, Not Heroics
In software I helped scale a post-sales organisation from about 20 people at $1M ARR to more than 150 collaborators at $20M+ ARR. What kept it steady was not talent or late nights. It was cadence: the same weekly review, the same questions, the same place to write down what we learned. When something went wrong, we could see it early because we looked at the same things in the same order.
Restaurants reward heroics, and that is the trap. The manager who saves a Friday gets the credit, while the manager who quietly prevented the problem on Tuesday gets none. Heroics also hide patterns. If you personally fix the slow ticket times every Saturday, nobody learns why they are slow.
So I break the week into five fixed habits:
- A look back on Monday
- A pre-shift before each service
- A deliberate watch during service
- A ten-minute close after service
- One change chosen for the week
None of these takes long. Together they replace most of the firefighting with something your team can predict and follow.
Monday: Look Back at Last Week
I keep Monday's review to about an hour and ask the same three questions. Where did time go? Where did guests wait? What did we promise and miss?
For time, I look at table turns against our targets by party size. A two-top that sits for two and a half hours on a Friday is worth a conversation; so is a six-top that was rushed. In Regular, the Reports app shows table turns against party-size targets, which saves me building that comparison by hand. For waiting, I look at the gap between reservation time and seating, and at any comps or notes about slow courses. For missed promises, I read the closing notes from each night: the allergy that reached the kitchen late, the birthday nobody acknowledged, the regular who was seated by the kitchen door.
Then I write one page. Not a dashboard, a page: what went well, what went wrong, and the two or three patterns that showed up more than once. That page is the agenda for the weekly meeting with the floor leads, and it is where the week's one change comes from. If your systems are separate, you can still do this with exports. You can see every app in Regular if you want to see how the pieces connect.
Before Every Service: The Pre-Shift
A pre-shift should take about ten minutes and follow the same order each time, so the team knows what is coming and the manager cannot skip the hard parts. Here is the routine I use:
- Headcount and sections. Confirm who is in, who is missing, and who covers which section.
- Tonight's book. Walk through the reservations that need care: returning guests, VIPs, allergies, celebrations and large parties, with table numbers.
- One menu note. An 86, a new dish or a wine to recommend. One, not five.
- This week's standard. Repeat the single change we are working on and what good looks like tonight.
- One question. Ask the team what they need from you to have a good service, then listen.
Step two is where most pre-shifts fall apart, because the manager is reading the book cold. I want that list ready before the team arrives. Regular's Today's Guests app lists each reservation tonight with visit history, VIPs, allergies and seating notes, so the manager spends the time talking about guests rather than searching for them. That second-visit guest matters most, which I wrote about in how to turn first-time guests into restaurant regulars.
During Service: What a Manager Watches
During service the manager's job is to see the room. I stand where I can see the door and the pass at once, and I watch four things in rotation.
First, the door: how long a guest stands before someone greets them. Second, the stall points: the gap between seated and first order, and between the last plate and the check. Those are where tables most often feel forgotten. Third, the floor: a scan for empty water glasses, a guest looking around for help, a table that has gone quiet in a way that suggests something is wrong. Fourth, the team: who is in the weeds and needs a hand before they ask.
This is the moment where technology should step back. It should not be a screen the manager stares at while the room drifts. A laptop in the office is fine; a tablet carried through service usually means eyes down at the wrong time. What technology should do here is surface the few things a manager needs without looking: the allergy on table twelve, the anniversary on table four, the server who has not clocked in. Picture a manager who knows all three before the doors open. Their eyes stay on guests, which is the point.
After Service: The Ten-Minute Close
The close is the habit managers drop first, because they are tired and the room is done. I keep it to ten minutes so it survives a hard night.
I write three notes in the same place each time. What went well, including names, because praise that waits until Monday loses most of its value. What went wrong, described as a fact rather than a judgment: "table nine waited 25 minutes for mains" is useful, "kitchen was slow" is not. And which guests need follow-up: the table that had a bad experience, the guest who mentioned an upcoming birthday, the regular who brought a new friend.
The follow-up list matters most. Picture a couple whose mains came out cold and who left politely without complaining. A short, personal note the next day often does more than a comp ever would, but only if someone wrote their name down that night.
These notes are also the raw material for Monday. When they live in the same place as reservations and staffing, the review almost writes itself. That is the argument I make in what a hospitality operating system does for a restaurant: the data a restaurant already has should work together.
One Change a Week
The output of the whole week is one change. Not a new training manual, not a list of ten fixes. One standard the team works on for seven days.
It comes from Monday's page. If the pattern was slow greetings, the change might be: every guest is acknowledged within a minute of walking in, even if it is just eye contact and "I'll be right with you." If the pattern was long gaps before the check, the change might be: the server offers the check within a few minutes of the last plate clearing.
Then the loop closes on itself. Announce it at Monday's meeting. Repeat it at each pre-shift. Watch for it during service. Note it at the close. Review it the following Monday and decide whether it becomes a standard or gets dropped. In my experience restaurant standards stick when they are introduced one at a time and checked daily, and fade when they arrive as a binder.
If you want your reservations, point of sale and schedule feeding this routine in one place, you can book a Regular demo. And if you run your own version of this week, I'd like to hear how it goes. You can find me on Instagram.
Frequently Asked Questions
What are the main duties of a restaurant manager each week?
A restaurant manager's core weekly duties are reviewing last week's service, running a short pre-shift before each service, watching the floor during service, closing out each night with notes, and choosing one improvement for the team. Around that sit scheduling, ordering, hiring and handling guest follow-up. A fixed routine keeps those duties from turning into constant firefighting.
What should be covered in a restaurant pre-shift meeting?
A good pre-shift takes about ten minutes and covers staffing and sections, the reservations that need special care such as allergies, VIPs, celebrations and large parties, one menu note, the standard the team is working on this week, and a question for the team. Keeping the same order each time helps staff know what to expect and stops important items being skipped.
How long should a restaurant weekly meeting be?
For most independent restaurants, a weekly meeting with floor leads works well at 30 to 60 minutes. Base it on a one-page review of last week: what went well, what went wrong, and the patterns that repeated. End the meeting with one agreed change for the coming week rather than a long list of fixes nobody will remember.
How do you get restaurant staff to follow new standards?
Introduce one standard at a time and check it daily. Explain it at the weekly meeting, repeat it at each pre-shift, watch for it during service, note how it went at close, and review it the following week. Standards tend to stick when they are small, specific and visible, and tend to fade when several arrive at once.