Why six weeks is the silent default
The new chef arrives on Monday. You shake hands, hand them a jacket, walk them past the cold room, and introduce them to the team. By Wednesday they're cooking on a section but nothing they make tastes quite like the version you've been doing for two years. By Friday a regular has politely sent the carbonara back. By the end of week three you're doing 60% of the senior chef's job yourself "just for a bit, until they settle in." By the end of week six, either the new chef has slowly absorbed the place by osmosis, or one of you has given up.
This is how most independent UK restaurants onboard a new chef. Not because anyone designed it this way — because nobody designed it at all.
The cost of those six weeks isn't just the salary. It's the regulars who quietly stop coming because the food has been inconsistent for a month. It's the existing kitchen team picking up slack and burning out. It's the owner doing prep at 9am when they should be looking at the books. And it's the not-small chance that the new chef leaves before week eight because they were never set up to succeed.
Two weeks is enough. Not for them to be brilliant — for them to be productive, safe, and pointed in the right direction. The rest is the year that follows. But the first 14 days set whether that year happens at all.
What "onboarded" actually means in week two
By day 14, a chef who's been onboarded properly should be able to do all four of these without supervision:
- Cook every dish on the main menu to your standard, from a written recipe, without asking.
- Run prep for a full service day — knowing what to make, how much, and in what order.
- Work the pass during a busy service alongside the senior team without slowing tickets.
- Identify allergens on every dish, follow your cross-contamination rules, and complete your daily safety logs without prompting.
If by day 14 they can't do any one of those four, the plan didn't work — and the answer is almost never "give them more time." It's "the handover system was incomplete." Which is the part you, as the owner, control.
The day-by-day plan
The structure below assumes a full-time chef joining an established kitchen with an existing head chef or owner-operator on-site. Adjust the pace if the new hire is a senior position (head chef coming in) or a junior section chef — the days compress or stretch, but the order doesn't change.
Days 1–3: kitchen, safety, and the hits
The first three days are mostly absorption, not production. The mistake is to put them on a section in service on day one because "we're short." It feels efficient. It costs you the entire next month.
What gets covered:
- Walk the kitchen. Every station, every fridge, every shelf in the cold room, every cupboard. Where things live. Where things go back to. The labelling system. The use-by rotation.
- Hand over the recipe book. Written, with weights, photos, and allergen tags. Not verbal. Not "I'll show you when we make it." The chef reads it on their own that evening. Discussion happens day two.
- Walk through the allergen and food-safety system. Your cleaning schedule. Your fridge-temp log. Your allergen matrix. Where the chemical storage is. How you handle a customer with a nut allergy. The 14 UK allergens are non-negotiable — every chef should know them by the end of day one.
- Cook your top three hit dishes alongside them. Not them watching you. Them cooking, you correcting. By the end of day three they should have made each of your top sellers at least once, to your standard. If they can't, you've found the gap early.
- Introduce the team properly. Names, sections, who answers what. The kitchen porter who's been there longer than anyone. The pastry chef who handles weekends only. The supplier they'll talk to most.
Days 4–7: shadow service, then run prep
Now they move from kitchen-as-classroom to kitchen-as-workplace.
- Day 4–5: shadow two full services. They stand at the pass with the senior chef. They don't cook. They watch ticket flow, pickup pacing, what gets called when, how plates get checked before going out. They make notes in the evening — what they didn't expect, what was different from their last place.
- Day 6: run prep alone. The senior chef writes the prep list the night before. The new chef arrives early and runs the prep solo. The senior chef does a 9am check, a 11am check, and a final pre-service review. Anything missed, they cover before service. They never re-do it secretly. The new chef has to know what was wrong, or they'll do the same thing tomorrow.
- Day 7: cover one section in service with the senior chef on pass. First cooked tickets. The senior chef calls anything that needs adjusting. The new chef redoes the dish if it's wrong. No silent rescue.
The "silent rescue" trap: the single fastest way to ruin a chef onboarding is to fix their mistakes without telling them. The senior chef redoes the plate, the dish goes out, the new chef never knows. By week three they've made the same mistake 40 times and the senior team is exhausted. Always show the mistake. Always explain the fix. Always let them redo it.
Days 8–10: solo on a section
By day eight the chef runs a full section in service on their own. Pasta. Grill. Cold. Whatever's most central to your menu. The senior chef or owner stays on pass to call tickets and check plates, but doesn't cook in the section.
Three things get reviewed at the end of each evening:
- Ticket times — were any over 25 minutes for mains? If yes, where did the time go? Was it prep, pickup, or pacing under pressure?
- Pickup errors — anything sent back, anything redone, anything that left the kitchen wrong.
- Confidence drift — were there any dishes the chef hesitated on? Don't wait for the dish to come back to find out.
These end-of-shift reviews don't need to be long. Ten minutes after close, three questions, write the answers down. Patterns appear fast.
Days 11–14: own the rotating 20% (specials)
By day eleven the chef should be solid on the main menu. Now you give them their first opportunity to put their stamp on the restaurant — but on safe ground.
You give them the specials slot. The next two weeks of board specials are theirs to design, within your usual constraints (food cost, allergen consideration, supplier availability, your style). They write the recipes, propose the dishes, cost them, brief the team, run them in service.
Why this matters: the rotating 20% is where the new chef earns ownership without breaking the 80% that your regulars come for. If they're a strong fit, you'll see it immediately in how the specials are designed and how they sell. If they're a poor fit, you'll also see it — usually in dishes that don't sell, are too expensive to run, or break food-cost expectations. (For the wider 80/20 menu refresh framework, see our piece on why this rule keeps neighbourhood regulars coming back.)
On day 14, you have the sign-off conversation. It's not a performance review. It's three honest sentences each way.
Side-note: A new chef also has to integrate with the front-of-house team, and that's where most operational friction shows up in week three. We've split that out as a separate piece — see how to fix front-of-house and kitchen communication for the "lamb is pink" / "verbal allergens" / day-one briefing sheet that prevents the most common FOH-BOH blow-ups.
The day 14 conversation
This is the conversation most owners skip, and then six months later wonder why nothing's working. Don't skip it.
You ask:
- What's the hardest thing you've learned so far?
- What's still confusing or where do you feel slow?
- What do you want to own in the next 30 days that you don't yet?
They ask (or you offer):
- Where do I want them to be a month from now — what gets handed off to them next?
- What's the one habit you've noticed that's a strength, and the one habit that's a risk?
- Is the fit honest on both sides — and if not, when do we talk about it again?
This conversation is fifteen minutes. It's the difference between a chef who stays for 18 months and a chef who quietly disengages by week six because nobody told them what success looked like. Our wider staff onboarding piece covers the same pattern for FOH and junior kitchen hires.
What kills chef onboarding (and how to avoid it)
Verbal recipes
If your recipes only live in someone's head, no chef can onboard fast. They have to interrupt service to ask, they get fragments not whole recipes, and the version they build is a mutation of the original. By month three, you have two different carbonaras coming out of the same kitchen depending on the shift.
The fix is unsexy: write the recipes down. With weights. With photos. With allergens called out. A tatty notebook works. A shared note on the kitchen iPad works. A digital tool that auto-prints in service works best because it survives staff turnover. But anything written beats anything verbal.
"You'll pick it up"
Often said with good intent. Almost always the wrong move. "Picking it up" means a chef builds a private mental model of your restaurant that may or may not match the actual restaurant. By the time you notice the divergence, it's set. Explicit beats implicit every time in the first 14 days.
Letting them rewrite the menu in week one
Tempting, especially if the chef is talented. Don't. The hits are the hits because they sell. Your regulars order them by name. A new chef rewriting the menu in week one signals to regulars that the restaurant they trusted is now somewhere else — and you'll feel the bookings within four to six weeks. The chef gets the specials slot. The main menu stays exactly where it was for the first three months minimum.
No formal sign-off
Probation drifts. Three months becomes six. The honest conversation never happens. The chef leaves at month eight without you ever having said "this is what I needed from you and here's how it went." Force the day-14 conversation even if it's awkward. Especially if it's awkward.
Boss-friction
In a small independent kitchen, the owner and the chef butt heads. Different generations, different schools, different ideas of how a section should be run. That's normal. The fix isn't to win every argument — it's to agree explicitly which 20% of decisions are the chef's call ("the specials are yours; how the pasta station is set up at 4pm is yours") and which 80% are yours ("the hit dishes don't change; allergen protocol is non-negotiable; the supplier list is mine for now"). When the lines are explicit, friction drops by an order of magnitude.
How to tell in the first week if you've hired the wrong chef
Most owners don't admit this until month three. By then you've sunk training time, lost team morale, and now have to start the search again — usually in panic mode. The signals are visible in the first seven days if you know where to look.
| Signal | What it means | What to do |
|---|---|---|
| Doesn't ask questions on day 2 | Either ego or disengagement — both are bad | Address directly; if no change by day 5, this is a wrong-fit hire |
| Arrives on the minute every day | Contract minimum, not curiosity | Not a deal-breaker alone, but combined with anything below — red flag |
| Insists their recipe is better than yours by day 3 | Won't follow your standards under pressure | Address in the day-14 conversation explicitly; if it persists, part ways |
| Recipes don't replicate | Skills gap, not effort gap | Solvable with more drilling; not a wrong-fit on its own |
| Doesn't engage with the team | Won't be in the kitchen culture in 6 months | Real-talk conversation by day 7; this rarely improves on its own |
| Allergen sloppiness | Non-negotiable — this is a legal and life-safety issue | One warning, immediate retraining; recurrence = part ways |
One signal alone isn't a verdict. Two signals together is a serious conversation. Three is your hire was wrong and the kindest thing you can do for both sides is admit it before you've both invested more.
The recipe handover question
Every chef onboarding stands or falls on whether the new chef can access your recipes in a form they can actually use. Most independent restaurants struggle here because their recipes are scattered — half on a notice-board in the kitchen, half in the head chef's memory, half on photos in someone's phone.
Three formats work. Pick whichever you'll actually maintain:
- Paper recipe book. A clear ring binder, one recipe per page, with photo, weights, prep notes, allergens. Cheap, works, gets food-stained, needs reprinting every six months. Vulnerable to being lost. Good for kitchens that won't move to digital.
- Shared digital folder. Google Drive, Notion, Dropbox, whatever. One folder per dish, photo + written recipe + allergen list. Survives staff turnover. Searchable. Works on the kitchen iPad. Needs discipline to keep updated — usually broken within a year.
- Purpose-built tool. A restaurant operations app that handles the recipe, allergen, and menu-printing flow in one place. Higher upfront cost (or a monthly fee), but the recipe is always current because the menu is generated from it. This is the path most kitchens with 30+ dishes end up on.
Whatever you pick, the test is the same: a new chef arrives on Monday, opens it on day one, and can cook your top three dishes by Wednesday without asking. If they can't, your handover system is broken — not the chef.
Free download: the 14-day chef onboarding plan
A two-page printable plan you can hand a new chef on day one. Day-by-day milestones, end-of-shift review questions, the day-14 sign-off conversation prompts, and a recipe-handover checklist. Adapt the dish names to your menu and you have a complete two-week plan.
The 14-Day Chef Onboarding Plan (A4 PDF)
Two pages. Day-by-day milestones, the silent-rescue trap, the day-14 sign-off conversation, recipe handover checklist. Print one per hire.
What to do this week
- Write down your top 10 hit dishes — recipe, weights, allergens, photo. If you can't do this in an afternoon, that's the gap your next chef will hit on day one.
- Print or save the 14-day plan above. Keep it ready for the next hire.
- Block the day-14 conversation in your calendar before they start. Make it real.
- Pick which recipe format you're going to commit to (paper book / shared drive / app). Don't run all three half-heartedly.
- If you currently have a new chef in week two: ask the three day-14 questions today. You're behind schedule, but it's not too late.
Two weeks isn't magic. It's just what happens when you decide what "onboarded" means before the new chef walks in, instead of figuring it out as you go. The rest is the same restaurant you already run — you've just stopped paying the silent six-week tax.
If you want a tool that handles the recipe documentation, allergen tagging, menu printing, and daily safety logs that this plan depends on — try Blueroll free for 14 days. The chef-handover flow is one of the use cases it was built for.