Recipe management without a binder nobody opens

Most kitchens have a recipe binder. It sits on a shelf in the office or above the pass, it was complete once, and nobody has opened it in months. The recipes in it describe dishes as they were first written, at prices that were current then, with allergen lists that may or may not match what the kitchen cooks today. The real recipes live in the heads of the chefs who cook them, and walk out of the door when those chefs leave.

Recipe management is the work of keeping the written recipes in step with the real ones: what is in each dish, how it is made, what it costs and what allergens it contains, all current. It sounds like administration. In practice it underpins kitchen consistency, protects margins when prices move, and is the only reliable basis for answering a guest's allergen question.

This guide sets out how to manage recipes so the binder problem does not return: one master per dish, clear recipe versions, costs that follow ingredient prices, allergens that change when the recipe does, and a routine that takes minutes rather than days. Every figure in it is an example.

The binder fails for the same reasons in almost every kitchen.

Each of these has a fix, and together the fixes are what good recipe management looks like.

Start with a single rule: every dish has one master recipe, kept in one place, and every other copy is made from it.

The master is the full record: ingredients with specifications and quantities, sub-recipes, method, plating, yield, portion sizes, allergens, cost and version history. Station copies, training copies and the version a central kitchen works from are all taken from the master and replaced when it changes. Our guide to writing a standard recipe card your kitchen will use covers what the station copy should contain.

Where the master lives matters less than the rule. A shared spreadsheet, a shared document folder or recipe software all work, as long as there is exactly one master per dish and everybody knows where it is.

Dishes change, and recipe management has to record the changes without losing the history.

Give every recipe a version number and a date, and change both whenever the recipe changes. Keep a short note of what changed and why: "v4: carrot glaze changed to honey and thyme; cost up 0.12 a portion". Keep old versions rather than overwriting them, so you can see what a dish cost and contained at any point.

Versions matter for three reasons. They tell the line which station card is current. They let you see how a dish's cost has moved as it has changed. And they matter for allergens: if a guest reacts to a dish, knowing exactly what was in it on that date is essential.

Some dishes have more than one valid version at the same time: a summer and a winter garnish, a version with a substitute ingredient for when the usual one is unavailable, a version for a set menu with a smaller portion. Treat each as its own recorded version, with its own costing and allergens, rather than as an informal variation.

When the kitchen switches between versions, the station card and the allergen information must switch too. A winter dish served with its summer allergen list is a risk, not a detail.

The hardest part of keeping recipes current is cost. Ingredient prices change every week, and each change affects every recipe that uses the ingredient, and every dish that uses those recipes.

Doing this by hand, recipe by recipe, is what makes the binder impossible. The fix is to separate ingredient prices from recipes. Keep one list of ingredients with their current price per unit. Build each recipe from that list, so its cost is calculated from the current prices rather than typed in. When a price changes, change it once on the ingredient list, and every recipe and dish that uses it is re-costed at once.

A shared spreadsheet can do this with lookups; recipe software does it as a matter of course. Either way, the gain is large: recipe costs that update themselves mean the kitchen always knows what each dish costs now, not what it cost when it was first written. Our guide to recipe costing covers building a costing, and our guide to purchase price variance covers tracking the price changes that feed it.

Recipe costs are only as accurate as their units. An ingredient bought by the case, used by the gram and costed by the kilogram needs consistent conversions, and each ingredient needs a usable yield after trimming and cooking.

Record, for each ingredient, the purchase unit, the price, the conversion to the recipe unit and the yield. A whole fish bought at a price per kilogram with a 45 per cent fillet yield costs more than twice its purchase price per kilogram of fillet. Our guide to plate cost works through these conversions on one plate. Getting them right once, on the ingredient list, means every recipe that uses the ingredient gets them right too.

Allergen information must follow the recipe exactly. When an ingredient changes, including a change of brand or supplier for the same ingredient, its allergens may change, and so may the allergens of every recipe and dish that uses it.

Hold allergens on the ingredient list as well as on the recipes. A recipe's allergens are then the combined allergens of its ingredients and sub-recipes, and a change to one ingredient shows which dishes are affected. Check the specification of any new product before it is used, and update the ingredient's allergens first.

Then make sure the change reaches the guests. The allergen information on the menu, given to the floor team and shown to guests, must match the current recipe. Our guide to an allergen matrix that stays correct covers the menu-wide view.

Recipe management needs an owner, usually the head chef, sometimes a sous chef or, in a group, an executive chef. The owner approves every change to a master recipe, updates the version and makes sure the station copies and allergen information follow.

The owner does not have to make every change. Chefs who develop or adjust dishes can propose changes, and the owner records them. What matters is that changes go through one person, so the master stays the master.

Recipe management does not need a day a week. It needs a short, regular routine.

For a single venue, that can take thirty minutes a week once the master recipes exist, as an example. The first setup takes longer, which is why it is worth starting with the dishes that matter most.

An invented kitchen keeps its recipes in a shared spreadsheet: one tab of ingredients with prices and allergens, one tab per recipe built from them.

In one week, three things happen. The butter price rises by 6 per cent on the dairy invoice. The supplier substitutes a different brand of stock cubes, which contain celery where the usual ones did not. And the head chef changes the garnish on the fish dish from fennel to samphire.

With the routine above, the butter price is changed once on the ingredient tab, and every recipe using butter, from the mash to the beurre blanc to the pastry, is re-costed. The new stock cube is added as an ingredient with its allergens, the stock recipe is updated to version 3, and the celery flag appears on every dish that uses the stock, which the chef checks against the menu's allergen information before the next service. The fish dish becomes version 5, with its new garnish costed and its allergens checked. The whole week's recipe management takes under an hour.

Without the routine, the butter increase would sit unnoticed in the costs, the celery would be in several dishes without anyone knowing, and the fish dish's card would still say fennel.

Recipes are part of a kitchen's food safety management as well as its costing. The method should include the critical points that keep a dish safe: cooking temperatures, cooling times for anything cooked ahead, holding temperatures and how long prepared components may be kept. When a recipe changes, these may change too.

Keep the food safety steps in the master recipe, not only in a separate manual, so a cook following the recipe follows them automatically. If a change to a dish alters a critical point, such as cooking a component ahead where it was previously cooked to order, review it against your food safety system before it goes live, not after.

Dishes come off the menu, and recipe management should record that too. Mark the master as retired, with the date, rather than deleting it. A dish often returns in a later season, and its recipe, costing history and allergen list are worth keeping.

Retiring a dish properly also means removing its station cards, taking it off the menu everywhere it appears, and checking whether any sub-recipe it used is still needed. A sauce made only for a retired dish is prep time and stock that nobody needs.

The real test of recipe management is the day the chef who created most of the menu leaves. In a kitchen without written masters, the recipes leave too, and the dishes change within weeks, whatever the menu says.

With good recipe management, the hand-over is a matter of walking the new chef through the masters, the versions and the routine. The new chef will want to change things, and should be able to, through the same process of versions and approval. What the business keeps is the record: what each dish is, what it costs and what it contains, independent of who happens to be cooking it.

Consistency is the most visible result of good recipe management. Guests who order a dish again expect it to be the same, and a team that cooks from current recipes, with current station cards, produces the same dish whoever is on.

Consistency also depends on training: the team must know the recipes as well as having them. Train every cook on the current version of each dish, and retrain when a version changes. A recipe the team has never been shown is not a recipe they will follow.

In a group, recipe management is how the same dish stays the same across kitchens. Keep one master per dish for the whole group, owned centrally, and give each kitchen the current station copies. When a dish changes, the master changes first, then every kitchen on the same day.

Allow local variations deliberately, as recorded versions, never informally. A venue that makes a dish its own way has a different dish, with a different cost and possibly different allergens, and the group needs to know.

A well-built spreadsheet handles recipe management for many single venues: an ingredient tab with prices, units, yields and allergens, and recipe tabs built from it with lookups. It costs nothing but time, and it is easy to share.

Recipe software becomes worth its cost when the number of recipes, ingredients, venues or people grows: when keeping lookups working becomes a job in itself, or when several people need to edit at once. Some software connects to invoices and stock, so prices update from invoices automatically. Our guide to moving from a spreadsheet to inventory software covers the signs that it is time.

Whatever the tool, the principles are the same: one master per dish, versions, prices separate from recipes, allergens on ingredients, and one owner. Standard operating procedures in other industries rest on the same idea: one current, controlled version of how a job is done.

If your recipes live mostly in people's heads, start small.

Within a couple of months, the menu is covered, the costs follow prices, and the binder can go in the recycling.

Master recipes, ingredient prices and recipe costs stay in your own spreadsheet or recipe system today: servearound does not hold recipes or costings. What servearound holds is the dish as guests and the kitchen screen see it.

Each dish in menus has its name, description, photograph, price and allergen and dietary information, shown on the guest menu, and a change made there shows on the till and on every guest menu at once. That makes it the place to update when a recipe change alters what guests are told. During service, the kitchen display shows orders by station and course, with guest allergies on the ticket, through the point of sale. If you would like to see how it works, get in touch.

It is keeping a kitchen's written recipes in step with what it actually cooks: ingredients, quantities, method, versions, costs and allergens, all current and in one place.

Keep ingredient prices on one list and build every recipe from it, so a price changed once re-costs every recipe that uses it. Update the prices weekly from checked invoices.

Numbered, dated records of each change to a recipe, with a note of what changed. They tell the line which card is current and keep the history of cost and allergens.

One owner, usually the head chef, who approves changes and keeps the master, the station copies and the allergen information in step.

Hold them on the ingredient list as well as the recipes, so a change of ingredient or brand shows which dishes are affected, and make sure the menu's allergen information follows.

Yes, for many single venues: an ingredient tab with prices, yields and allergens, and recipe tabs built from it. Software becomes worthwhile as recipes, venues and editors grow.

Once the master recipes exist, perhaps thirty minutes a week for a single venue to update prices, record changes and check allergens.

The master recipe is the full record, including costs and history. The standard recipe card is the working copy at the station, with the portions, method, photo and allergens the line needs.

With written masters, nothing is lost: the new chef learns the current versions and can change them through the same process. Without them, the recipes leave with the chef, and the dishes change within weeks.

No. Mark them as retired with the date. Dishes often return in a later season, and their recipes, costing history and allergen lists are worth keeping.

They can propose changes, but one owner should approve and record them. Several people editing the masters freely is how a kitchen ends up with two versions of every dish.

Build an ingredient list for your top ingredients first, then write masters for your best-selling dishes, then add a few dishes a week.

Recipe management keeps the written recipes in step with the kitchen: one master per dish, numbered recipe versions with notes of what changed, and station copies made from the master and replaced when it changes. Keep ingredient prices, units, yields and allergens on one list, and build recipes from it, so recipe costs update themselves and a change of brand shows every dish whose allergens it affects.

Give one person ownership, run a short weekly routine from the week's invoices and changes, and make sure every change reaches the menu, the floor team and the station cards. Start with the dishes that matter most. Kitchen consistency, accurate costs and reliable allergen answers all come from the same habit.