Kitchen teamwork works like a well-oiled machine - everyone has their part. Who enters temperatures, checks recipes, and tracks food costs? Without clear agreements, your records develop gaps and you lose control of your numbers.
Why making agreements matters
During busy service, everyone assumes someone else handled it. Temperatures get skipped, recipes go unchecked, and food costs spiral out of control. The result: your numbers no longer reflect reality.
⚠️ Note:
Without clear agreements, gaps appear. The NVWA doesn't check who entered what, but whether it was entered. You're ultimately responsible.
Divide tasks based on kitchen workflow
The smartest division follows your kitchen's natural rhythm. Link tasks to specific moments throughout the day.
💡 Example: Daily task schedule
Morning (8:00):
- Sous chef: measure and enter fridge temperatures
- Sous chef: check and register deliveries
Afternoon (14:00):
- Chef: enter or adjust new recipes
- Chef: check food costs after purchase price changes
Evening (22:00):
- Dishwasher: complete cleaning log
- Chef: review daily report
Build a RACI matrix for your kitchen
RACI means: Responsible (does it), Accountable (ultimately responsible), Consulted (is asked), Informed (is notified). This eliminates confusion about who handles what.
- Temperature registration: Sous chef does (R), Chef checks (A)
- Enter recipes: Chef does (R), owner checks (A)
- Update food costs: Owner does (R), accountant is informed (I)
- HACCP checks: Assigned staff member does (R), chef checks (A)
Schedule regular check moments
Entering data is step one, verifying it is equally crucial. From years of working in professional kitchens, I've learned that scheduled verification prevents most data problems before they start.
💡 Example: Check routine
Daily check (5 minutes):
- Were all yesterday's temperatures entered?
- Have deliveries been registered?
Weekly check (15 minutes):
- Do food costs still match reality?
- Have new recipes been entered completely?
Monthly check (30 minutes):
- Overview of all registrations
- Are there patterns in what gets forgotten?
Apply the four-eyes principle
Critical data should always get reviewed by two people. This catches errors and ensures better quality control.
- New recipes: Chef enters, owner checks before publishing
- Price changes: Buyer adjusts, chef checks impact on food cost
- HACCP critical points: Staff member measures, supervisor checks daily
Document your agreements
Verbal agreements get forgotten during busy shifts. Write down who does what, when, and how often. Post this somewhere everyone can see it daily.
💡 Example: Kitchen task list
Daily:
- 8:00 - Sarah: Measure fridge temperatures (fridge + freezer)
- 9:00 - Mark: Check and enter deliveries
- 22:00 - Lisa: Register cleaning
Weekly:
- Monday 14:00 - Chef: Check food costs
- Friday 16:00 - Owner: Review weekly overview
Train your team on the system
Make sure everyone understands how the system works. Not just their own tasks, but also why it matters and what happens if things get missed.
- Show: How to enter data in the app
- Explain: Why this registration matters
- Practice: Have everyone do it several times themselves
- Check: Extra attention the first week for new tasks
Plan backup for absences
What happens if the person who normally enters temperatures calls in sick? Make sure there are replacements who know how to handle it.
⚠️ Note:
During an NVWA inspection, you can't say 'the person who normally does this was sick'. You're required to maintain registrations regardless of staff changes.
Use digital tools for oversight
An app shows who entered what and when. This makes it easy to verify whether all agreements are being followed, without you having to track everything manually.
How do you set up a working task division?
Make a list of all tasks
Write down all tasks that need to happen daily, weekly, and monthly. Think about temperatures, recipes, food costs, deliveries, and cleaning. Don't forget checks either.
Link tasks to natural moments
Tie tasks to fixed moments in the workday. Temperatures at opening, deliveries at arrival, recipes during quiet afternoon hours. This makes it easier to remember.
Assign people with backup
Give each task to a specific person, but also train a replacement. Document who does what and post it visibly. Check extra carefully the first few weeks to make sure everyone is doing their tasks.
✨ Pro tip
Audit your data entry agreements every 90 days to catch gaps before they become problems. Staff turnover and menu changes often create blind spots in your system.
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
What if my team doesn't follow the agreements?
Start by understanding why. Are the tasks unclear, too time-consuming, or do people just forget? Adjust the agreements where needed and make consequences clear.
How often should I check if everything is being entered?
A quick daily check (2-3 minutes), a thorough weekly check (15 minutes). More often at first, later you can reduce it as it becomes routine.
Can I automate tasks instead of dividing them?
Some things yes, others no. Temperatures must be physically measured and entered by someone. Food cost calculations can be automatic, but someone needs to update purchase prices.
What do I do if someone who did important tasks resigns?
Make sure all procedures are documented and not just in someone's head. Always train at least two people per critical task so you can switch over quickly without gaps.
How much time does it take to set up agreements properly?
Setting it up the first time takes an afternoon. Then about a week to see if it works and make adjustments. Invest this time upfront, otherwise it'll cost you much more time later.
Should different staff levels have different system access?
Yes, limit access based on roles. Line cooks might only enter temperatures, while chefs can modify recipes and costs. This prevents accidental changes to critical data.
📚 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.
Give your team insight into the numbers
When your team understands what dishes cost, their behavior changes. KitchenNmbrs makes food cost visible to everyone in the kitchen. Start your free trial.
Start free trial →