The restaurant manager's week, hour by hour

A restaurant manager's week rarely goes the way it was planned. It starts with a list: the rota to write, the suppliers to call, the new starter to train, the numbers to read, the broken fridge to chase. By Wednesday, the list has been overtaken by a server off sick, a delivery that did not arrive, a complaint that needs a call, and a Friday that suddenly looks much busier than expected. By Sunday, most of the week has gone on service and firefighting, and the work that would have made next week easier has been pushed back again.

That is normal, and some of it cannot be avoided. Service comes first, and a good manager spends most of the week on the floor. But the managers whose venues improve year after year do one thing differently. They protect a small number of hours each week for the work that compounds: the planning, the review and the coaching that make every following week a little easier. Three hours, protected, are worth more than twenty hours of good intentions.

This guide looks at where a restaurant manager's week actually goes, lays it out hour by hour, and identifies the three hours worth protecting. It covers the manager routines that hold the week together, the weekly review, the staff rota, the restaurant KPIs worth reading, and how to reclaim time from firefighting.

Here is an illustrative week for a general manager of a 90-seat restaurant, around 50 hours. The figures are examples.

Most managers who track their own week for a fortnight find something similar: service and firefighting take most of it, and planning and people get what is left.

Service should take most of a manager's week. Guests notice when the manager is on the floor: problems are spotted early, the team feels supported, regulars are greeted, and standards hold. A manager who spends the evening in the office misses all of that.

The aim is not to spend less time on the floor, but to make the time off the floor count.

Firefighting is the work nobody planned: covering an absent server, chasing a missing delivery, calling a contractor about a broken dishwasher, sorting out a double booking. Some of it is unavoidable. Much of it comes from problems that were never fixed at the root: a rota published too late, a supplier who is often late, equipment never serviced.

Every hour of firefighting is an hour the manager did not spend preventing the next fire.

Some work pays back again and again. A rota built properly from the forecast saves overtime every week. A new starter trained well becomes a strong team member for years. A recurring problem fixed at the root stops costing time every week. A weekly review that catches a rising cost saves money for months.

This is the work that compounds, and it is exactly the work that gets pushed aside when the week fills up.

Three hours a week, protected, cover the work that compounds:

Put each in the diary at a fixed time, treat it like a service, and protect it from everything except a genuine emergency.

The planning hour is for next week: the covers forecast for each service, built from the bookings and the same week last year; the staff rota built from the forecast; the ordering for the main deliveries; and anything unusual, such as events, holidays or large parties.

Hold it early in the week, after the weekly review, so the rota can be published by midweek. A rota published early prevents more firefighting than almost anything else a manager does.

The staff rota should follow the trade: more people at the peaks, fewer at the quiet edges, with the right mix of experience on each shift. It is the restaurant's version of workforce management: matching the people on duty to the work expected. Build it from the forecast, check it against the labour budget, share the difficult shifts fairly, and publish it at least a week ahead.

Our guides to staff scheduling against the trading curve and scheduling from forecast, not from memory cover the method.

The review hour is for the weekly review: a short meeting with the head chef and the other managers to read last week's numbers, discuss what moved and why, hear about guests and the team, look at next week, and agree a few actions with owners and dates. With preparation, the meeting itself takes thirty minutes; the rest of the hour is for preparing the numbers and following up.

Our guide to a weekly review that takes thirty minutes sets out the agenda.

The review hour is where the restaurant KPIs are read: covers against last year, spend per head by service, food cost and labour cost as a share of sales, prime cost, no-show rate and table turns on the busy services. Each should have an owner, a target range, and an action when it moves.

Our guide to restaurant KPIs worth tracking every week sets out the list.

The people hour is for the team: training a new starter, coaching a server who is struggling, a stay conversation with a strong team member, preparing a supervisor for promotion, or planning the month's short training sessions. It is the hour most often sacrificed, and the one whose absence costs most over time.

Teams that feel invested in stay longer and perform better. Our guide to staff retention covers why.

Here is one way to lay out a week that protects the three hours. The times are illustrative, for a venue open for lunch and dinner from Tuesday to Sunday.

Adjust it to your own trading pattern, days off and team.

Beyond the three protected hours, a handful of manager routines hold every day together:

Each takes minutes, and together they prevent many of the fires that would otherwise fill the week.

Before service, walk the venue: the dining room, the toilets, the kitchen, the bar, the store rooms. Check the bookings for the service, the large tables and the allergies. Check who is on and who is missing. Ten minutes at the start of a shift often saves an hour of firefighting later.

The pre-service briefing aligns the floor and the kitchen in five to ten minutes: the expected covers, the large parties, the regulars, the allergies booked in advance, the specials, what is off, and one thing to focus on tonight. A briefing that runs every service makes every service calmer.

During service, the manager's job is to see the whole room: tables waiting too long, a section under pressure, a guest who looks unhappy, a kitchen falling behind. Visit every table, help where the pressure is, and deal with problems before they become complaints.

Keep the office door shut during service unless there is no alternative.

At the close, cash up, sign the closing checklist, check the bookings for tomorrow, and spend a minute with the closing team: what went well, what went wrong, what to fix tomorrow. Write a short note for the opening manager if it is someone else.

A good close makes the next morning easier.

To reclaim time from firefighting, keep a simple log for two weeks: every unplanned problem, how long it took, and its cause. Most managers find that a few causes produce most of the fires: late rotas, unreliable suppliers, equipment that breaks, unclear procedures. Fix the biggest cause first, in the planning or people hour.

Each fire prevented is an hour returned to the week.

Before changing anything, track your own week for a fortnight. Note, roughly, how each hour was spent: service, opening and closing, firefighting, admin, rota, people, numbers. It feels tedious, but the result is almost always surprising, and it shows exactly where the protected hours can come from.

Repeat it once a quarter. Weeks drift back towards firefighting unless someone is watching.

Messages can swallow a manager's week: supplier emails, booking enquiries, team messages about shifts, guests asking about allergies. Answering each one the moment it arrives breaks every other task into pieces. Set two or three times a day to deal with messages, and agree with the team which kinds of message need an immediate reply.

Move routine questions, such as shift swaps, to one agreed place, so they do not arrive in five different apps.

Suppliers take more time than most managers expect: placing orders, checking deliveries, chasing missing items, querying invoices. Fixed ordering days, standard order lists and a clear person responsible for receiving each delivery cut that time sharply. Where a supplier is regularly late or short, raise it, and change supplier if it does not improve.

The best supplier is often the one who causes the fewest phone calls.

Between services, guests still need the manager: a complaint that deserves a call back, a large party asking about the menu, a review that needs a reply. Set aside a short slot each day for these, so they are handled promptly rather than in the middle of the next service.

A complaint answered the same day often turns an unhappy guest into a loyal one. Our guide to guest complaints: the first thing to say covers how.

Many managers dread Monday mornings, because the weekend's problems arrive all at once. A short routine helps: read the weekend's numbers, check the week's bookings, look at the rota for gaps, and list the three things that must happen this week. Then decide which can wait.

A calm hour on Monday often sets the tone for the whole week, and it gives the planning and review hours on Tuesday a clear starting point.

A manager cannot do everything, and should not try. Delegate routine jobs to supervisors and senior team members: the cash-up on some nights, the ordering for one supplier, the opening checklist, the training of a new server. Delegation develops the team and frees the manager for the work only they can do.

Delegate clearly: what, by when, and what good looks like. Then check, and thank.

A quick daily look at the numbers takes a few minutes: yesterday's sales, covers and spend per head against the same day last week, the bookings for the days ahead, and any no-shows. Do it at the same time each day, on a phone if needed. Our guide to a restaurant dashboard you look at daily covers what to include.

The daily glance catches surprises; the weekly review handles trends.

Clear communication saves hours. Publish the rota on time, post changes in one agreed place, and keep a short weekly note for the team with anything they need to know. Answer questions once, in writing, rather than repeating them on every shift.

A team that knows what is happening asks fewer questions in the middle of service.

Agree with the owner how and when you report: a short weekly note with the key numbers, the actions agreed and any problems, and a monthly conversation about the bigger picture. A manager who reports clearly and early earns trust and freedom.

A tired manager makes worse decisions and has less patience with guests and the team. Protect days off as firmly as the three hours, plan holidays in advance, and make sure someone can cover. Managers who never rest burn out, and their venues suffer when they leave.

In a small venue, the manager may also be the owner, the host or the chef, and the three hours may shrink to two or one. Protect them anyway, in a shorter form: a thirty-minute review, a planning slot for the rota, and a weekly conversation with each team member, even briefly.

In a group, the venue manager's week includes the group's rhythm: a weekly meeting with the operations lead, shared reports, and group standards. Fit the three protected hours around those, and use the group meeting to raise problems that need help from outside the venue.

Here is an illustrative manager who reclaimed time over a quarter. The details are examples.

In servearound, the dashboard gives the daily glance: revenue, covers, spend per cover and no-shows against the previous period, with a "Right now" view of covers and bookings today, guests seated and waiting, tables in service and open orders. Reservation analytics and the reservations calendar show the week ahead for the planning hour, and analytics gives the weekly numbers for the review, on the venue's local clock.

Each venue has its own team chat for the messages that would otherwise fill the manager's phone. servearound does not write rotas. See Analytics, and if you would like to work with us, our careers page lists our open roles.

Mostly on service, opening and closing, firefighting and admin, with planning, review and people getting what is left.

The planning hour for the forecast and rota, the review hour for the weekly review, and the people hour for training and coaching.

At least a week ahead, ideally by midweek for the following week.

About thirty minutes for the meeting, with preparation and follow-up filling the rest of the hour.

Log every unplanned problem for two weeks, find the few causes that produce most of them, and fix the biggest first.

Yes, for most of it. The floor is where problems are spotted early and the team is supported.

Routine jobs such as some cash-ups, some ordering and the training of new starters, with clear expectations.

A quick daily glance, and a fuller weekly review.

Make it shorter rather than skipping it: twenty minutes with one team member each week is far better than nothing, and the habit matters more than the length. Over a few months, everyone in the team gets a conversation, and the manager learns things no report would show.

A restaurant manager's week is mostly service and firefighting, and that is partly as it should be. But the work that compounds, planning, review and coaching, needs protected time. Put three hours in the diary every week: a planning hour for the forecast and the staff rota, a review hour for the weekly review and the restaurant KPIs, and a people hour for the team.

Hold the days together with simple manager routines: the opening walk-round, the pre-service briefing, table visits and a proper close. Log and fix the causes of firefighting, delegate routine jobs, glance at the numbers daily, communicate clearly with the team and the owner, and protect your days off.