A seasonal menu the kitchen can keep up with

A seasonal menu is one of the best things a kitchen can offer. Ingredients at their peak taste better and often cost less. Guests have a reason to come back and see what has changed. Chefs get to cook something new instead of the same dishes for the hundredth week running.

It is also one of the easiest ways to exhaust a kitchen. A menu that changes completely four times a year means four rounds of new recipes, new suppliers, new prep, new training and new mistakes, each landing on a team that is still running service every night. Many venues start a seasonal menu with enthusiasm and quietly abandon it by the second winter.

This guide covers how to plan a seasonal menu the kitchen can keep up with: how much to change each season, which standing dishes should never move, how to plan around seasonal ingredient costs, how to keep each season's recipes on record, and a calendar for changing the menu without a crisis. Every figure in it is an example.

The case for a seasonal menu rests on three things.

The first is quality. Produce in season is usually at its best: tomatoes in high summer, asparagus in late spring, game and root vegetables in autumn. Cooking with ingredients at their peak makes simpler dishes taste better, which is easier on the kitchen as well as better for the guest.

The second is cost. Ingredients in their main season are often cheaper and more reliable to buy, because there is more of them. A dish built on peak-season produce can deliver a better plate at a lower cost than the same dish made out of season.

The third is the story. A menu that changes with the seasons gives regulars a reason to return, gives the team something new to talk about and gives the venue something to say on its website and social channels. Wikipedia's overview of seasonal food gives the broader background.

Seasonal menus usually fail for one reason: too much changes at once. A complete new menu means every station learns new dishes in the same week, every prep list is rewritten, every supplier order changes and every server has to learn a new menu, all while service continues.

The first week of a new menu is always slower and more error-prone. Tickets take longer, dishes come back, waste rises as the kitchen learns new portions. If the whole menu changes, that week affects every table. If it happens four times a year, the kitchen spends a month of every year in that state.

There are other causes too: dishes that look good on paper but are slow to plate during a rush, new suppliers who cannot deliver reliably, and costs that were never checked. But the scale of the change is the main one, and it is the easiest to fix.

The traditional seasonal menu changes four times a year, with the seasons. That rhythm is easy to communicate and gives each menu time to settle. It also means four big changes.

An alternative is a rolling menu: a few dishes change every month or so, as ingredients come into and go out of season. That spreads the work more evenly and keeps the menu closer to what is actually at its best, but it is harder to promote and needs a team that is comfortable with constant small changes.

Many venues land between the two: a main change at each season, with one or two dishes swapped mid-season as particular ingredients peak or fade. Whatever the rhythm, the important decision is how much of the menu changes at each step, and that is where standing dishes come in.

Standing dishes are the dishes that stay on the menu whatever the season: the signature dish regulars come back for, the steady seller that pays the bills, the simple option every menu needs. They are the backbone of a seasonal menu the kitchen can keep up with.

Standing dishes do several jobs. They give regulars something reliable. They give the kitchen dishes it can make in its sleep while the new ones settle. They keep the core of the prep the same from season to season. And they hold the menu's identity steady while the rest of it moves.

Choose them on evidence: the dishes that sell well across every season, that the kitchen makes consistently well, and that guests ask for by name. Our guide to menu engineering, and the four dishes you must act on covers how to find them. A standing dish can still change a little with the season, with a different garnish or side, without becoming a new dish.

A useful rule of thumb is that around a third of the menu changes at each season, while two thirds stay or change only slightly. On an example menu of eighteen dishes, that means five or six new dishes each season, and twelve or so that the kitchen already knows.

That proportion keeps the menu feeling fresh without overwhelming the kitchen. Each station learns one or two new dishes rather than six. The prep list changes in places rather than everywhere. Servers have a handful of new dishes to learn, which they can taste and describe properly.

Spread the new dishes across the menu and across the stations. Five new dishes all on the grill will overload one cook; one new starter, two new mains, a side and a dessert spread the learning. Check the new dishes against the busiest night, too: a dish that takes four minutes to plate is fine at lunch and a problem at eight on a Saturday.

The heart of seasonal menu planning is matching dishes to ingredients at their best and their cheapest. Before designing new dishes, list the ingredients that will be in season during the menu's life, and ask suppliers what they expect to be good, plentiful and well priced.

Build the new dishes around those ingredients rather than starting from a dish and hoping its ingredients are in season. A dish built on what is plentiful will be more reliable to buy, cheaper to make and better to eat.

Plan for the whole life of the menu, not just its first week. A menu that launches at the start of a season will run for three months. Some ingredients will be at their peak in the first month and fading by the third; others will arrive late. A dish that depends on an ingredient with a short season may need a planned swap halfway through.

Seasonal ingredient costs follow a curve. At the start of a season, the first produce is often expensive and limited. At the peak, it is plentiful, at its best and usually cheapest. Towards the end, supply falls, quality varies and prices can rise again.

Plan the menu around the peak. If the season for an ingredient runs from late spring to late summer, a dish that relies on it is best launched as the price falls and retired before it climbs again. Launching on the very first, expensive produce of the year is a choice for the specials board, not the main menu.

Weather moves the curve. A cold spring can delay a season by weeks; a hot summer can bring it forward and shorten it. Keep in touch with suppliers through the season, and have a plan for each key ingredient if its price jumps or supply fails: a substitute, a different dish, or a planned early change.

Seasonal menus often go hand in hand with local sourcing: buying from nearby farms, growers and producers. It can add a great deal: fresher produce, a story guests value, relationships with suppliers who will tell you what is good this week.

It also asks more of the kitchen. Small local suppliers may have less consistent supply, shorter seasons and less flexibility on delivery days. A dish that depends on one grower's crop can disappear from the menu if their harvest fails. Prices may be higher than a wholesaler's, though quality often justifies it.

Plan for that. Use local suppliers for the ingredients where freshness and story matter most, keep a reliable wholesale option for the rest, and agree with local suppliers what happens when they cannot deliver. A seasonal menu built partly on local sourcing is often more resilient than one built wholly on it.

A seasonal menu the kitchen can keep up with uses its new ingredients more than once. If a new seasonal vegetable appears in a starter, a main and a side, the kitchen preps it once, orders it in useful quantities and wastes less of it.

Look for the same principle in the existing prep. New dishes that use sauces, bases or garnishes the kitchen already makes are far easier to introduce than dishes that need entirely new preparation. A new main served with an existing sauce and a new seasonal side is one new thing to learn, not three.

Map the new dishes against the stations and the prep list before finalising them. If one station gains three new preparations and another none, rebalance. If a new dish needs a piece of equipment that is already fully used during service, change the dish.

Seasonal menus create a great deal of knowledge, and much of it is lost. A dish that worked beautifully last autumn is half-remembered the following year: the exact portion, the garnish, the supplier, what it cost.

Keep recipe versions. For each dish, record the recipe as it was served each season: ingredients and quantities, method, portion, plating, photograph and the cost at the time. When a standing dish changes with the season, record that as a new version of the same dish rather than overwriting the old one.

Recipe versions pay for themselves. Next year's autumn menu can start from last year's best dishes, with their costs and specs already on record. A dish that comes back can be costed again against this year's prices, and the kitchen can see exactly what changed between versions.

Every new seasonal dish should be costed before it goes on the menu, using the prices you expect to pay during its season rather than the price of a test batch. A dish that is profitable at peak-season prices may lose money if it is still on the menu when those prices rise.

Cost the plate fully: every ingredient, the garnish, the side and a realistic allowance for waste and trim. Our guide to recipe costing, one dish from box price to plate covers the method, and our guide to plate cost, the arithmetic behind a single dish covers the sums.

Then set the price with the whole menu in mind. A seasonal dish can carry a higher price if it uses a special ingredient, but it should sit sensibly next to the standing dishes, so the menu as a whole stays coherent.

New dishes need testing before they reach guests. Cook each one several times in the weeks before the change: in a quiet afternoon session, as a staff meal, and as a special during a normal service. Each test shows something different: how it tastes, how long it takes to plate, how it holds during a rush.

Training follows testing. Every cook who will make the dish should make it at least once before the change, with the spec and a photograph to work from. Every server should taste it and know how to describe it, what is in it and which allergens it contains.

A soft launch helps. Running the new dishes as specials for a week or two before they join the menu lets the kitchen learn them gradually, gives you real feedback from guests and catches problems before they appear on every table.

Changing the menu goes far more smoothly with a calendar. One that works for many kitchens, counting back from the change date:

Adjust the timings to suit your kitchen, but keep the order. Most menu crises come from skipping steps, especially costing and training.

The week of the change needs some care at both ends of the menu. On the way out, run down stock of ingredients that only the outgoing dishes use, so they are not wasted. A dish that is leaving can become a special for its last few days, using up what is left.

On the way in, order cautiously for the first week. The kitchen does not yet know exactly how well each new dish will sell, and over-ordering perishable seasonal produce is an expensive way to find out. Check sales daily and adjust orders.

Watch the first services closely. Ticket times, dishes sent back and waste all show where a new dish needs adjusting. A short daily conversation between the head chef and the floor manager during the first week catches problems while they are still small.

A seasonal menu is a reason for guests to come back, so tell them. Mention the change on the website, on social channels and in any email to guests who have agreed to hear from you. A photograph of a new dish says more than a list.

On the floor, servers are the best messengers. A server who has tasted the new dishes and can describe them with enthusiasm will sell them far better than a menu can. Brief the team on what is new, what has stayed and what has gone, so they can answer the regular who asks where their favourite dish went.

For standing dishes that change slightly with the season, say so. A note on the menu, or a word from the server, turns "they've changed my dish" into "they've given it an autumn twist".

When the menu changes, every version must change with it: the printed menus, the specials board, the website, the menu on guests' phones and the till. A seasonal menu that is live in the dining room but still shows last season's dishes online disappoints guests who come in for a dish they saw on the website.

Prepare the new versions before the change date, so they can all go live together. Check each one on change day. Our guide to updating the menu in one place, not five covers how to keep them in step, and our guide to menu layout covers how to fit the new dishes on the page without crowding it.

For printed menus, check whether the new dishes fit the existing layout. New dishes with longer names or descriptions can break a layout that was designed for the old ones.

At the end of each season, look back before planning the next. Which new dishes sold well, and which did not? Which were hard work for the kitchen? Which caused waste? What did guests say, and what did the servers hear?

Look at the menu mix for the season against the one before. Did the new dishes take sales from the standing dishes, or add to them? Did any standing dish fall away during the season, which might mean it needs a refresh? Our guide to seasonal trade, mapping your own restaurant year covers how trade itself moves through the year.

Record the answers with the recipe versions. A season's best dishes are candidates to return next year; its weakest are lessons. Over a few years, that record becomes a library that makes every seasonal menu easier than the last.

An invented bistro changes its whole menu of twenty dishes four times a year. The team dreads each change: the first fortnight of every new menu brings long ticket times, waste and complaints, and the head chef is exhausted by the third season.

The bistro changes its approach. It chooses twelve standing dishes that stay all year, some with a seasonal garnish, and changes six dishes each season, spread across the menu and the stations. It builds the new dishes around three or four peak ingredients, each used in more than one dish, and keeps a recipe version of every dish with its cost.

It follows an eight-week calendar, runs new dishes as specials for two weeks before each change and trains every cook before the switch. The next change week is calm. Waste falls, the new dishes sell well from the first day, and the following autumn the team builds its menu from last year's recorded best dishes in half the time.

In servearound, a venue runs one menu at a time, and each menu can be scheduled: always on, tied to shifts, or on a custom schedule with dates it is active from and until, days of the week and a daily time window. So next season's menu can be built in advance and set to start on its date, with the outgoing menu ending the day before, and last season's menu can be kept switched off and brought back next year rather than rebuilt. One dish can sit on several menus without being copied, which suits standing dishes that carry from season to season, and each menu can charge its own price for it.

Print designs warn when a dish has been added, removed, renamed or repriced since they were last printed, each published version is kept, and digital menu boards update themselves. Menu analytics show units, revenue and share of sales for every dish that sold over any dates, and, from the digital menu, how often guests looked at each dish against how often they ordered it, which is the starting point for reviewing a season. servearound does not hold recipes or recipe costs today, so recipe versions and costings stay in your own records; inventory tracking, for the stock behind the menu, is coming. See the menus module.

Four times a year is the classic rhythm. Many kitchens add one or two smaller swaps mid-season as particular ingredients peak or fade.

Around a third is a sustainable starting point, with the rest made up of standing dishes that stay or change only slightly.

Dishes that stay on the menu whatever the season: signatures, steady sellers and simple options that give regulars and the kitchen something reliable.

As its main ingredient's price falls towards the peak of its season, and retire it before supply fades and prices rise again.

Often, for the ingredients where freshness and story matter most. Keep a reliable wholesale option alongside it in case a local supplier cannot deliver.

A record of each dish as it was served each season, with its recipe, portion, plating, photograph and cost, so good dishes can return and changes are clear.

About eight weeks: decisions, supplier talks, testing and costing, a specials trial, menu updates and training, then the switch.

Run down stock used only by outgoing dishes, use leftovers as specials, and order cautiously for the first week of the new menu.

Look at how each new dish sold, what it cost, how hard it was for the kitchen and what guests said, and record the answers with the recipe versions.

A seasonal menu brings better ingredients, lower costs at the peak of each season and a reason for guests to return, but changing everything at once exhausts the kitchen. Keep a backbone of standing dishes and change around a third of the menu each season, spread across sections and stations, built on ingredients at their peak and used in more than one dish.

Cost new dishes on seasonal prices, keep recipe versions so good dishes can return, and follow a calendar: decide, source, test, cost, trial as specials, update every version of the menu and train before the switch. Then review each season against the last, so every seasonal menu is easier than the one before.