Seasonal menus are talked about as a philosophy and run as a logistics problem. The philosophy is easy to agree with. The logistics are where most attempts fail — usually in the third week, when the ingredient the whole dish was built around triples in price or simply stops arriving.
This is about the second part: how to structure a restaurant menu so the season shows up on the plate without the kitchen rebuilding itself four times a year.
Menu architecture first
Before the dishes, decide the shape. A workable structure for most Australian mid-size restaurants:
- Antipasti / entrées: 5–6
- Pasta or middle course: 4–5
- Mains: 4–5
- Sides: 3–4
- Dolci: 3–4
Roughly twenty dishes. Within that, split each section into two groups: fixed and seasonal.
The fixed dishes — around two-thirds — are what the venue is known for. They stay year-round, they are what regulars return for, and they are fully costed and drilled. The seasonal third moves with produce.
This structure is the whole trick. It gives you genuine seasonality and a stable core, so a bad month for one crop does not compromise the entire menu. A fully seasonal menu sounds better and is a considerably harder business to run.
Build seasonal dishes around a technique, not an ingredient
The failure mode of seasonal cooking is designing a dish that only exists because of one item. When that item goes, the dish goes, and you have an empty slot and no lead time.
The alternative is to design around a technique and a shape, then let the season fill it.
A dish specified as "seasonal vegetable, charred, agrodolce, toasted almond, ricotta salata" runs on zucchini in January, on eggplant in March, on cauliflower in July and on artichoke in September. The prep is identical. The costing barely moves. The section already knows how to make it. What changes is the produce, which is exactly what should change.
Written that way, a seasonal menu becomes four or five slots that rotate, rather than four or five new dishes a quarter.
The Australian calendar
Roughly, for the south-east:
- Summer (Dec–Feb): tomatoes at their only genuinely good point, stone fruit, zucchini and their flowers, basil, capsicum, figs from late summer.
- Autumn (Mar–May): eggplant, mushrooms, pears, late tomatoes, chestnuts, the start of brassicas. The strongest produce season in the country and the most underused.
- Winter (Jun–Aug): brassicas, root vegetables, radicchio and bitter leaves, citrus at its peak, WA black truffle from roughly June to August.
- Spring (Sep–Nov): artichokes, broad beans, peas, asparagus, new-season lamb, the first strawberries.
Two practical notes. Australian winter citrus is world-class and consistently underused on savoury menus — a blood orange and fennel salad in July costs very little and tastes like the season. And a tomato dish in August is a decision to serve a bad tomato; there is no technique that rescues it.
Write the menu for a reader, not a chef
Seasonal menus attract a particular kind of over-writing — every dish listing seven components, three of which are garnishes.
A description should tell the customer what the dish is, in the order they will taste it, and stop. Name the thing that justifies the price — the producer, the region, the cut — and leave out anything they would assume anyway. Nobody needs to be told there is olive oil.
Compare: "Charred zucchini, almond, ricotta salata, mint" against "Locally sourced seasonal zucchini, chargrilled over coals, finished with toasted almond, aged ricotta salata, torn mint, extra virgin olive oil and aged balsamic." The first is a dish. The second is an inventory.
Changeover mechanics
Where seasonal menus break is the transition, not the menu.
- Cost the new dish before it goes on, not after. Obvious, routinely skipped under time pressure, and the source of most seasonal margin damage.
- Run it as a special for two weeks first. You learn the real prep time, the real yield and whether it sells, before it is printed.
- Change one section at a time. Rolling changes are absorbed by a kitchen. A full menu changeover on a Tuesday is a bad week.
- Run down the outgoing ingredient deliberately. Order for the changeover date, not the changeover week, or the saving from seasonality goes in the bin.
- Retrain on the changeover. A new dish explained verbally at handover is a new dish executed four different ways by Saturday.
A test worth applying
Before a dish goes on the menu, three questions:
- Can the section make it correctly at eight o'clock on the busiest night of the week?
- Does it use ingredients that at least one other dish uses?
- Can you explain in one sentence why it is on the menu now and not in three months?
If the answer to the third is only "it's seasonal", the dish is a gesture rather than an idea. Seasonality is a means to better cooking, not a claim to be made on a menu.
Common questions
How many dishes should a restaurant menu have?
Around twenty across all sections works for most mid-size Australian restaurants — roughly five to six entrées, four to five pastas or middle courses, four to five mains, three to four sides and three to four desserts. Keep about two-thirds fixed year-round and rotate the remaining third seasonally.
How often should a restaurant change its menu?
Rotate the seasonal third quarterly, and change one section at a time rather than the whole menu at once. A full changeover in a single service is a bad week for the kitchen and usually for the margins.
How do you stop a seasonal menu from breaking when an ingredient runs out?
Design the dish around a technique and a shape rather than a single ingredient. A slot specified as 'seasonal vegetable, charred, agrodolce, almond, ricotta salata' runs on zucchini, eggplant, cauliflower or artichoke depending on the month — same prep, same costing, same training.