The best compliment a menu can get is not that it was fancy. It is when a guest takes a bite of something in June and says, without thinking, that it tastes like summer. That is the whole trick, and it is not really a trick. It is just cooking with what the ground is actually giving you that week, instead of ordering the same four proteins and three sides you would serve in any month of any year.
We are lucky here. The Bay Area sits in the middle of the most productive growing region in the country, and the seasons show up on the table in a way they do not in a lot of places. Karina builds menus off the calendar, not off a fixed list. Here is how to do the same, whether you are feeding twelve at a dinner party or two hundred at a wedding.
Why seasonal food actually tastes better, not just prettier
This is not a moral position about food miles, though that is real. It is about flavor and money. A tomato picked ripe in August thirty miles away and served two days later tastes like a different species than a tomato shipped green from Mexico in February and gassed to red in a warehouse. One is sweet and heavy with juice, the other is a pale sphere you salt to make edible. When you cook in season, the ingredient is doing the work, so your caterer can do less to it and it still lands. That is why a peak-season menu often costs less per plate for a better result. You are buying things at the bottom of their price curve instead of paying a premium to fly them in against the calendar.
The flip side is the mistake most people make: they pick the menu first, months out, then force the kitchen to source those exact items whenever the date lands. That is how you end up paying triple for asparagus at a November wedding, or serving strawberries in January that taste like wet cardboard. Pick the season first, then the dishes.
Build a seasonal menu in this order
- Start with your date and ask what is at its peak that exact month, not the whole season.
- Choose two or three hero ingredients you build dishes around, then fill in supporting players.
- Give the caterer the season and the feeling, then let them shop the market that week and adjust.
- Leave one or two dishes flexible so the kitchen can swap based on what actually looks good.
What is actually in season here, month by month
People say spring, summer, fall, winter, but the produce turns over faster than that. A menu built in early May is different from one built in late June. Here is the rough shape of the Bay Area growing year, which runs longer and gentler than most of the country because of our mild coast.
- Late winter (Jan to Feb): citrus at its absolute peak, blood oranges, Meyer lemons, mandarins, plus chicories, fennel, brassicas, and hardy greens. Dungeness crab season is on.
- Spring (Mar to May): asparagus, peas, fava beans, artichokes, green garlic, the first strawberries by late April, ramps and spring alliums.
- Early summer (Jun to Jul): stone fruit arrives, apricots then cherries then peaches, plus zucchini, the first tomatoes, corn, cucumbers, berries in full flood.
- Late summer (Aug to Sep): tomatoes and stone fruit at their peak, figs, melons, peppers, eggplant, sweet corn, the last of the berries.
- Fall (Oct to Nov): squash, apples, pears, persimmons, pomegranates, wild mushrooms after the first rains, late tomatoes, grapes during harvest.
- Winter (Dec): citrus returns, root vegetables, kale and hardy greens, pomegranate, and the start of crab season again.
Notice how short some windows are. Cherries are basically a three-week event. Fava beans and green garlic are gone almost before people notice them. If a guest's favorite is one of those, you either build around the date or you let it go. That honesty up front saves a lot of disappointment later.
How to brief your caterer so this actually happens
The single biggest reason menus end up generic is that the client hands over a fixed dish list and the caterer, wanting to make the client happy, sources it no matter the cost or quality. You have to give them room to cook. The strongest brief is short: here is the date, here is the feeling I want, here are two or three ingredients I love if they are good that week, and please shop the market and tell me what looks best. A caterer who is any good will light up at that, because it lets them do the thing they trained to do.
Ask for a tasting scheduled close enough to your date that the produce overlaps with what you will actually serve. A tasting in January for a September wedding tells you almost nothing about the tomatoes. If the timeline does not allow that, at least ask the caterer to build the tasting around the same category of ingredients you will have. And get the flexible dishes in writing as flexible, so nobody panics when the menu shifts a week out because the corn came in early. If you are still choosing between formats, our guide on how we work walks through where a planner sits between you and the kitchen.
Match the format to the season, not just the food
Seasonality is not only about which vegetable. It is about how food wants to be served in that weather. A July garden dinner in Sonoma wants cold, bright, hand-held things and a lot of ice, because nobody wants a heavy braise when it is 92 degrees at 6pm. A November harvest dinner wants the opposite, dishes that come out steaming in a pan and get passed around. Serving a cold composed plate at a cold-weather event, or a slow-cooked stew in a heat wave, fights the season even if every ingredient is technically correct.
Think about temperature of the food and temperature of the room together. Summer wants raw bar, crudités, chilled soups, grilled things, stone fruit and burrata, a lot of herbs. Winter wants roasts, braises, root vegetables, warm spice, citrus for brightness so it does not go heavy. Spring wants green and light, peas and asparagus and the first tender lettuces. Fall wants squash and mushroom and apple, food with a little weight. If you are weighing seated versus stations for the format itself, that is a separate decision from the season, but the two should agree with each other.
The Bay Area microclimate problem nobody warns you about
Here is a specific local trap. Our region is not one climate, it is a dozen stacked within an hour's drive, and that changes what your guests actually want to eat even in the same month. A June evening in San Francisco near the water can be foggy and 55 degrees while the same evening in Livermore or Napa is 85 and dry. If you book a summer menu of chilled soups and raw bar for a foggy waterfront venue in the city, your guests will be shivering over cold food.
So plan the menu for the actual site and its evening, not for the calendar month in the abstract. Coastal and city venues (Presidio, waterfront, anything near the Golden Gate) run cold at night even in July, so keep at least one warm element on the menu year round. Inland (Napa, Livermore, the East Bay hills, the South Bay) can be genuinely hot from June through September, so you want shade, cold food, and serious hydration. Ask your venue what the temperature actually does at your event's hour, not the daytime high. Our San Francisco venue notes and Napa venue notes get into which sites run warm or cold.
Seasonal drinks do more work than you think
People spend forever on the food menu and then default to a generic bar. But a drink is the fastest way to put the season in someone's hand the moment they walk in. In late summer that is a peach or a tomato in a glass, something with the fruit that is falling off the trees. In winter it is warm cider, a citrus-forward cocktail with blood orange, a spiced mulled option on a cold terrace. In spring, something green and herbal with cucumber or pea shoots. It costs almost nothing to make one signature drink track the season, and it is the first thing a guest tastes.
Do not forget the people not drinking. A seasonal mocktail should be as considered as the cocktail, made from the same fruit and syrups, not a sad cranberry-and-soda afterthought. If you want to go deeper on this, our piece on signature cocktails and mocktails covers how to build a pair that share ingredients so the bar stays simple.
Weaving in Chinese and Korean seasonal traditions
A lot of our clients are planning across two cultures, and the good news is that Chinese and Korean cooking are deeply seasonal to begin with, so this fits naturally. Mid-Autumn Festival in September is literally built around the harvest moon, so a fall event can lean into mooncakes, pomelo, and osmanthus without inventing anything. Lunar New Year in late winter overlaps beautifully with peak citrus, and the traditional whole fish, long noodles, and tangerines all carry meaning and happen to be in season.
Korean seasonal eating is its own quiet system. Namul (seasoned vegetable sides) change with what is fresh, spring greens in April, summer squash and cucumber later. A summer event can feature naengmyeon, the cold buckwheat noodle dish that exists precisely because it is what you crave in heat. Working these in is not a costume, it is cooking the way both cultures already cook. For a full treatment, see our Lunar New Year guide, which gets into the symbolic dishes and their timing.
Common mistakes that flatten a seasonal menu
Even people who mean well trip on the same few things. Here are the ones we see most.
- Locking the exact dish list too early. Commit to the season and the hero ingredients, keep the specific preparations loose until a month out.
- Confusing available with in season. You can buy strawberries in December. They will still taste like nothing. Available is not the same as good.
- Decorating seasonal and cooking generic. Autumn leaves on the table and grilled chicken breast on the plate is a mismatch guests feel even if they cannot name it.
- Ignoring the evening temperature. A cold coastal night needs a warm dish no matter what the calendar says it is summer.
- One-note seasonality. Squash in the soup, squash in the side, squash in the dessert. One clear hero, not the same thing four times.
- Forgetting dietary needs in the rush to be seasonal. Peak-season vegetables actually make this easier, lean into them so your vegetarian and vegan guests eat as well as everyone else.
A quick worked example
Say you are throwing a 40-person dinner in late September in Healdsburg, outdoors, starting at 5pm while it is still warm and cooling to pleasant by dark. Peak of the year up there: tomatoes and figs hanging on, grapes at harvest, the first squash, wild mushrooms if the rains have started. You might open with a raw bar and a tomato-and-fig salad while it is warm, move to family-style roasted chicken with grapes and a mushroom farro as the temperature drops, and close on a fig or a late-stone-fruit dessert. The drink walks the same line, a spritz with the last of summer's fruit early, something a touch warmer once the sun is down. Nothing on that menu was chosen from a template. It was chosen because that is what Sonoma County is growing that exact week, and the guests taste it.
Questions, answered
How far ahead should I lock my menu? Lock the season, the format, and your two or three hero ingredients as early as you like. Leave the exact preparations flexible until roughly four to six weeks out, when your caterer can see what the market is actually doing. That balance protects both your planning and the quality.
Is seasonal food more expensive? Usually the opposite. Peak-season produce is at the bottom of its price curve and needs less doctoring to taste great, so you often pay less per plate for a better result. The expensive path is forcing out-of-season ingredients against the calendar.
What if a guest requests a specific out-of-season dish? Be honest early. If their must-have is a three-week ingredient like cherries and your date misses it, tell them and offer the in-season equivalent that will actually taste good. Most people would rather have a great peach than a mediocre cherry, they just need someone to say so.
Planning Something?
Let's make it one of a kind.
Tell us what you're celebrating and we'll bring the plan to you, anywhere from Monterey to Sacramento.
Start your inquiry