Most restaurant owners panic about getting sick because they think their business will collapse without them. But experienced operators know that inexperienced staff can actually keep things running smoothly with proper systems in place. The difference lies entirely in your preparation.
Create an emergency protocol before you get sick
Smart preparation happens during healthy days, not sick ones. Your emergency protocol becomes your staff's roadmap for operating without constant phone calls to your bedside.
💡 Example emergency protocol:
- Daily ordering: which supplier, how much to order
- Critical recipes: exact quantities and preparation method
- Contact details: suppliers, backup chef, accountant
- Daily checks: temperatures, cash register closing, cleaning
Limit the menu to the basics
Fewer menu items equal fewer disaster opportunities. Strip away complex dishes temporarily and focus on what your team can execute flawlessly.
⚠️ Note:
Be upfront with customers. "Due to chef illness, we're running a simplified menu" earns understanding, not complaints.
Daily remote monitoring
Even while recovering, you can track essential metrics. Have your team text you these four numbers daily:
- Yesterday's revenue: Compare it with the same day last week
- Number of covers: Does this match the revenue?
- Waste: What went in the trash and why?
- Problems: What went wrong and how was it solved?
Bring in external help
Sometimes hiring temporary help costs less than staying closed. The math usually works in your favor.
💡 Example cost calculation:
Freelance chef: €200 per day
Lost revenue from closing: €800 per day
Difference: €600 per day savings
What if it takes longer than expected
Extended illness requires strategic adjustments. Based on real restaurant P&L data, these modifications often maintain profitability:
- Shorter opening hours: Dinner only, no lunch
- Weekends only: Focus on the busiest days
- Stop catering: Too complex without you
- Expand delivery: Simpler menu, fewer staff needed
⚠️ Note:
Announce changes early through social media and your website. Transparency prevents disappointment.
Digital systems as a lifesaver
Restaurant management apps let you monitor operations from your sickbed. Your staff logs temperatures, you track dish sales, and digital recipes stay accessible 24/7.
This creates peace of mind: your team has every piece of information they need, regardless of your physical presence.
How do you prepare for illness? (step by step)
Create an emergency protocol
Write down: daily ordering, critical recipes, supplier contact details, and important procedures. Keep this somewhere everyone can find it.
Train your staff in the basics
Teach at least 2 people how to check temperatures, place orders, and close the cash register. Practice this regularly when you're there.
Build a network of freelancers
Collect contact details of reliable freelance chefs and wait staff. Test them out during busy periods, so you know who you can count on.
✨ Pro tip
Test your emergency protocols during your next planned day off by staying completely unreachable for 8 hours. You'll discover exactly which systems need strengthening before an actual crisis hits.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Do I have to close the business if I'm sick?
Not necessarily. Staff can handle basic operations with proper emergency protocols and a simplified menu. Food safety and quality must remain non-negotiable though.
How do I prevent my staff from making mistakes without me?
Simplify the menu to dishes they've mastered completely. Document every critical step with clear recipes. Five perfect dishes beat fifteen mediocre ones every time.
What if my illness lasts longer than a week?
Consider hiring temporary help or reducing operating hours. Weekend-only service sometimes generates more profit than running at a loss all week.
Can I give my staff all the responsibility?
They can handle daily operations, but you should monitor the numbers. Daily reports on revenue, problems, and waste prevent small issues from becoming major disasters.
How do I communicate to guests that I'm sick?
Honest professionalism works better than elaborate excuses. "Chef illness has simplified our menu today" usually earns customer understanding and patience.
What happens if my key cook calls in sick too during my illness?
This double-hit scenario requires immediate action. Contact your network of freelance cooks or consider closing for 1-2 days rather than risking food safety. Your reputation matters more than missing revenue.
⚠️ EU Regulation 1169/2011 — Allergen Information — https://eur-lex.europa.eu/eli/reg/2011/1169/oj
The allergen information on this page is based on EU Regulation 1169/2011. Recipes and ingredients may vary by supplier. Always verify current allergen information with your supplier and communicate this correctly to your guests. KitchenNmbrs is not liable for allergic reactions.
In the UK, the FSA enforces allergen regulations under the Food Information Regulations 2014.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →