Daypart menus: breakfast, lunch and the gap between

A venue that opens from breakfast to dinner serves several different businesses in one day. At eight in the morning, guests want coffee and eggs, fast. At one o'clock, they want lunch they can finish within the hour. At four, the room is quiet and the few guests want cake or a glass of wine. At eight in the evening, they want a full dinner and a reason to stay.

Daypart menus are how a venue serves each of those businesses well: a different menu for each part of the day, shaped to what guests want then. Done well, they fill more hours of the day and use the kitchen efficiently. Done badly, they multiply stock, prep and confusion until the kitchen is running three restaurants at once.

This guide covers how to run several daypart menus from one kitchen, the overlap worth keeping between them, how to handle the set lunch and the brunch menu, and how the quiet hours between can earn their keep. Every figure in it is an example.

A daypart is a part of the trading day with its own pattern of guests: breakfast, brunch, lunch, afternoon, dinner and, in some venues, late night. A daypart menu is a menu designed for one of them.

Some venues run a single all-day menu, with every dish available whenever the kitchen is open. Others run entirely separate menus for each daypart. Most land in between: a core of dishes available all day, with each daypart adding its own dishes and dropping others.

The right approach depends on the venue's hours, its guests and its kitchen. A café open from seven until four may need breakfast and lunch only. A brasserie open from eight until eleven at night may need four. The principle is the same: each part of the day should have a menu that suits the guests who come then.

Guests want different things at different times. Breakfast guests are often in a hurry and value speed and familiarity. Lunch guests have a fixed amount of time and want to know they can eat within it. Dinner guests have the evening and want choice, atmosphere and a sense of occasion.

One menu rarely serves all of them well. A dinner menu at breakfast is too heavy and too slow; a breakfast menu at dinner is too limited. A lunch menu priced and paced for a quick meal leaves money on the table at dinner, when guests would happily spend more.

Daypart menus also let the kitchen plan. Each menu can be built around what the kitchen can produce at that time, with the staff on shift then, so the morning team is not trying to produce dinner dishes and the evening team is not caught with breakfast stock.

Every extra menu brings costs. More dishes mean more ingredients, and more ingredients mean more stock, more waste and more prep. More menus mean more for the team to learn: every cook must know the dishes of every daypart they work, and every server must be able to describe them.

There are also costs at the changeover. When one menu ends and another begins, the kitchen has to switch stations, prep and plating, and guests who arrive near the change need clear answers about what is available.

These costs are real, and they are why daypart menus need discipline. The aim is not as many menus as possible, but as few as needed to serve each part of the day well, sharing as much as they sensibly can.

The key to running several menus from one kitchen is shared preparation. Each menu should draw on the same core ingredients and components wherever possible, so the kitchen preps once for several dishes across the day.

A roast chicken prepared in the morning can appear in a lunch sandwich, a salad and a dinner main. A tomato sauce can serve a breakfast dish of baked eggs, a lunch pasta and a dinner side. Bread baked or bought for breakfast toast can carry lunch sandwiches. Each shared component reduces stock and prep and makes the menus feel connected.

Map the components before writing the menus. List the main ingredients and prepared components each daypart needs, and look for overlaps. Where a dish needs something no other dish uses, ask whether it earns its place.

Some dishes are worth having on more than one menu. A signature dish that guests associate with the venue might run all day. A popular salad might appear at lunch and dinner. A dessert might run from lunch onwards.

Overlap helps guests as well as the kitchen. A regular who loves a particular dish can have it whenever they come. A guest arriving at the edge of a daypart finds familiar dishes on either side of the change.

But too much overlap blurs the menus. If the lunch and dinner menus are nearly identical, the dinner menu loses its sense of occasion and lunch loses its speed. Keep a core of shared dishes, and let each daypart have dishes of its own that suit it.

Breakfast is the daypart where speed matters most. Many guests are on their way somewhere, and a breakfast that takes twenty-five minutes to arrive is a breakfast they will not order again.

So build the breakfast menu around dishes the kitchen can produce quickly and consistently: eggs in a few styles, a handful of hot dishes, pastries, granola or porridge, and good coffee. Keep the menu short enough that the morning team knows every dish by heart.

Prepare as much as possible before the doors open: portioned ingredients, sauces made, garnishes ready. A breakfast menu should be cooked and plated in minutes, and that only happens when the preparation is done before the first order arrives.

Brunch is a different daypart from breakfast, even when it overlaps the same hours. It is usually a weekend business: guests arrive later, stay longer, order more and often come in groups. The idea of brunch has long been a late, leisurely meal rather than a quick one.

A brunch menu can be more generous than a weekday breakfast: larger dishes, more choice, some lunch-style options and brunch drinks. But it often arrives all at once, with a queue at the door at eleven and tables of six ordering together, which can overwhelm a kitchen built for a steady breakfast.

Plan the brunch menu for the rush. Keep dishes that can be produced quickly in volume, limit dishes that tie up a single station, and stagger seating if the kitchen needs it. A brunch menu that looks wonderful and takes forty minutes to arrive will lose the queue.

At lunch, the guest's main constraint is time. Many lunch guests have an hour or less, and they choose a venue partly on whether they can trust it to serve them within that time.

Build the lunch menu around dishes that can be cooked and served quickly: salads, sandwiches, bowls, quick mains, a soup. Make the timing visible where it helps, for example by telling guests that a particular dish takes longer, or by offering an express option.

Lunch menus can also be priced differently from dinner, with smaller portions and lower prices that suit a working day. That is not a discount on dinner; it is a different meal for a different guest.

A set lunch, a fixed price for two or three courses, is one of the most effective tools for filling the middle of the day. It gives guests a clear price, a quick decision and confidence that they can eat within their time, and it gives the kitchen a short list of dishes to produce in volume.

Keep the set lunch simple: two or three choices for each course, built from ingredients already used elsewhere on the menu, priced to offer clear value while still earning a fair margin. Change it weekly or with the seasons, so regulars have something new.

A set lunch can also fill a quiet day. A venue whose Tuesday lunch is slow can use a well-priced set lunch to bring in local workers who might otherwise eat at their desks. Our guide to quiet-night trade and filling Monday honestly covers the same thinking for slow evenings.

The hours between lunch and dinner are the hardest to fill. In many venues, the room empties at half past two and stays quiet until six. The kitchen is often restocking for dinner, and the few guests who come in want something light.

There are several ways to make those hours pay. A short all-day menu of small plates, salads and sandwiches can serve the few guests who come without tying up the kitchen. Coffee and cake, or a glass of wine and something to share, suit the guests who want to linger. Some venues close the kitchen and serve only cold dishes, freeing the cooks for dinner prep.

The test is simple: do the afternoon hours earn more than they cost? A quiet afternoon with a full kitchen team waiting for orders loses money. One with a short menu that the dinner team can serve while they prep may earn a modest but useful sum.

Dinner is usually the daypart where guests spend most and stay longest, and the menu can be at its fullest. Guests expect more choice, more elaborate dishes and the full experience of the venue.

Even so, the dinner menu benefits from discipline. It should share components with the other menus wherever that makes sense, so the kitchen is not preparing an entirely separate set of ingredients for the evening. And it should be sized to what the evening kitchen can produce well at the peak. Our guide to menu size, and why thirty dishes is usually too many covers how to find that number.

Dinner is also where the overlap with lunch matters most. Guests who have had a dish at lunch may come back for it at dinner, and a dinner menu that keeps the venue's best-known dishes alongside its evening specials serves both.

The moment one menu ends and the next begins needs planning. The kitchen has to change stations, put away one set of components and bring out another, and guests who arrive near the change need to know what they can order.

Set clear changeover times and stick to them: breakfast until half past eleven, lunch from twelve, for example. Leave a short gap if the kitchen needs it, and make sure guests arriving in the gap are told what is available. A guest who orders a breakfast dish at eleven thirty-five and is told it has just finished, with nothing offered instead, feels turned away.

Make the change visible everywhere. The printed menu, the menu on the table and the menu guests open on their phones should all show the current daypart, so nobody orders a dish that is no longer being served.

Pricing the same dish differently at different times needs care. A dish that costs more at dinner than at lunch can feel unfair if it is exactly the same dish. Guests notice, especially regulars who come at both times.

The usual answer is to make the dishes genuinely different: a smaller lunch portion at a lower price, or a dinner version with an extra component. Then the price difference reflects a difference on the plate, and guests can see why.

Where a dish is truly the same at both times, it is often simpler to keep the same price. The dayparts can still differ in price through their mix: a lunch menu built around lighter, cheaper dishes and a dinner menu with more substantial ones.

The menu mix, the share of sales each dish takes, should be read separately for each daypart. A dish that sells strongly at lunch may barely sell at dinner, and a dish that does well in the evening may never be ordered at breakfast. Reading the mix for the whole day blurs those patterns.

Look at each daypart's mix over a few weeks. Which dishes carry each menu? Which shared dishes earn their place on more than one menu, and which sell in only one? Which dishes in each daypart rarely sell? Our guide to menu mix: what your guests order, not what you sell covers how to read it.

Use the answers to shape each menu. A shared dish that sells only at dinner can come off the lunch menu, simplifying it. A lunch dish that guests keep asking for in the evening may deserve a place on the dinner menu.

Guests should never have to guess which menu is being served. Show the current menu on the website, on the menu guests open from a QR code and on any boards, and make the dayparts and their times clear.

Online, this matters a great deal. A guest who looks at the website at six in the evening and sees the breakfast menu may assume the venue is a café and go elsewhere. A website that shows every daypart, with its hours, lets guests plan.

At the door, the team should be able to tell guests what is available now and when the next menu starts. "We're serving lunch until three, and dinner starts at six, but we have small plates in between" is a far better answer than "the kitchen's closed".

With several menus, updating the menu becomes more complex. A price change on a shared dish has to reach every menu it appears on. A dish taken off at lunch but kept at dinner has to be removed from one menu and not the other. A seasonal change may affect every daypart at once.

Keep shared dishes as one dish in your records, not several copies, so that a change to its description, photo or price reaches every menu that carries it. Our guide to updating the menu in one place, not five covers why that matters.

Plan seasonal changes across all dayparts together. A new seasonal ingredient might appear at breakfast, lunch and dinner in different dishes, and introducing them together keeps the prep coherent.

An invented all-day café in a city centre opens from half past seven until ten. It runs a single menu of thirty dishes all day, so the kitchen holds stock for everything from pancakes to steak at every hour. Breakfast is slow because the morning team works across the whole menu, and the afternoon is almost empty.

The café moves to four daypart menus. Breakfast, until half past eleven, offers ten quick dishes. Lunch, from twelve until three, offers twelve dishes and a two-course set lunch. The afternoon, from three until half past five, offers six small plates and cakes that the dinner team can serve while they prep. Dinner offers sixteen dishes, six of them shared with lunch.

The kitchen maps shared components across the menus, cutting its ingredient list by a quarter. Breakfast tickets get faster, the set lunch brings in office workers on quiet weekdays, and the afternoon covers its costs for the first time.

In servearound, each menu can run on a schedule: tied to shifts, such as breakfast, lunch and dinner, or on a custom schedule of days of the week and a daily time window, even one that runs past midnight, with dates it is active from and until. Only one menu runs at a time, so daypart menus each get their own hours, and menu groups apply one schedule to several menus at once. The menu guests open from a table's QR code and the venue's menu page show the menu that is running, and a digital menu board set to the live menu follows it through the day.

One dish can sit on several menus without being copied, so a dish shared between lunch and dinner is edited once, and each menu can charge its own price for it. A set lunch can be built as a bundle with its courses, a fixed price and an availability window. The menu report can be read for any range of dates and for one menu or all of them. See the menus module.

Menus designed for different parts of the trading day, such as breakfast, lunch, afternoon and dinner, each shaped to the guests who come then.

It depends on your hours and guests. Most venues do best with a core of shared dishes and each daypart adding a few dishes of its own.

Share ingredients and prepared components across the menus, so the kitchen preps once for several dishes, and size each menu to the team on shift.

A short choice for each course, built from ingredients already on the menu, at a clear price that offers value and still earns a fair margin.

Brunch is usually a weekend business with later, longer, larger meals and a rush of groups, so it must be built for volume at the peak.

Offer a short menu of small plates, salads or cakes that the team can serve while preparing for dinner, and check that the hours cover their costs.

Only if the dish is genuinely different, such as a larger portion or an extra component. Otherwise the difference can feel unfair to regulars.

Separately for each daypart, so you can see which dishes carry each menu and which shared dishes earn their place on more than one.

Keep shared dishes as single records that appear on several menus, and plan seasonal changes across every daypart together.

Daypart menus let one venue serve the different guests who come at breakfast, brunch, lunch, the quiet afternoon and dinner, each with a menu that suits them. Run them from one kitchen by sharing ingredients and components across the menus, keep a core of dishes that appear in more than one daypart, and give each part of the day dishes of its own.

Build breakfast for speed, brunch for the weekend rush, lunch and the set lunch for guests short of time, the afternoon for the few who linger, and dinner for the full experience. Set clear changeover times, show the current menu everywhere guests look, read the menu mix daypart by daypart, and keep shared dishes as single records so updating the menu stays simple.