The Three Most Common Places Cash Leaks from a Kitchen Door


TL;DR If your restaurant falls apart the moment you step back from it, the problem is structural, not personal. Independent operators who build proper systems for their people, their operations, and their kitchen end up with restaurants that run consistently, protect their reputation, and give them something back. The ones who do not remain permanently on call in a business that owns them rather than the other way round.
I have met owners who cannot take a Sunday off without their phone going four times before noon. I have met chefs who built genuinely good restaurants and then watched them slowly drain the life out of them because they could never quite let go of being the person everything ran through.
I understand it. When you build something from nothing when you have poured money, time, and a significant piece of yourself into a restaurant it feels like yours in a way that goes beyond the legal sense. It feels personal. And so you treat it personally. You are there every service. You handle the difficult table yourself. You sort the supplier problem because you know the rep. You cover the shift because it is easier than the alternative.
What you have built, without meaning to, is a business that only works because you are in it.
That is not a restaurant. That is a job you happen to own.
A baby needs you. Constantly, urgently, and without much regard for whether you have anything left to give. You cannot reason with it. You cannot delegate to it. You cannot leave it alone and expect to come back to find everything as you left it.
A lot of restaurants work exactly like this. The owner is the answer to every question that does not have a written process behind it which, in most independent restaurants, is most questions. The team is capable of people who have learnt, consciously or not, that it is easier to ask than to decide. And the owner has learned, consciously or not, that it is faster to answer than to build the system that makes the answer unnecessary.
This loop does not break itself. And the longer it runs, the harder it is to escape.
A restaurant that works is a machine. Not in the cold, clinical sense the warmth, the hospitality, and the cooking, those remain entirely human. But the structures underneath them: the prep systems, the ordering process, the opening and closing procedures, the way a new team member is brought up to standard, the way a complaint is handled when you are not in the building those should run whether you are there or not.
This is what the best-run kitchens actually look like. Not kitchens where everyone is waiting to be told what to do, but kitchens where everyone knows what good looks like, knows what their job is, and has the tools and the authority to do it.
That does not happen by accident. It happens because someone decided to build it deliberately, one system at a time.
The honest difficulty for independent restaurant owners is that building systems feels like a luxury for people with more time and more resources than you currently have. There is always a service to get through, a rota to sort, a problem to fix. The urgent crowds out the important, week after week.
But here is the thing: the reason you have no time to build the systems is precisely because you have not built them yet. Every hour you spend being the answer to a question that should have a process behind it is an hour you are not spending making the business less dependent on you.
You will not find the time. You have to make it, and that means accepting that some things will be done less well in the short term, by someone other than you, while you do the work that actually changes the shape of the business.
You do not need to fix everything at once. Start with the three areas where your absence causes the most disruption.
For most independent operators, that tends to be people, operations, and the kitchen itself.
Your people system is how new staff are inducted, trained, and brought to standard. If that process currently lives mostly in your head, or relies on whoever happens to be senior that week, it needs to be written down. Not a fifty-page manual a clear, usable set of standards that anyone can follow and any manager can enforce.
Your operations system is how the restaurant opens, runs, and closes when you are not directing it. Checklists, procedures, and decision-making authority for your team. The goal is that a competent manager can run a solid service without needing to call you.
Your kitchen system is how the food gets made consistently, to standard, across every service. Recipes, specs, prep sheets, portion controls. Not because you do not trust your chefs, but because consistency is what protects the reputation you have spent years building.
None of this is glamorous work. But it is the work that turns a restaurant that depends on you into one that does not.
If you stepped away for a month genuinely away, not checking in, not available by phone what would happen?
If the honest answer is that things would start to unravel within a week, that is the answer you need to take seriously. Not as a criticism of your team, but as a clear signal about what you have and have not built.
The goal is not a restaurant that does not need you. The goal is a restaurant that does not only work because of you. There is a significant difference, and it is worth building towards.
I am a hands-on chef-owner. Surely my presence in the kitchen matters?
It does, and there is nothing wrong with choosing to cook in your own restaurant. The question is whether you are there by choice or by necessity. A chef-owner who has built strong systems, trained their team well, and documented their recipes and standards can step back when they need to. One who has not cannot and that distinction becomes very important the moment life requires you to be somewhere else.
My team are not ready to run things without me.
That may be true right now, but it is also partly a product of how you have run things until now. If your team has always deferred to you, they will continue to do so until you deliberately build their capability and confidence to decide. That takes time and some tolerance for imperfection, but it is how it gets done. Waiting until they are ready without actively developing them is not a strategy it is a holding pattern.
My restaurant is small. Does any of this apply at a smaller scale?
Yes, more than you might think. Small operations are often the ones most damaged by the owner’s absence, because there is less redundancy. A clear set of opening procedures, a trained senior member of staff with defined authority, and a kitchen that runs to documented standards cost nothing except the time to create them and pay back many times over.
Does systematising a restaurant not strip out the character?
No and this is a misconception worth challenging. The character of a restaurant comes from its food, its people, its atmosphere, and the decisions its owner has made about what kind of place it should be. Systems do not replace any of that. They protect it. A kitchen that consistently produces food to your standard because the processes are clear is a more characterful restaurant than one that produces it brilliantly one night and poorly the next because it depended on who happened to be in.
Where do I actually start?
Pick the single thing that causes the most disruption when you are not there. Write down how it should be handled. Make sure the right person has the authority and the knowledge to handle it. Then move to the next one. It is not a quick process, but starting somewhere specific is far more useful than waiting for a moment of calm that is unlikely to arrive.
A restaurant that only runs because you are in it is not a functioning business; it is a daily act of will that ends when you do. The chefs and operators who build something lasting are the ones who put the same care into their systems as they put into their food. Every process you document, every standard you set, every decision you hand to a capable team member is an investment in a restaurant that exists beyond your constant presence. That is what separates the places that endure from the ones that were always, in the end, one person’s effort held together by the force of their personality.
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