Team and management

Restaurant opening: how to prepare your team before day one

Preparing a restaurant opening means writing each role, training before the first service, running a dress rehearsal and correcting every night for two weeks.

Published on

Days before opening, the new team listens to the manager in the unfinished dining room

Preparing the team for an opening comes down to four steps: write down what each role does, train before the first service, rehearse with real guests, then correct every night for two weeks. A ready team is not a fully staffed team. It is a team that knows who does what, in what order, and where to find the answer when doubt hits.

The Thursday evening when nobody knows who rinses the ice bins

It is 5 p.m. on Thursday, two days before opening. The chef has the recipe cards, the owner has the budget, the front-of-house manager has the floor plan. The team arrives for the first rehearsal. A line cook asks who prepares the bread before service. The sous chef says "the floor." The front-of-house manager says "the kitchen." A server is looking for somewhere to put dirty glasses, because nobody has decided how the dish pit flow works.

It is nobody's fault. Everyone held one piece of the opening in their head, and those pieces had never been put on the same page. That is the real work of an opening on the people side: turning scattered intentions into a shared way of operating.

Why openings go off the rails on the people side

Three causes come up almost every time.

  • Recruiting dictates the calendar. You hire when you find someone, so training gets squeezed into the last few days, or replaced by "we'll figure it out as we go."
  • The standards live in the founders' heads. The owner knows how service should run but has never written it down. In the first days everyone asks them, and they become the bottleneck.
  • Training covers theory, not the real workflow. A recipe can be read on a card. The flow of plates, cutlery and waste only reveals itself inside the actual walls, with the actual equipment.

A fourth trap is quieter: an opening team mixes people who already know each other with people who have never met. The first group organizes itself with half-sentences. The second feels left out or does not dare to ask questions.

The preparation calendar, phase by phase

PhaseWhat you produceProof it is done
Six weeks beforeList of roles, with morning, service and closing tasks for eachOne page per role, reviewed by the chef and the front-of-house manager
Four weeks beforeCritical tasks identified (food safety, allergens, safety, cash handling)A short list signed off by the owner
Two weeks beforeTraining by role, onboarding plan for new hiresA training schedule with a point person for each new hire
One week beforeRehearsal service with guests you knowA written record of what went wrong
Opening weekFixes from the rehearsal appliedUpdated, dated role sheets
Days 1 to 14A ten-minute check-in every nightA list of gaps, closed or assigned

There is nothing sacred about this calendar. What matters is the order: write before you train, train before you rehearse, rehearse before you open.

The method, in six steps

  1. Write the typical day for each role. Who, what, at what time, for how long. The chef writes the kitchen's, the front-of-house manager writes the dining room's. A spreadsheet is enough, one sheet per role.
  2. Mark the tasks nobody should learn on the fly. Temperature checks, allergen handling, opening and closing the register, safety instructions. These are taught and signed off before the first service.
  3. Name one point person per new hire. One name, not "everyone." They answer the questions of the first week.
  4. Run the rehearsal like a real service. Tickets, pace, dish pit, closing. An observer takes notes without stepping in.
  5. Fix the role sheets, not just the people. If two people made the same mistake in the same place, the sheet or the workflow is unclear.
  6. Hold a ten-minute check-in at the end of every service for two weeks. Three questions: what went wrong, what did we say more than once, what is missing.

The mistakes that cost the most

  • Betting everything on the first service. The opening is not decided that night. The first two weeks are when habits set, good or bad.
  • Training everyone at once, in the dining room. Kitchen skills are not learned in the noise of a group meeting. Train by role, in small groups.
  • Mistaking energy for preparation. An enthusiastic team that does not know where the temperature log is kept is still a team improvising.
  • Saving corrections for the end of the month. A gap noted the same day takes five minutes to fix. After three weeks, it has become a habit.

Three indicators to judge the opening

You do not need a dashboard. Three things are enough, observed every week:

  • The number of identical questions asked several nights in a row. They point to a missing standard.
  • The number of times someone stepped in across stations. When the floor team clears for the dish pit every night, the workflow is badly designed.
  • How long before a new hire works without a point person beside them on basic tasks. Measure it in services, not calendar days.

Noted by hand, these three observations say more than a satisfaction score.

Where Tsuno comes in

Tsuno keeps what was decided during preparation: typical days by role, expected tasks, the chef's instructions, everything that was said once and should not have to be said again. These items are attached to a role and passed on through checklists, training and the onboarding of new hires. Gaps noted during the first services are dated and stay available. If the owner asks "what is going wrong at the opening this week?", Tsuno answers from what has been entered, and says when data is missing. It does not score new hires and judges no one: it connects the facts, the team decides. The details of each module are on the features page.

To go further in your preparation

The hardest part is moving from the founder's knowledge to a written way of operating. How to reduce onboarding time without cutting corners covers welcoming a new hire, and how to know when a new employee is actually ready gives the criteria for removing the point person. To assign roles, lean on a useful skills matrix. And for following the first weeks, keep in mind that managers do not need another dashboard: ten minutes of check-in a night beat a report.

Key takeaways

A successful opening on the people side is prepared in order: write the roles, train on the critical tasks, rehearse, then correct every night. Fix the sheets before you fix the people. The sign of good preparation is not the absence of problems at the first service. It is that every problem gets a written answer by the next day.

Frequently asked questions

How long before opening should you hire the front-of-house and kitchen team?

Early enough for them to complete training and take part in at least one rehearsal service. Fix that constraint first and work your hiring calendar backward from it, not the other way around.

Do you need a rehearsal service before opening?

Yes. A practice service with guests you know exposes the gaps in roles, workflows and equipment that nobody sees on paper. Better to find them in front of friends and family than in front of the first full dining room.

Who should train an opening team: the chef, the owner, a manager from another location?

Skills are best passed on by people who do them every day, often experienced team members from another location. The owner or the chef sets the standard but should not be the only trainer.

What if part of the team is hired at the last minute?

Separate the critical tasks (food safety, safety, allergens, cash handling), which must be mastered before the first service, from the tasks that can be learned with someone alongside. Late hires go on low-risk stations with a named point person.

How do you know the opening is going well on the people side after the first week?

Look at the questions that come back every night, the stations where someone had to step in, and the instructions given more than once. If the same issues return three days in a row, the problem is in the standard, not in the person.