How to run a ticketed brunch experience

A ticketed brunch works when guests know exactly what they've bought and your team can serve it within the time you've sold. Start with one sitting, a tightly defined menu and a reason to book beyond getting a table. Add another sitting only after you've tested the kitchen, the room reset and the money it leaves you.

It's tempting to start with the fun part. You've found a chef, the venue looks good in daylight, and you can already picture the announcement. Then someone asks whether coffee is included. Another person wants to bring five friends. The chef wants a final headcount before your planned ticket deadline. Suddenly you're running several different versions of the brunch in people's heads.

You can prevent most of that confusion before launch. This guide walks through the offer, the sitting times, the menu and dietary process, then a worked budget and the decisions you'll make during service. The aim is a paid experience people would book again, with enough money left to make repeating it worthwhile.

Decide why someone should buy this brunch

The first thing you want to do is explain why this needs a ticket. An ordinary restaurant already offers food, seats and a weekend outing. Your brunch needs a clear reason for someone to commit to a date and pay before arriving. That could be a chef cooking a specific regional menu, a food producer hosting a tasting, or a short performance built around a shared meal.

Choose one reason and develop it properly. A three-course seasonal brunch with the chef introducing each course is understandable. A brunch with unlimited activities, several performers and an enormous menu is much harder to explain or deliver. Every extra also competes for the same guest time and staff attention. If the meal is the attraction, let people enjoy eating it.

Write the promise as a sentence you could say to a prospective buyer. For example, you're offering a hosted seasonal brunch, with shared tables, a set menu and one included hot drink, between 10:00 and noon. The details are illustrative, but notice how many decisions that sentence settles. It tells the kitchen what to prepare and gives guests a useful picture of the visit.

Next, decide who would value that promise. Local food enthusiasts may book for the chef. Friends may want an easy way to organise a weekend together. Solo diners may be interested in a hosted communal table, provided you describe it honestly. You don't need to serve all of them equally. Pick the audience whose expectations you can meet at a price that supports the event.

If the wider restaurant setup is still unresolved, read our paid pop-up restaurant guide first. This article assumes you're building a brunch that depends on a particular arrival time, meal format and finish. Those constraints affect nearly every choice that follows, especially when you want to use the room again later that day.

Write the inclusions before you choose the headline

List everything the ticket includes in ordinary language. Name the meal format, number of courses if relevant, included drinks, seating arrangement and hosted element. Explain whether water, coffee refills, service charges or other costs need separate payment. Use the actual total and the rules that apply where you sell, rather than making buyers reconstruct the bill from small print.

Words such as generous, premium and indulgent don't settle those questions. A guest can reasonably read unlimited coffee into one description while your team has budgeted one drink. If you offer a choice of main course, say when the choice is made. If dishes are shared, say so. People planning a celebration or arriving alone may care about that more than the photography.

Be especially careful with bottomless language. It creates expectations about quantity, duration and service speed, and alcohol brings separate obligations. For a first event, I'd usually choose a finite package you can cost and fulfil. You can make it feel generous through the quality of the food and hosting without selling an open-ended promise. If you do offer refills, define the arrangement and check it with the responsible operator.

Decide what happens when something sells out or becomes unavailable. A seasonal menu can allow named types of substitution, but that flexibility doesn't justify replacing the central attraction without telling buyers. A small garnish change and removing the advertised chef are very different changes. Write the response while you can think calmly, including how you will contact affected guests and assess an appropriate remedy.

Survey evidence offers some context for why clear descriptions matter. Loopyah's Worth It Event Index, fielded through Pollfish among 500 US consumers in February 2026, asked how clear people usually felt about an event before buying. The chart reports their answers. It covers events generally, not brunch buyers, and doesn't prove that clearer copy increases sales.

Use that as a reason to check your own page, not as a prediction. Ask someone unfamiliar with the brunch to explain what they'd receive, when they'd arrive and what else they might spend. Their questions reveal missing information you can fix before paying for promotion.

Start with one sitting and rehearse its busiest moment

A sitting is the period a particular group has booked to eat. Its end needs to mean the same thing to guests, servers and the kitchen. If the ticket says 10:00 to noon, don't privately assume everyone will leave at 11:40 so you can clean. Build the reset after the guest period, then test whether the next arrival time is realistic.

For a first brunch, one sitting removes a lot of uncertainty. You can watch how arrivals cluster, whether coffee delays the opening and how long people take over the final course. A room that looks settled halfway through service tells you little about the effort required to empty and reset it. You need to see the end before promising to repeat the beginning.

Rehearse the difficult part with the actual equipment and people. If your main course needs several dishes to arrive together, prepare and deliver a realistic group of orders. Include dietary adaptations, clearing, washing and drink orders. Cooking one excellent plate doesn't establish how a full room will eat. Change the menu or service method when the test exposes a delay.

Work backwards from the guest finish. Leave time for the final course, last drinks, coats, payment for extras and anyone who needs assistance leaving. A friendly reminder is easier when the finish was clear at booking. It feels much less friendly when someone first learns about it while they're halfway through their coffee. Brief hosts to explain the timing without making guests feel chased out.

Here's a fictional running order, not a recommended service standard. Guests arrive from 09:45, the booked sitting begins at 10:00 and the host welcomes them at 10:10. The first course follows at 10:15, the main course at 10:40 and the final course at 11:20. At 11:45 the host reminds guests about the noon finish. The room is then unavailable to new guests until the reset is complete.

If you later add a 12:45 sitting, the 45 minutes after noon belong to clearing, cleaning, restocking, resetting and checking the room. They aren't spare minutes for overselling the first sitting. Staff still need suitable breaks and the kitchen may need its own recovery period. Confirm both, rather than treating a single gap on the public timetable as proof that everyone is ready.

Set capacity from the service you can actually deliver

The number of chairs is only one limit. You also need a suitable layout, the relevant permitted occupancy, accessible movement and a kitchen that can serve the menu. Use the lowest workable limit and have the appropriate people assess it. A ticket quantity should follow that decision. It shouldn't become the reason the team squeezes another table beside an exit.

Look at capacity in groups as well as individual seats. A room may have four spare seats that cannot accommodate one party of four together. Decide whether you're selling individual places at shared tables, whole tables, or a mix. Make that arrangement visible before purchase. Don't promise private tables while budgeting for every chair to sell independently.

If you sell whole tables, keep their seat count in the same capacity calculation as individual tickets. A table for four consumes four places, even if one person makes the payment. Likewise, a complimentary guest still needs a meal and a seat. Keep any held places inside the total rather than adding them after the public allocation sells out.

Group bookings need a contact route that doesn't turn into an informal second inventory. You can ask people to send their order references and seating request by a stated deadline, then confirm what you can accommodate. A request isn't a guarantee until you've checked it. Avoid holding unrecorded tables through social messages while the same places remain available to buy online.

Set a rule for arrivals with a different party size. If three people arrive using a booking for four, that doesn't automatically create a safe extra ticket to sell. You may already have prepared the fourth meal or promised the seat to a late guest. Check the booking and your transfer terms before making a change. A quiet chair is still part of an existing purchase.

There is also a service reason to avoid selling every possible place immediately. You may need an arrangement that supports access requirements or a way to keep a group together. Plan that with the venue before launch and explain how people can contact you. Any reserved capacity has a cost, so include it honestly when deciding whether the event can support its price.

Choose a menu that survives a full room

A good brunch menu gives the kitchen manageable work when guests want food at the same time. Start with the core dish and map the equipment it needs. If nearly everything requires the same cooking surface or the same last-minute finish, the queue exists before guests arrive. You can change a dish much more easily now than during the first sitting.

Ask the chef to define portions, ingredients, preparation steps and how the dish reaches the table. Include drinks in this exercise. One coffee machine can become the slowest part of a meal even when the kitchen is comfortable. A menu promise that includes a drink still needs the labour, equipment and service route to deliver it without delaying everything else.

For an initial event, a short set menu or a limited advance choice is often easier to manage than ordering freely on arrival. It lets the kitchen purchase against actual selections and organise preparation. But don't make every dietary request a new ticket type. Keep the public buying decision understandable, then use a clear, confirmed process for the information the chef needs.

Give the kitchen one final version of the menu counts. Suppose, in a fictional 40-person sitting, 28 guests have selected one main and 12 another. Those are guest meal counts, including complimentary guests. Record staff meals separately and tell the kitchen whether they need to be ready during the same service. Otherwise a total can look correct while the wrong people are included.

Ask about purchasing units and minimum charges. The cost of a dish isn't simply the quantity on one plate multiplied by attendance. You may have to buy a whole pack, pay for delivery or commit to a minimum catering order. Establish what can be changed before a cutoff and what becomes payable afterwards. That distinction matters when sales are lower than expected.

Buffets and shared platters need their own assessment. They change portion control, replenishment, guest movement and the handling of dietary questions. They aren't automatically cheaper because fewer plates leave the kitchen. Have the food operator plan the safe service method, then cost the labour and equipment it actually requires. Choose the format because it fits the meal, rather than because it sounds relaxed.

Confirm dietary requests through a named food lead

Make it easy for someone to ask about the menu before buying. A short contact instruction is more useful than a vague promise that all requirements can be accommodated. Explain the options you've confirmed with the kitchen and the process for questions. If the team can't safely provide a requested meal, resolve that before taking payment wherever possible.

The Food Standards Agency's best practice for non-prepacked allergen information, applying to England, Northern Ireland and Wales, recommends written information supported by a conversation. It also addresses advance orders and passing requests to the people preparing and serving food. Check the current requirements for your location and operation with the relevant authority.

For the brunch, appoint the person who can assess and confirm a request. The event host can collect an enquiry, but shouldn't invent an answer because the chef is busy. Agree how the food lead responds and how the confirmed arrangement reaches service staff. A message marked received is different from a kitchen confirming it can fulfil the request.

Use a small record with the booking reference, sitting, guest identification, request, confirmed arrangement and responsible person's acknowledgement. Limit access to the people who need it and follow the privacy requirements that apply. You don't need a medical history in a public guest list. You do need the server to identify the correct guest without broadcasting their personal information across a shared table.

Explain what happens when ingredients change. The food lead should reassess affected meals and update the relevant information before service. Don't let a supplier substitution remain only in a delivery conversation. The public menu, the preparation record and the person answering guest questions need to describe what is actually being served that day.

Keep dietary descriptions precise. GOV.UK's allergen labelling guidance explains that vegan labelling doesn't guarantee the absence of particular allergens. A vegan option and a meal suitable for a specific allergy answer different questions. Avoid treating either as a general assurance that every guest can eat it.

Set an advance request deadline to help purchasing, then retain a calm process for late questions. A deadline cannot make a food safety question disappear. Brief staff to pause, consult the food lead and explain the available information. They should never guess, quietly remove a garnish or assume another guest's apparently similar request supplies the answer.

Agree who runs the food business and the venue

Before launching, settle the operating arrangement in writing. Is your business selling the full brunch while a caterer supplies the food, or is the restaurant selling a meal alongside your separately ticketed activity? Who employs the service team, controls the kitchen, handles complaints and pays suppliers? Ask the relevant authorities and advisers how the actual arrangement affects your responsibilities.

For an England, Wales and Northern Ireland example, GOV.UK's food business registration guidance covers activities including selling, preparing and distributing food and explains registration. Speak to the local authority early about your particular setup, including temporary or host premises. An existing restaurant's involvement doesn't settle every obligation your own business may have.

Alcohol requires a separate conversation. In England and Wales, the Temporary Events Notice guidance describes one route for qualifying licensable activities on unlicensed premises or beyond existing permissions. Check the proposed package with the licensing authority. A drink bundled into a ticket shouldn't be treated as automatically outside the rules because there is no separate bar payment.

For food safety procedures in England and Wales, the Food Standards Agency's Safer food, better business packs provide practical material for small food businesses, including caterers. Have the responsible food operator choose and apply a suitable system. Your event schedule needs to allow their procedures to work during preparation, service and reset.

The venue agreement should include access for deliveries, preparation and cleanup, not just the public hours. Confirm equipment, breakages, linen, cleaning, waste collection and the room's condition at handback. If another business needs the kitchen afterwards, record the handover time. A second sitting may be impossible even when the guest room is available.

Give someone authority to pause admissions or service when the room isn't ready. Include the venue's emergency arrangements in the briefing and check staff know how to get help. The Health and Safety Executive's catering risk guidance, for Great Britain, covers issues such as slips, trips and knives. Assess the real operation with competent people rather than relying on the relaxed atmosphere guests will see.

Work out what one sitting has to earn

Now put the offer into a budget. Use actual quotes and include paid preparation, cooking, service, hosting, cleanup and your own work. Separate costs payable regardless of attendance from costs that genuinely change with meals. Then identify any minimum catering charge or purchasing cutoff that makes a supposedly variable cost fixed before the event.

Here's a fictional example in USD to show the decisions. It is not a price recommendation, staffing standard or forecast. Assume an approved 40-place sitting. Fixed costs are $300 for venue access, $420 for kitchen labour, $240 for service staff, $120 for your planning and hosting, $120 for promotion and $80 for hire and cleanup. That totals $1,280. Each meal adds $18 in food and consumables.

Assume each paid ticket leaves $58 after transaction costs and any sales tax included in the selling price. This is a chosen calculation amount, not a Loopyah fee or tax quote. Every paid meal therefore leaves $40 towards the fixed costs. Dividing $1,280 by $40 gives 32 paid guests to break even, provided meal costs still change with attendance as assumed.

At 40 paid guests, retained receipts are $2,320. Meals cost $720 and fixed costs are $1,280, leaving $320 before business taxes and any costs omitted from this simplified example. At 36 paid guests, the same model leaves $160. At 30, it loses $80. The room can look respectable while the event still fails to cover the work you've agreed to pay for.

Complimentary guests change the calculation. If 36 people pay and four attend free, you receive $2,088 but still provide 40 meals costing $720. After $1,280 fixed costs, $88 remains. That's different from 36 paid guests eating only 36 meals. Record the meal and seat cost of each invitation before a partner promises a table to their friends.

Purchasing commitments change it too. If all 40 meals become payable at the supplier cutoff, meals cost $720 even when you later sell only 30 tickets. Retained receipts of $1,740 then leave a $260 loss after the fixed costs. Your sales decision needs to happen before that commitment, using the terms already given to buyers. Our event break-even guide explains how to build the fuller calculation.

Test whether a second sitting improves the result

A second sitting brings more available tickets, but it also creates another service. You may need longer venue access, more kitchen and floor hours, another cleaning period and additional stock. Ask for the actual incremental costs, meaning the costs you incur because you add it. Don't simply double revenue while keeping the morning's staff bill unchanged.

Continue the fictional example. Assume the first sitting goes ahead independently. Adding the second costs another $500 in fixed labour, access and reset expenses, plus $18 for each additional meal. Each extra paid ticket still leaves $58 before the meal cost, so contributes $40. With meal costs genuinely flexible, 13 paid guests contribute $520 and leave $20 after the additional $500.

That is a mathematical threshold, not a sensible automatic launch target. At 20 paid guests, the additional sitting leaves $300. At 40, it leaves $1,100. Both assume the same offer can be delivered at the stated costs, with no effect on the first sitting. If extending the day adds another charge, or rushing the reset damages the first meal, revisit the whole decision.

Now suppose the caterer requires payment for at least 20 second-sitting meals. At 13 paid guests, receipts are $754, the minimum meals cost $360 and additional fixed costs are $500. The second sitting loses $106. With that minimum, 15 paid guests leave $10 because $870 minus $360 minus $500 equals $10. Beyond 20 meals, use the actual additional meal cost again.

You also need evidence that those extra buyers exist. Ask interested people which time they would buy, or use a clearly described interest form before committing. Expressions of interest aren't paid bookings. If you plan a conditional launch, set its terms and refund process appropriately before taking money. Don't count the same interested group as demand for both sittings.

Keep the customer experience in the decision. A second sitting that only works by shortening the advertised meal or making staff work without suitable breaks needs a different plan. You could raise the price, simplify the menu, change the access agreement or keep one sitting. I would choose one well-delivered sitting over two that depend on everything running perfectly.

Check what else the longer day prevents you from doing. If the venue could otherwise run its normal lunch service, its extra charge may reflect the business it gives up. If you're the venue operator, compare the brunch with the income and costs of that alternative. A positive second-sitting result doesn't automatically make it the best use of the room. Use evidence from your own trading records rather than assigning an invented value to every empty hour.

Put the commercial agreement through the same test. If the chef receives a percentage, define whether it's based on ticket receipts before or after refunds, tax and fees. If the venue keeps extra drink sales, leave them out of your revenue. If you receive a share, confirm the reporting and settlement date. You want both parties to calculate the same amount without reopening the negotiation after service.

Build a ticket page that answers group questions

Put the exact sitting time beside the ticket choice. Buyers should know which session they are selecting before they reach payment. Use plain labels, such as first sitting, 10:00 to noon. If you have different packages, explain their differences without implying they include more time or private seating unless they do. A higher price is still a promise you have to deliver.

With Loopyah ticket selling, buyers can choose ticket types and quantities, pay, and receive a confirmation email linking to their QR tickets. That gives the brunch a clear paid booking route. Your team still needs to define the sittings, the menu and how seating requests are confirmed. A ticket purchase should not be described as automatically confirming an unassessed dietary adaptation or table arrangement.

Keep the essential information near the buying decision. State the venue entrance, guest period, inclusions, seating format, dietary contact and cancellation or transfer terms. If extra drinks are sold separately, explain how guests order and pay. If children can attend, define their booking arrangement and meal clearly. Otherwise say who the event is designed for without leaving families to guess.

Explain how friends book together. For individual shared-table places, you might ask the lead guest to buy the whole group in one order or send linked order references by the seating deadline. Confirm the arrangement you can support. Don't ask people to buy unrelated tickets and rely on a public comment saying that you'll sort it out later.

Write a short example description before designing the page. A usable version might say that the ticket includes a three-course set brunch, one hot drink and a hosted chef introduction, with communal seating. Then state the sitting's start and finish, how to view the menu and how to ask questions before purchase. Substitute your real details; the structure makes the offer understandable without dressing it up.

Check the confirmation as well as the page. Someone may forward the ticket to another guest who hasn't seen your announcement. The arrival instructions should make sense independently. If a test purchase is supported, use it and check the complete experience on a phone. Find out now whether a buyer can easily distinguish the two sittings and locate the dietary contact.

Sell against a purchasing deadline

Choose the date on which paid bookings must justify the next non-refundable commitment. Work backwards from the caterer's final count, venue cancellation terms and promotion schedule. A deadline is useful when it leaves you choices. It isn't useful if every major cost became payable a week earlier and you can no longer change the plan without a loss.

Start promotion with the audience most likely to care about the specific brunch. Agree what the chef and host venue will share, when they'll share it and which booking link they'll use. Show the meal and explain the format. A photograph of food can attract attention, but the caption still needs to tell people why this is a hosted event they should book in advance.

Review sales by sitting. A strong morning session can hide a weak afternoon if you look only at the total. Likewise, a busy group booking can make sales jump without indicating a repeatable flow of new buyers. Ask what changed when orders arrived and use that information carefully. You need evidence for your purchasing decision, not a confident story about every small movement.

Discounts need to fit the remaining budget. In the fictional first sitting, ten tickets discounted by $10 reduce the sellout surplus from $320 to $220, assuming the retained amount falls dollar for dollar and all other costs stay fixed. If the discount doesn't create extra paid demand, you've simply collected less from people who might have bought anyway. Set a quantity and an end date before promoting it.

When questions recur, fix the page. If several people ask whether coffee is included, answering each message doesn't solve the cause. Add the missing information where buyers are making the decision. Be careful with changes after purchase. Clarifying the offer is different from quietly changing it, and existing buyers may need a direct explanation if a material detail changes.

At the decision date, compare paid bookings with the real committed-cost case. If the event doesn't work, assess the options you can lawfully and honestly offer. You may keep the smaller sitting, renegotiate a supplier commitment or cancel under the applicable terms. Our event cancellation email guide helps with the communication if that becomes necessary.

Brief the room before the first guest arrives

Give each person a defined job for the moments that overlap. Someone welcoming guests cannot simultaneously answer every kitchen question and take payment for extras. Agree who runs admissions, who leads service, who confirms food information and who handles a complaint. One person may hold several roles, but test whether the work happens at the same time.

Use one final guest record for the sitting, with the relevant booking references, group arrangements and confirmed requests. Keep dietary details restricted appropriately. The room team needs a reliable way to reach the food lead, and the kitchen needs to know when a change has been acknowledged. Don't rely on someone remembering a message sent while they were unloading supplies.

Walk the route as a guest. Check the entrance, signage, accessible route, coats, toilets and seating. Then walk it as a server carrying food and as someone clearing used dishes. If those movements collide, change the arrangement before service. The atmosphere will feel more relaxed when the work behind it has enough space.

Agree the late-arrival response. If the meal is served in courses, say what the kitchen can still provide and who explains it. Don't promise that every missed course can be restarted without affecting other guests. Equally, avoid making a server invent a refusal at the table. The public terms, host explanation and kitchen's actual ability should match.

If the event includes a performer or chef introduction, give them an agreed cue and finish. A welcome that overruns can delay food and reduce the time guests have to eat. Keep the programme compatible with service, including noise levels that let guests hear staff. A brunch can have energy without asking the kitchen to wait for an unpredictable performance.

Before opening, ask each lead whether their part is ready. That includes the food procedures, room, guest records and any unresolved request. If something prevents safe or accurate service, delay the relevant activity and explain it. The advertised start is a commitment to organise around, but it doesn't justify proceeding with a problem the responsible team hasn't resolved.

Reset, settle and decide what to repeat

If you run two sittings, close the first as deliberately as you opened it. Help guests leave comfortably, clear and clean according to the operation's procedures, restore the layout and check the next guest records. Give the kitchen and room leads a clear chance to say whether they're ready. Admission to the next sitting should follow readiness, rather than pressure from a queue outside.

After the final sitting, complete the agreed venue handback and record outstanding charges. Count actual meals supplied, paid tickets, complimentary places, refunds and staff hours. If unused ingredients can safely return to normal operations, record that under the food operator's procedures. Don't assume that unserved food has no cost or can automatically be reused.

Compare the result for each sitting as well as the whole event. The first may carry the shared setup cost while the second adds a worthwhile surplus, or the extra session may have consumed more labour than expected. Keep the allocation clear so you can explain the decision. Changing where you record an invoice doesn't change what the business spent.

Keep the payment calendar alongside that result. A profitable brunch can still require cash for ingredients, a chef deposit and hire before the ticket payout arrives. Record when those amounts are due and how you'll fund them, including a suitable refund reserve. Count a deposit as part of the supplier's total bill, not an extra cost on top. That simple check stops the same payment appearing twice in your budget while a real funding gap goes unnoticed.

Ask guests focused questions about what you sold. Did the menu and included drinks match the page? Was there enough time? Did communal seating work as described? Ask staff where service slowed down and what caused it. A guest saying the meal felt rushed gives you something to investigate against the actual course times and reset plan.

Choose the next format from that evidence. You might keep one sitting, leave a longer reset, remove a slow dish or change the group-booking process. Cost the correction before announcing another date. A sold-out brunch is encouraging, but the repeat decision should include the actual money left, the work it took and whether the team can deliver the same promise again.

Before opening the next sale, update the menu promise, staffing quote and purchasing deadline together. Then read the page as the next buyer will. They should be able to tell what they'll eat, when they'll be there, who to ask about their needs and what the payment covers. Once those answers agree with the plan your team will use, you've got a brunch ready to sell.