Head Chef Leadership and Brigade Mental Health


TL;DR: The four-day workweek kitchen model uses rotating compressed schedules to cut burnout without closing on busy days. Early results show improved chef retention and lower recruitment costs. It requires careful rota design but is operationally viable.
The four-day work week in a professional kitchen sounds, at first hearing, like something dreamed up by someone who has never worked a Saturday service in their life. And yet here we are, and it is working.
I will be honest with you. When I first heard that kitchens were trialling compressed schedules and rotating four-day patterns, my instinct was to roll my eyes hard enough to strain something. Kitchens run seven days. Guests eat seven days. The idea that you could restructure that without the whole thing collapsing into chaos seemed faintly delusional. Then I looked at the numbers on chef retention strategies, and the eye-rolling stopped fairly quickly.
The hospitality workforce retention problem is not new, but it has got considerably worse since 2020. Chefs who left during the pandemic closures discovered something inconvenient: other industries pay more, finish earlier, and do not expect you to work Christmas Day on the understanding that you are ‘passionate about food’. Passion does not pay a mortgage, and it turns out people noticed.
Recruitment has become painful in ways that go beyond the usual difficulty of finding a decent sauce chef. Whole brigades are being rebuilt from scratch on a rolling basis. Training costs money. Constant turnover costs more. And the quality of food suffers in ways that are difficult to admit out loud but are entirely obvious on the plate.
Reducing chef burnout is not a wellness initiative. It is an operational necessity. A burnt-out chef is slower, less precise, and tends to leave in the spring without much notice.
The phrase ‘four-day work week’ needs unpacking here, because it means different things in different operations. In most hospitality contexts, it does not mean ten-hour days compressed into four. What it more often means is a genuine four-days-on, three-days-off rota pattern, achieved by splitting the brigade into overlapping teams and scheduling accordingly. It requires more people, not fewer. That is the first thing to understand.
A restaurant opening seven days a week needs coverage across all of them. If your team of eight works four days each on a rotating pattern, you need ten or eleven people to cover the same hours a team of eight previously covered at six days each. The maths is not complicated, but the upfront staffing cost makes owners nervous. What changes the calculation is retention. Keep your chefs for three years instead of eighteen months, and the recruitment and retraining costs largely disappear.
A number of independent restaurants in the UK have trialled this model since 2021, with some running it quietly and successfully without making a particular fuss about it. The ones I have spoken to report the same things: lower sick leave, higher consistency, and chefs who actually turn up in a reasonable state of mind at the start of service.
Modern kitchen management under this model tends to work best when you split your brigade into two named teams rather than simply issuing rotas. Call them what you like. Red and blue, A and B, whatever avoids sounding like a school sports day. The point is that each team has its own identity, its own rhythm, and a genuine sense of ownership over the days it covers.
The practical challenge is handover. A kitchen that runs a changing menu needs every team member to know where everything is, what is being prepped, and what the state of the walk-in is at the end of each shift. This requires a handover culture that most brigades do not naturally have. Written notes, tasting notes, clear labelling, and a brief overlap between outgoing and incoming team leads. It takes about three months to bed in properly. Before that, it is slightly chaotic. After that, it runs.
One thing I did not expect: the quality of cooking on day four of a four-day run is noticeably better than it was on day six of a six-day run. That sounds obvious once you say it. At the time it surprised me.
I asked a group of chefs working under a four-day rota what had changed for them in practical terms. The answers were fairly consistent. They sleep more. They cook at home occasionally, which several of them had stopped doing entirely. They see their families on a weekday, which matters when your partner also works and weekends are complicated. One sous chef told me she had started going to the gym again for the first time in four years. She said it as if she was slightly embarrassed about it, which tells you something about the culture we have built in professional kitchens.
None of them said the work had got easier. The four days they are in the kitchen are still full days. The pressure of service is unchanged. But the recovery time is there, and recovery changes everything about how a person performs under pressure.
The most common objection from operators is cost. More staff means higher wages, higher NI contributions, more management overhead. This is true. It is also true that replacing a skilled chef costs somewhere between one and two times their annual salary when you account for recruitment, training time, and the reduced output during that period. The four-day model tends to pay for itself within twelve to eighteen months if you are losing chefs regularly. If your retention is already strong, the case is harder to make.
The second objection is consistency. How do you maintain a consistent product across two teams? The answer is the same as it always has been: good recipes, good training, and clear standards. The four-day model does not create inconsistency. Poor systems create inconsistency. The rota is not the problem.
The third objection, which is rarely stated directly, is cultural. Some operators feel that a demanding schedule is part of the identity of professional cooking. That suffering is somehow instructive. I understand where this comes from. I came up through kitchens where sixteen-hour days were considered normal and complaining was career-limiting. I am not convinced it made me a better cook. It made me tired and occasionally insufferable, which is not quite the same thing.
The four-day rota is one tool among several. It works best alongside a few other changes that are less headline-grabbing but equally important. Clear progression paths matter, because chefs leave when they cannot see where the next two years take them. Regular one-to-ones matter, because most chefs will not raise a problem until they are already halfway out the door. And pay matters, because no rota adjustment compensates for wages that are genuinely below what the work deserves.
Restaurant staff wellbeing also includes the texture of daily working life. Shouting less. Explaining more. Treating a mistake as a teaching moment rather than an opportunity to embarrass someone in front of the section. None of this is soft. All of it is practical. A kitchen where people feel respected is a kitchen where people stay.
In most cases, yes. To maintain seven-day coverage with four-day individual schedules, you need a larger team than you would with a six-day rota. The offset is the reduction in recruitment and retraining costs when retention improves, which tends to make the model cost-neutral or better within about a year and a half of consistent operation.
Through strong systems, not through having the same people in every day. Detailed prep notes, clear labelling conventions, a proper handover between team leads, and training that is documented rather than passed down verbally. Consistency comes from process. The rota does not change that requirement.
It suits restaurants with sufficient volume to justify a larger team. A very small owner-operated place with three kitchen staff is unlikely to make the numbers work. Restaurants opening seven days with a brigade of eight or more are better placed to trial it. Hotel kitchens and catering operations with predictable scheduling are often the easiest environments to start with.
Handover culture. Kitchens are not naturally good at communicating between shifts. Building the habit of written handovers, tasting notes, and prep status updates takes deliberate effort and probably three months before it feels natural. After that, most brigades find it less effortful than they expected.
The real question is not whether this model works. Several kitchens have already answered that. The question is whether the industry has the appetite to accept that the way things have always been done is not the same as the way things have to be done.
Chef Ian McAndrew’s specialist eBooks and guides are available directly on ChefYesChef, including his technical titles and autobiography. If you want more practical, chef-led reading beyond this article, you’ll find the full collection here.
Chef Ian McAndrew works with chefs, businesses, and individuals on a wide range of culinary projects, from concept development to practical problem-solving.
If you’d like to talk through an idea or need informed guidance, you’re welcome to contact him.
Essential cookies required for the site to function. Cannot be disabled.
Cookies that help us understand how visitors use the site.
Cookies used to deliver relevant advertisements.
Privacy Policy Terms of Service