Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Our Specials Board Changes Every Weekend: How Does the Allergen Folder Our Servers Use Keep Up?
Problems We Solve

Our Specials Board Changes Every Weekend: How Does the Allergen Folder Our Servers Use Keep Up?

Restaurant specials and weekend dishes outrun the allergen folder servers use. We build dish sheets generated from the chef's ingredient list, with sign-off.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

An allergen matrix is typed up when the menu launches, then the chef tweaks a sauce, swaps a supplier's product or adds three specials, and the printed matrix no longer matches the food. We build allergen records held against each recipe and its ingredients, so any change to a dish or ingredient prompts the chef to review it, and the front of house information is regenerated from the same data.

The specials board changed, the folder did not

Your allergen folder behind the bar was accurate when the autumn menu launched. Since then the chef has changed the dressing on the salad, the pastry supplier has sent a different product, and there are new specials every weekend. Each change is small. Updating the folder is a job for later, and later becomes next month.

When a guest asks what is in the special tonight, a server either reads a matrix that may be out of date or goes to the kitchen to ask a busy chef. Neither feels good.

Allergen sheets are separate documents, not part of the recipe

In most independent restaurants, recipes live in the chef's head, a notebook or a folder, and the allergen matrix is a spreadsheet typed separately. The two are linked only by someone remembering to update one when the other changes.

  • Specials are created quickly and often never reach the matrix.
  • Supplier product changes alter ingredients without the menu changing at all.
  • Sub-recipes, such as sauces and dressings used in several dishes, have to be updated everywhere they appear.
  • Printed copies stay in circulation after the spreadsheet is updated.

A worked example: the house dressing is used on three dishes. The chef changes one ingredient in it. The matrix row for the dressing is updated, but the three dishes that use it are separate rows, and one of them is missed. The information for that dish is now wrong, and nothing shows it.

Why keeping it current matters to the business

Allergen information is something guests rely on, and something your local authority and your own procedures expect you to keep accurate. Out-of-date information creates a risk you do not want, and the time spent keeping several documents in step is time the chef would rather spend cooking.

Staff confidence matters too. Servers who are not sure the folder is right send every question to the kitchen, which slows service on a busy night.

How we build allergen records tied to recipes

  1. Ingredients are recorded once, with the allergen information from the supplier's specification, and linked to the supplier product they come from.
  2. Recipes and sub-recipes are built from those ingredients, so a dish's allergen information is worked out from what is actually in it, including sauces and dressings.
  3. Any change to an ingredient or recipe marks every affected dish as needing review, and the chef confirms each one before it goes live.
  4. Specials are created in the same system, from existing ingredients, so they have allergen information from the start.
  5. Front of house information, such as a printed matrix, a tablet view or menu cards, is regenerated from the confirmed data, with a version date on it.
  6. A change log shows what changed, when and who confirmed it, so you can see the history of each dish.
ChangeTodayWith linked records
New specialMaybe added to the matrixBuilt from recorded ingredients
Supplier swaps a productNot noticedAffected dishes flagged for review
Sauce recipe tweakedUpdated in one rowEvery dish using it flagged
Printed matrixOld copies in circulationReprinted with a version date

We do not decide what is in a dish or give advice on allergen law or food safety. The chef confirms every dish, and your procedures and your adviser or local authority guidance decide what your records must contain.

What the kitchen and floor see after the change

The chef changes a recipe in one place and sees exactly which dishes need a quick review. Specials come with their information from the moment they are written. Front of house works from a current version with a date on it, and old printouts are easy to spot and replace.

When someone asks when a dish's information last changed, the answer is in the log rather than in someone's memory.

Signs your allergen information is drifting

  • Specials often go out before their allergen information is written up.
  • The matrix is a spreadsheet separate from your recipes.
  • Supplier product changes are not checked against dishes.
  • Servers go to the kitchen for most allergen questions.
  • You are not sure which version of the matrix is behind the bar.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Does the system decide what allergens a dish contains?

It works them out from the ingredient information you and your suppliers provide, and the chef confirms each dish. It does not replace the chef's check or your procedures.

Do we have to enter every recipe?

Yes, once, including sub-recipes. We help structure it so each sauce or base is entered once and reused.

Can it read supplier specification sheets?

Where suppliers provide specifications in a readable format, we can extract ingredient information for a person to check. Nothing is accepted without review.

Does it work with our recipe costing?

It can share the same recipes, so costing and allergen information come from one set of data.

What drives the cost?

The number of dishes and sub-recipes, how supplier specifications arrive and what front of house outputs you want.

Keep reading

More on Problems We Solve

Start here

Tell us what eats your restaurant's admin time

Describe how bookings, the rota, supplier invoices and the end of the night work in your restaurant now, and which booking, till and accounting systems you use. We will tell you what we would build and what we would leave alone, and if your booking system or till can already do it with a setting, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →