New Head Chef Onboarding: The First 90 Days
TL;DR: New head chef onboarding works when the first month is spent observing, not changing. Learn the team, the suppliers, and the informal power structures before you act. The first 90 days set the tone for everything that follows.
Getting new head chef onboarding right is the difference between a kitchen that finds its feet in three months and one that loses half its brigade in six. The first ninety days are not a grace period. They are an audition, for everyone.
I say that having been on both sides of it. Years ago, I walked into a kitchen where the previous chef had run things with a combination of autocracy and selective amnesia. Nobody wrote anything down. The fish order was apparently kept ‘in Terry’s head’, and Terry had left. It took me six weeks just to work out what the restaurant was actually trying to be. Six weeks I could not afford.
Why the First Thirty Days Are Not About Cooking
Most incoming head chefs want to get straight into the food. Understandable. It is what they know, what they are good at, and frankly it is more comfortable than sitting in the dry store asking where the lentils come from and why. But the first month should be almost entirely observational.
Watch service. Watch how the team communicates, or fails to. Notice who leads informally, because that person exists in every kitchen regardless of what the org chart says. See which supplier deliveries arrive short, which sections habitually run out of mise en place by nine o’clock, and whether the pastry chef and the sous chef actually talk to each other.
This is not passivity. It is intelligence gathering. You cannot make good decisions about a kitchen you do not yet understand, and the kitchen will respect you more for taking the time to learn it rather than arriving with a rolled-up menu and a set of assumptions.
New Head Chef Onboarding: What Management Owes the Chef
This section is for the owners and general managers reading over someone’s shoulder, and you know who you are. Onboarding is not something that happens to the chef. It requires active participation from above.
Before the new head chef walks through the door, certain things need to be in place. A clear brief on the food direction, access to the last twelve months of GP figures, introductions to the key suppliers, and an honest conversation about what the previous chef did well and what went wrong. Not a sanitised version. The real one.
Withholding that information to avoid awkwardness is how you guarantee the new chef will discover it at the worst possible moment, usually mid-service in front of the team.
The Handover Document
If the outgoing chef is still around, insist on a written handover. Verbal handovers are essentially rumours. A decent handover document covers current supplier contacts and lead times, standing orders, any dietary or allergen agreements already in place with regular guests, and which pieces of kit are held together by optimism and a single cable tie.
It does not need to be literary. It needs to be accurate and complete.
Kitchen Leadership Transition: Building Trust With the Brigade
A kitchen leadership transition lives or dies on the chef de parties and the senior section cooks. These are the people who actually run the pass on a Tuesday night when things go sideways, and they have usually seen a few new head chefs come and go. They will be watching.
The worst thing a new head chef can do in the first month is make obvious changes without explanation. Moving the garnish station, changing the prep rota, pulling a dish that the team has cooked two hundred times: all of these can be entirely reasonable decisions, but if they arrive without context they read as territorial, not strategic.
One-to-one conversations with each section chef, early and without agenda, are worth more than any team meeting. Ask what they find frustrating. Ask what they think works. Then actually listen, rather than using the question as an opportunity to deliver your own answer.
Taking Over a Kitchen: The Menu Question
Taking over a kitchen and immediately rewriting the menu is rarely as impressive as it feels. There is always pressure, from owners especially, to see visible change fast. A new menu feels like progress. Sometimes it is. Often it is just noise.
The smarter move is to assess what is already on the menu before deciding what needs to go. Some dishes will be genuinely good and the team will know how to cook them in their sleep. Those are assets. Some dishes will be there out of inertia, cooked badly, ordered rarely, and quietly resented by the section that has to prep them. Those are the first to go.
A considered partial menu refresh in the first sixty days, built around the season and the kitchen’s actual capability, will serve you better than a complete overhaul that the team does not yet know how to execute consistently.
Seasonality and Supplier Relationships
New chef, new relationships. Meet the suppliers in person where you can. Not every supplier is worth keeping, but you will not know that from a phone call. A good fishmonger will tell you what is coming in before you ask. A poor one will tell you whatever shifts the stock.
Build the menu around what is actually available and good right now, not around a concept that requires ingredients flown in from somewhere that the budget will not support by February. The kitchen will thank you for it. The GP will too.
Days Sixty to Ninety: Making the Kitchen Yours
By the end of the second month, you should have a clear picture of the kitchen’s strengths, its gaps, and the two or three people you are actually building around. This is when you start making structural decisions with confidence rather than instinct.
Review the prep schedules. Look at where labour is being spent and whether it matches where the revenue comes from. If Saturday lunch is consistently your quietest service but requires the same prep commitment as Saturday dinner, that is a conversation to have. Not every inefficiency is the team’s fault. Some of them are built into the systems the kitchen inherited.
By day ninety, the team should have a reasonable sense of your standards, your style, and what you will and will not tolerate. Not through announcements. Through consistent behaviour, every shift.
Common Pitfalls in the First Ninety Days
- Changing too much too quickly, without explaining the reasoning to the team
- Relying on verbal communication for systems that need to be written down
- Ignoring the informal hierarchy in the brigade and expecting the org chart to do the work
- Avoiding difficult conversations about underperformance until it becomes a crisis
- Assuming the food cost problems are the team’s fault before checking the ordering systems
- Not cooking. A head chef who is not on the tools regularly loses the respect of the brigade faster than almost anything else
Frequently Asked Questions
How long should a new head chef wait before changing the menu?
There is no fixed answer, but waiting at least four to six weeks before making significant changes gives you time to see which dishes actually sell, which the team can execute consistently, and which are carried by reputation alone. Small seasonal adjustments can happen earlier. A wholesale rewrite should wait until you know the kitchen properly.
What should a new head chef prioritise in the first week?
Observation and introductions. Work every section if you can, even briefly. Learn names. Understand the flow of service before you try to alter it. The first week is not the time for big decisions; it is the time to collect the information that will make your decisions better.
How should a new head chef handle an underperforming team member?
Directly and early. A quiet, private conversation in the first month is far preferable to a public correction at the pass in the third. Be specific about what needs to change and give the person a fair chance to change it. If there is no improvement, you have done your due diligence and the decision that follows is easier to justify.
Is it normal for a new head chef to feel overwhelmed in the first month?
Entirely normal, and anyone who tells you otherwise is either lying or did not take the job seriously enough to notice the weight of it. The job carries the food, the team, the costs, and the expectations of management simultaneously. Acknowledging that privately is sensible. Showing it to the brigade constantly is not helpful to anyone.
The Bottom Line
- New head chef onboarding works best when the first month prioritises observation over action
- Management must provide honest context, access to financial data, and a proper handover before the chef starts
- Trust with the brigade is built through consistent behaviour and genuine listening, not announcements
- A partial, seasonal menu refresh in the first sixty days is almost always smarter than a complete overhaul
- By day ninety, structural decisions about systems, staffing, and food direction should be grounded in evidence, not assumption
The ninety-day mark is not when the job gets easier. It is when the excuses run out and the kitchen becomes yours, for better or worse. The ones who get it right are usually the ones who spent the first month learning to ask the right questions rather than delivering the right answers.