Restaurant operations: the week as a system

Restaurant operations are everything a venue does to be ready for guests and to look after them: buying, preparing, staffing, cleaning, serving, counting and reviewing. In a well-run restaurant, most of this happens without drama, because the same jobs are done at the same time by the same people every week. In a struggling one, the same jobs are done when someone remembers, by whoever is around, and the week is a series of emergencies.

The difference is rarely talent. It is whether the venue treats its week as a system: a set of recurring jobs, each with an owner and a day, that together keep the business running. When the system works, the managers have time to look after guests and develop the team, because the routine work takes care of itself. When it does not, the managers spend their time firefighting.

This guide sets out the eight recurring jobs that make a venue run, who owns each one, and the day of the week each belongs on. It covers the daily checklists and manager routines that hold the system together, how standard operating procedures fit in, and how to build the system in a venue that does not have one.

A restaurant week has a natural rhythm. Trade builds from a quiet start to a busy weekend; deliveries arrive on set days; the rota is written for the week ahead; the numbers are counted when the week ends. The jobs that keep the venue running fit into that rhythm, and when they are placed deliberately, each one supports the next.

The forecast feeds the rota and the orders. The orders feed the prep plan. The prep plan feeds service. Service produces the numbers. The numbers feed the weekly review, which shapes next week's forecast. Treat these as separate tasks and the links break; treat them as one system and they reinforce each other.

Almost every venue runs on eight recurring jobs:

Some are weekly, some daily, some both. Each needs an owner, a time and a standard for what done looks like. The sections that follow take each in turn, and then lay them out across the week.

The weekly review is a short meeting, early in the week, where the people who run the venue look back at the week just ended and ahead at the next. It covers a few key numbers, guest feedback, the team, next week's bookings and events, and a short list of actions with owners and dates.

The owner or general manager runs it. It belongs on Monday or Tuesday morning, when the previous week's numbers are ready and the next week can still be shaped. Our guide to a weekly review that takes thirty minutes sets out the agenda.

The forecast estimates covers for each service next week, from bookings already made, recent trends and the same week last year. The rota sets who works when, matched to the forecast. Together, they decide whether the venue is staffed for the trade it will have.

The general manager or front of house manager owns the forecast and the floor rota; the head chef owns the kitchen rota. Draft the forecast after the weekly review, and publish the rota by midweek, so the team can plan their lives. Our guide to scheduling from forecast, not from memory covers how.

Ordering buys what the kitchen and bar need for the coming days; receiving checks that what arrives matches what was ordered, in quantity, quality and temperature; stock counts show what is on the shelves. Together, they keep the venue supplied without tying up cash or wasting food.

The head chef owns food ordering and the bar manager owns drinks. Ordering follows the suppliers' delivery days and the forecast. A quick count of the most valuable items each week, and a full stocktake each month, keep food cost visible. Our guide to running a restaurant stock count properly covers the counting.

Prep planning decides what the kitchen prepares each day, and how much, from the forecast and the stock on hand. A good prep list stops the kitchen from over-preparing on quiet days and running out on busy ones.

The head chef or sous chef owns it. Write the prep list each day for the next day's services, adjusted for bookings and events, and review it at the end of the day against what was used and what was wasted. Our guide to the prep list that ends the morning guesswork covers how to build one.

Opening and closing checks make sure the venue is ready for service and secure at the end of the day: equipment on and working, fridges at temperature, stations stocked, the dining room set, the toilets clean, the doors and alarms secured at night. Daily checklists make these checks consistent, whoever is on duty.

The duty manager owns the front of house checks and the senior chef on duty owns the kitchen checks. They happen every day, at opening and at close. A checklist that is signed and kept also forms part of the venue's food safety records.

The pre-service briefing is a few minutes before each service when the team hears what they need to know: covers expected, large tables, special guests, allergies booked in advance, the specials, dishes that are off, and anything unusual about the night. It aligns the floor and the kitchen before the first guest arrives.

The duty manager runs it, with the chef or sous chef covering the food. It belongs ten to fifteen minutes before each service. Keep it short and practical; a briefing that runs long eats into setting up.

At the end of each day, the cash-up reconciles the money taken with the sales recorded: cash counted, card totals checked, any differences explained. The day's numbers, such as sales, covers and anything unusual, are recorded for the weekly review.

The duty manager owns it, every night. A cash-up done properly every day catches problems while they are small and the people involved can still remember what happened. A cash-up left for the morning, or done loosely, lets small differences grow.

Cleaning, maintenance and safety checks keep the venue safe and in working order: the daily clean of each station, the weekly deep clean of one area, the regular checks of equipment, fire safety, first aid and pest control, and the repairs that keep everything running.

The head chef owns kitchen cleaning; the general manager owns the building, equipment and safety checks. Spread deep cleaning across the week, one area each day, so it never becomes a single overwhelming task. Keep a list of maintenance jobs and check it weekly.

Here is one way to lay the eight jobs across a week, for a venue that trades every day and is quietest early in the week:

Adjust it to your own trading pattern and delivery days. A venue closed on Mondays, for example, moves the weekly review to Tuesday.

Daily checklists are the simplest tool in restaurant operations and one of the most powerful. A list of the checks to make at opening and close, the temperatures to record, the stations to stock and the jobs to finish turns good practice into a habit, and it means a new manager on their first day does the same things as one who has been there for years.

Keep each list short: the checks that matter, not every possible task. Print it or keep it on a tablet, sign it when it is done, and keep the signed lists as a record. Review the lists every few months and remove anything that no longer matters.

Beyond the eight jobs, each manager needs their own routines: the walk-round at the start of the shift, the check of bookings and the floor plan, the conversation with the chef before service, the table visits during service, the review of the night with the closing team. These manager routines are what turn the system into a well-run evening.

Write them down for each role: the duty manager, the head chef, the bar manager. They become the basis for training new managers and for covering when someone is away. Our guide to the restaurant manager's week, hour by hour covers a full week in detail.

Standard operating procedures, or SOPs, are the written descriptions of how a job is done: how to receive a delivery, how to cash up, how to handle an allergy order, how to close the kitchen. They make sure the job is done the same way whoever is doing it, and they make training faster.

Write SOPs for the jobs where consistency matters most: food safety, allergens, cash handling, opening and closing. Keep each one short, with steps in order and a photo where it helps. The general idea of a standard operating procedure is simple: the agreed way of doing a recurring task, written down.

Every job needs one owner: the person who makes sure it happens, even if others help. Owners should be named, not described by role alone, and every owner needs a cover for when they are away. A job owned by "the managers" is owned by nobody.

A simple table on the office wall, listing each job, its owner, its cover and its day, is often enough. When someone joins or leaves, update it the same week.

Jobs will be missed sometimes: a manager is ill, a delivery is late, a busy service runs over. The system should notice and recover. A checklist that is not signed, a rota not published by Wednesday, a cash-up not done: each should be visible to someone who can act.

When the same job is missed repeatedly, ask why. The owner may have too much to do, the timing may be wrong, or the job may no longer be needed. Fix the cause rather than adding another reminder.

The power of the system comes from the connections. The weekly review produces actions and a view of next week; the forecast turns that view into numbers; the rota and the orders follow the forecast; the prep plan follows the orders and the bookings; service runs on the prep; the cash-up and the numbers record what happened; and the weekly review reads them.

When one link is weak, the others suffer. A poor forecast leads to a poor rota and poor orders; a skipped cash-up leads to unreliable numbers at the review. Strengthen the weakest link first.

The eight jobs prepare the venue for service, but service has its own operations: seating guests, taking orders, sending them to the kitchen, cooking and plating, delivering and clearing, taking payment, turning tables. Here, the system is the flow of orders from the table to the kitchen and back.

A clear flow, with orders reaching the right station in the right sequence and the pass seeing what is waiting, keeps service calm. Our guide to order management from table to pass covers the flow in detail.

The kitchen has its own rhythm inside the venue's: deliveries on set days, prep building towards the weekend, a deep clean of one section each day, the weekly count of key stock, and menu or special changes on a fixed day. The head chef owns that rhythm and agrees it with the general manager.

A kitchen that knows its week can plan around it. A delivery that always arrives on Tuesday morning shapes the Tuesday prep; a menu change that always happens on Wednesday gives time to train the team before the weekend.

Front of house has its own rhythm too: checking bookings and preparing for large parties, confirming the week's events, training new servers, checking the dining room and its equipment, and reviewing guest feedback. The front of house manager owns it.

The most useful front of house habit is a daily look at the next few days' bookings: large tables, guests with allergies, regulars, special occasions. Preparing for them a day ahead makes the evening easier.

A venue without a system cannot build one overnight. Start with three jobs: the weekly review, the daily cash-up and the opening and closing checklists. They are simple, they produce quick results, and they create the habit of doing things on time.

Then add the others, one every few weeks: the forecast and rota, ordering and stock counts, prep planning, briefings, cleaning and maintenance. Each one is easier once the earlier ones are in place.

Once the system runs, improve it steadily. Look at which jobs are often missed, which take longer than they should, and which produce problems later in the week. Change one thing at a time, and check whether it helped.

Our guide to how to improve restaurant operations in ninety days covers choosing three changes a quarter and telling whether they worked.

In a small venue, one person may own several jobs, and some may be very simple: the weekly review may be the owner and chef over a coffee; the forecast may be a glance at the bookings. That is fine. The point is not formality but regularity: the same jobs, at the same time, every week.

A small venue arguably needs the system more than a large one, because there is no layer of managers to catch what the owner forgets.

In a group, each venue runs its own weekly system, and the group adds a layer on top: a weekly meeting of venue managers, consolidated numbers, shared standards and procedures. The venue systems should look similar, so that managers can cover for each other and the numbers can be compared.

Our guide to multi-venue operations: what to centralise covers what the group should share and what each venue should keep.

Here is an illustrative venue before and after building its weekly system. The details are examples.

Within two months, the managers said they spent less time firefighting, waste fell because prep followed the forecast, and the team appreciated knowing their shifts earlier.

In servearound, the service side of the week runs through Order Fulfillment. Checks open on the floor plan; courses can be sent, held and fired; and tickets reach each station oldest first, with allergies, seats and removed ingredients shown, on a touch screen or a bump bar. The kitchen's live view shows new, preparing, ready and delayed tickets, the oldest ticket and the load on each station, and kitchen analytics shows ticket times and the on-time rate afterwards.

Bookings and the week ahead sit in the reservations calendar, and each venue has its own team chat for the messages that used to get lost. servearound does not hold rotas, stock counts or cleaning checklists; those stay in the tools you use now. See Order Fulfillment, or get in touch to talk through your week.

Everything a venue does to be ready for guests and look after them: buying, preparing, staffing, cleaning, serving, counting and reviewing.

The weekly review, forecast and rota, ordering and stock, prep planning, opening and closing checks, the pre-service briefing, the cash-up and cleaning and maintenance.

One named person per job, with a named cover for when they are away.

Yes, perhaps more than large ones. The system can be simple, but it should be regular.

Written descriptions of how recurring jobs are done, so they are done the same way whoever does them.

Short enough to be used every day: the checks that matter, not every possible task.

With the weekly review, the daily cash-up and opening and closing checklists. Add the other jobs one at a time.

Jobs happen on time, managers spend less time firefighting, and the weekly numbers become easier to read and act on.

Restaurant operations work best as a weekly system: eight recurring jobs, each with an owner and a day. The weekly review, the forecast and rota, ordering and stock counts, prep planning, opening and closing checks, the pre-service briefing, the cash-up and the cleaning and maintenance schedule together keep the venue running and feed each other.

Hold the system together with daily checklists, clear manager routines and short standard operating procedures, name an owner and a cover for every job, and build it gradually, starting with three simple jobs. Then improve restaurant operations one change at a time, so the managers spend their time on guests and the team rather than on emergencies.