How to organise a ticketed chilli cook-off

To organise a ticketed chilli cook-off, agree how the food can be prepared and served before recruiting contestants or selling tasting passes. Then build the event around a clear sample allowance, a workable service plan and published competition rules. The number of tickets you can sell has to fit all three.

The awkward part is that a cook-off contains several different experiences. A contestant wants a fair competition. A visitor wants good food without spending the afternoon in queues. Your judges need controlled samples, and you need enough money left after paying for the whole thing to make another edition worth running.

Those interests can work together. But selling admission first and asking everyone to bring a big pot later leaves some expensive questions unanswered. Where was that food made? How much does each ticket include? What happens when the favourite entry runs out halfway through voting?

This guide works through those decisions using a fictional small cook-off, with a reusable contestant brief, sample calculations, judging arrangements and a complete budget. The regulatory examples are from the United States and identify the authority concerned. Confirm the requirements for your actual location before relying on a preparation method, permit route or service arrangement.

Choose the kind of cook-off you can actually deliver

Start with the food operation. Will contestants cook from raw ingredients on site, prepare in an approved kitchen beforehand, or do some of each? These choices change access times, equipment, staffing and the permissions you need. They also change the competition, because a live cooking contest needs different rules from a tasting competition between finished dishes.

For a first event, I'd choose one clear format and keep the public offer small. You can create an enjoyable afternoon with a handful of strong entries, a defined tasting experience and a fair result. Adding a live cooking stage, a bar and several competition categories means paying for more operations before you've proved demand for the basic event.

Decide whether you want an independent competition or an event sanctioned by a recognised organisation. A sanctioned event brings rules you must check with that body, rather than inventing a similar badge for your poster. The International Chili Society's published 2025-26 contestant rules, for example, distinguish judged categories from People's Choice and require compliance with local and state food rules. Those are that organisation's rules, not universal cook-off requirements.

Our fictional example is independent. Eight adult teams each submit one chilli recipe. A panel chooses a judged winner, while ticket holders choose a separate People's Choice winner. The event sells up to 200 adult tasting passes for one afternoon, with one small sample from each of the eight entries. There is no alcohol, separate meal sale or unlimited tasting promise.

For this example, preparation takes place in kitchens approved for the operation, with transport and hot service arranged under the relevant food plan. We're assuming the authority accepts that method. If yours requires cooking on site, you must change the production plan and costs before using the example.

Write the format in a paragraph before choosing the event name. Include who competes, who attends, what admission includes and how winners are selected. Use that paragraph when speaking to the venue, food lead and prospective teams. If each person understands a different event, sort it out now.

Confirm the food-service route before inviting home cooks

The first thing you want to ask your local food authority is whether your proposed contestants can supply food to the public through the method you've described. A talented home cook and an authorised public food operation are different things. Calling the portion a sample doesn't settle the question.

Illinois provides a useful example. Its Department of Public Health's temporary food operations guidance includes food samples, requires preparation at an approved temporary location or approved kitchen, and prohibits home preparation or storage. Permits come through the local health department. That's the Illinois position described by that source; don't copy it as a rule for every jurisdiction.

Send the authority your proposed menu, site, attendance, preparation locations and service hours. Explain who buys ingredients, who prepares each entry, how it travels, where it is held and who hands out samples. Ask which approvals apply to the organiser and which apply to individual teams. Get the answer attached to the actual plan, rather than asking whether cook-offs are generally allowed.

Permit responsibility can vary. Salt Lake County's temporary food event guidance says each vendor needs its own permit and that event planners cannot obtain those permits on vendors' behalf. It also says an existing establishment's permanent permit doesn't automatically transfer to a temporary operation. A restaurant name on your contestant list therefore isn't enough evidence that its festival booth is ready to serve there.

Ask about deadlines early. Houston's temporary food permit page, reviewed in September 2026, states that applications must arrive at least 14 days before the event under its current process. Other locations have their own procedures. Your planning calendar needs the actual deadline, time to resolve questions and any required inspection before service.

Appoint someone competent to lead the food arrangements and give them authority to reject a proposed method. They should work with the participating food businesses and relevant officials on preparation, transport, holding, hygiene, ingredient information and corrective action. The organiser must supply the shared facilities it promises and prevent unapproved teams from serving.

If you want to include talented amateurs, explore an approved shared-kitchen arrangement with the authority and food lead. Confirm supervision, booking, storage, transport and who carries each responsibility. Price that arrangement honestly. If it doesn't work, change the contestant offer instead of suggesting people quietly prepare at home.

The broader food safety checklist for event organisers covers those responsibilities across an event. Here, the extra challenge is making eight separate entries behave like one planned tasting service while preserving the competition between them.

Sell a specific tasting experience

Your ticket page should answer the question someone will ask before spending money. What do I get to eat, and how much of the afternoon will I spend getting it?

In our example, a tasting pass includes admission during the stated hours, one 50 ml sample from each of eight entries and one People's Choice ballot. Water is available through the planned drinking-water service. There are places to pause and eat, a short introduction to the teams and a winner announcement. The samples are tasting portions, and the page says so. It doesn't sell them as lunch.

The 50 ml quantity is a fictional product decision, not a recommended portion for every event. Test the serving vessel, recipe texture and actual fill with your teams. A nominal cup size doesn't establish how much chilli reaches the visitor. A heaped scoop can consume the reserve much faster than anyone notices.

Keep tasting entitlement separate from voting entitlement. The sample card records which entries a visitor has received. The ballot records the entry they want to win. If you use the same token for both, a visitor may believe they must surrender their vote simply to get something to eat.

For this format, I'd use a card with eight numbered sample boxes and a separate ballot issued at check-in. Each booth marks its own sample box when serving. The visitor can choose the order, but receives only one included sample per entry. Staff need a clear replacement process for a damaged or lost card, with checks that don't casually issue another full tasting allowance.

Explain arrival and service times separately. If tasting ends before the award ceremony, someone arriving for the final announcement can't reasonably expect to start the whole tasting route then. Make the last recommended arrival clear before purchase and repeat it in the event reminder. Decide how you handle late arrivals and what remedy applies if you cannot provide the advertised experience.

In Loopyah's ticketing tools, you can set ticket types with their prices and quantities, take payment and give buyers QR tickets through their confirmation email. Use that to sell and check the tasting admission. Your team still runs the sample card and ballot process described here, with the agreed controls at each booth.

Recruit teams against a written delivery brief

Contestants supply the main attraction, so recruit for dependable delivery as well as an interesting recipe. Ask what they can produce through the approved method and how they will serve it. A brilliant competition bowl doesn't prove the team can provide consistent public samples for two hours.

Separate applying to compete from being accepted. Review the recipe category, proposed preparation method, required permissions, equipment and serving team before confirming a place. An application receipt should say that review is still pending. Don't let paying an entry charge become an implied food-service approval.

Our example waives contestant entry fees and pays each accepted team an agreed $200 supply allowance. That's a fictional commercial arrangement, not an industry rate or a claim that $200 covers every team's costs. Teams must price their ingredients, preparation, serving labour and transport before agreeing. The organiser needs viable suppliers who understand the quantity they've promised.

You could charge an entry fee at another event, particularly where the competition itself has established value. Keep it separate from public tasting revenue and describe what the contestant receives. If entrants also provide a large quantity of public food, show that obligation clearly. An attractive prize doesn't make hidden production costs reasonable.

Use a brief like this, completed for each accepted team:

• The competition is independent, with one recipe per team and separate judged and People's Choice awards.

• The accepted recipe, preparation kitchen, responsible food operator and service lead are recorded by name.

• The public allocation is 12 litres of ready-to-serve chilli, including the stated reserve, plus 300 ml held separately for judging and any planned retaste.

• The recipe and its current ingredient information must match what is submitted and served. Changes need review before use.

• The organiser and team list exactly which equipment, utensils, packaging, facilities and staff each supplies.

• Arrival, acceptance checks, setup, judging collection, public service and packdown times are confirmed.

• The supply allowance, payment dates, withdrawal process, replacement arrangements and treatment of a failed acceptance check are agreed in writing.

Treat the ingredient information as a current working record. Obtain the recipe and relevant ingredient labels, including stocks, sauces and spice mixes. Decide who reviews substitutions and removes outdated booth signs. A cook changing one sauce during preparation may change the information your visitors rely on.

Keep a suitable replacement team in reserve if you can, but give them the same review. Replacing a withdrawn entry with an unapproved pot from a friend's kitchen doesn't repair your lineup. It creates a new food operation at the point when you have the least time to check it.

Calculate samples for every entry

Start with the full entitlement you've sold. If each of 200 visitors can taste all eight entries, each team needs to cover 200 samples. You cannot divide 200 visitors by eight teams and ask each team to feed 25 people. That calculation would provide only one sample per visitor across the entire event.

At our fictional 50 ml serving, 200 samples require 10 litres of ready-to-serve chilli per entry. Across eight entries, that's 1,600 samples and 80 litres for the public entitlement. These are finished service quantities. They aren't ingredient purchase weights, and they don't tell you the raw meat or bean requirement.

The example adds two litres of public reserve per entry, giving 12 litres each and 96 litres across the eight booths. That reserve is an allowance we chose for this calculation, not a benchmark. Rehearse the recipe and service to decide what your operation needs for portion variation, handling losses and other contingencies.

Judging uses a separate allocation. Here, five judges each receive a 30 ml sample from each entry. That requires 150 ml per entry for the first round. We set aside another 150 ml per entry for any retaste, making the judging allocation 300 ml each, or 2.4 litres in total. Those small quantities also need a delivery and holding method the food lead accepts.

The total ready-to-serve quantity in this example is therefore 98.4 litres. Public service gets 96 litres, including its reserve, and judging gets 2.4 litres. Record those allocations separately so a runner collecting judging samples doesn't remove food the booth was counting on for public service.

Now check the promise at each individual booth. Extra chilli from one team can't replace a missing sample from another when your ticket includes all eight entries. Equal portions also matter for the public vote. A booth serving generous half-cups can run out while another follows the agreed fill, leaving visitors with unequal chances to taste the lineup.

Have teams test finished yield with the actual recipe and equipment. Ask them to show how they measured the quantity and accounted for what remains in containers. Our guide to catering quantities per attendee explains the difference between finished portions and ingredient purchasing. Apply that method to each recipe rather than assuming every large pot has the same usable volume.

Do not sell extra passes against the reserve automatically. It exists to protect the original service promise. Another ticket adds demand at every booth, along with another person using the site, toilets, seating and entrance. Any increase needs a revised quantity, capacity and cost decision.

Test the busiest booth before setting the ticket cap

Enough food doesn't mean people can obtain it comfortably. Think through the service at a single booth. A visitor presents a sample card, the server checks it, fills a cup, hands it over and marks the card. Ingredient questions, dropped cards and replenishment take time too.

Our public tasting runs from 1 pm to 3 pm. At 200 visitors taking one sample from each entry, each booth must complete 200 handovers in 120 minutes. That's about 1.67 handovers per minute on average. It assumes visitors spread their requests across the whole window, which they won't necessarily do.

Suppose a rehearsal finds that a prepared serving position can complete a handover every 20 seconds. That would be three handovers per minute, or a theoretical 360 over two hours. At 40 seconds, the same calculation falls to 180. The second arrangement couldn't deliver 200 samples even with perfectly even demand and uninterrupted service. These are invented test results to explain the calculation, not measured event benchmarks.

The faster arrangement still needs a realistic arrival test. Visitors may all head towards the most prominent booth after opening. A food-information question can occupy a server, and a refill can stop that position. Try the full process with the actual equipment and staff, including those interruptions, before treating the arithmetic as a ticket limit.

Separate admission from sample collection. If the person scanning tickets also explains eight dishes, distributes ballots and resolves ingredient questions, the gate becomes a slow information desk. Prepare the cards and route information in advance, then provide a separate place for questions and ticket problems.

Plan booth queues with the venue and competent safety team. A short queue can still obstruct the route to the next stall or prevent a wheelchair user reaching the counter. The footprint of a booth includes the people waiting and the space staff need to replenish it safely.

W3C's accessible event planning checklist recommends checking venue accessibility and asking participants about access needs. For a cook-off, apply that work to the whole tasting route. Check the entrance, paths, service heights, places to sit, toilets and way to obtain help. Publish verified access information so buyers can judge the outing before paying.

Food supply, service speed and site capacity each place a limit on sales. Use the lowest workable limit after the relevant assessment. A site that can accommodate more visitors doesn't create more chilli or make a slow booth faster. Complimentary tasters use the same food allowance as paying guests and need recording in the plan.

Our example includes no complimentary public tasting passes. Team members, judges, crew and any other people present still count in the site's assessed occupancy arrangements, even when they aren't public tasters. Arrange their meals separately, with team meals covered by their agreed supply deal and organiser crew and judge refreshments included in the relevant staffing allowance.

Make safe service possible during the rush

Walk through the actual operation with the food lead and teams before signing off the layout. Where do deliveries arrive? Who accepts each batch? How do containers reach holding equipment? What happens when a booth needs replenishment while the public is queuing?

The teams' food plans need to cover the relevant stages, with their applicable cooking, cooling, transport, reheating and holding requirements. Have the competent people set those instructions for the menu and jurisdiction. A generic temperature copied onto a volunteer checklist won't describe all those processes or what to do when a check fails.

Assign owners for shared water, handwashing, cleaning, waste and power. Include replenishment and response during service. If a facility stops working, the person discovering the problem should know which operations it affects and whom to contact. A working tap during setup doesn't prove the water arrangement will last until the final sample.

Keep the public out of preparation and replenishment routes. Agree how teams store reserve batches and obtain them without carrying hot containers through visitors. Confirm that the equipment can safely hold the planned quantities. Asking everyone to bring more food creates a problem if the approved storage and holding arrangement has no room for it.

Food information needs the same attention. The FDA's food allergy guidance explains that allergen cross-contact means unintentionally introducing an allergen into another food. An ingredient list alone doesn't describe how shared utensils or preparation affect that risk. Ask each food operator to explain its controls and the information staff can accurately give visitors.

Don't describe every meat-free entry as suitable for every dietary requirement. A vegetarian recipe might contain milk, wheat or another ingredient a visitor needs to avoid. Your event dietary and allergy planning should distinguish recipe preferences from specific food requirements and explain where guests can ask a competent person before accepting a sample.

Give servers a clear response when they don't know. They should stop, check the current information and reach the responsible lead. Guessing because the queue is growing is precisely what the process needs to prevent. Keep the current recipe information available without displaying visitors' personal health details at booths.

Agree stop-service authority and the route for medical help, suspected food concerns and official reporting. The safety decision comes first. Your producer then handles the operational consequence, including public information and any remedy for a tasting offer the event can no longer provide.

Publish rules that produce a result people can trust

For an independent competition, write rules around the experience you're actually running. State which recipes are eligible, whether beans are allowed, whether there are separate dietary categories and what preparation is permitted. Publish the rules before teams commit money or ingredients.

Our example has one open recipe category. It does not claim that the judged winner is the best traditional red chilli or the best vegetarian chilli. If you want category awards, recruit enough suitable entries and design a judging process for each. Printing another prize certificate is easy; delivering a credible comparison takes more work.

The judged award should use coded samples presented consistently. A steward keeps the entry-to-code record away from the panel, collects samples under the food plan and places them in identical approved vessels. Keep team branding and promotional conversations outside the judging area. Describe the process honestly as coded tasting rather than guaranteeing anonymity under every circumstance.

Have the food lead specify hygienic portioning, clean utensils for every taste and the handling of any retaste stock. Judges shouldn't share tasting spoons or return a used spoon to a common sample. Build those supplies and the time to change them into the judging setup.

Choose judges who can apply the published criteria and disclose relevant connections to teams. Replace someone with a material conflict or use the agreed conflict procedure. A sponsor's representative shouldn't acquire the deciding vote simply because their company paid for the prize.

For this fictional contest, each of five judges scores every entry out of 20. Flavour balance receives up to ten points, texture up to five and aroma up to five. The maximum total is 100 points per entry across the panel. These are proposed house rules, not an official judging standard. Test whether judges understand the criteria in the same way.

Have two people check the totals independently before announcing a result. Specify the tie process beforehand. Here, a tied total is separated first by combined flavour score, then by combined texture score. If both remain equal, judges conduct one coded retaste of the tied entries under the food lead's approved arrangement. Each judge then casts one vote. The entry with the most votes wins; a further tie produces joint winners.

This retaste allocation has a limit. If several awards or repeated rounds would require more food or time, plan those before opening entries. Don't keep extending judging because nobody decided what happens after the first tie.

People's Choice uses its own simpler rule. Each tasting-pass holder receives one ballot and chooses one accepted entry. The ballot closes at the published time, and two staff count it away from teams. Decide how blank, altered, duplicate or unreadable ballots are treated and tell voters what constitutes a valid vote.

I'd resolve an equal People's Choice total by declaring joint winners. In our example, each award has a fixed $200 cash prize, divided equally between any joint winners of that award. The two awards therefore cost $400 in total, including ties. Publish that arrangement before entry. An improvised deciding vote from the producer makes the result harder to defend.

Price the event using what you actually retain

Now put the entire operation into the budget. Food supplied by contestants isn't automatically free, staff time doesn't disappear because you're organising it yourself, and ticket revenue isn't the same as money left after delivering the tasting.

Here's a fictional budget in US dollars for our eight-team, 200-pass example. These are invented planning figures, not supplier quotes, market rates or promised results. Replace every allowance with the costs of your assessed event. The example assumes no sales tax applies and excludes business income tax; confirm the actual treatment where you operate.

Fixed event costs total $8,000:

• Eight team supply allowances at $200 each cost $1,600.

• Venue hire, including agreed setup and packdown access, costs $900.

• Shared equipment, power, water, hygiene facilities and waste arrangements cost $1,300.

• Organiser pay, preparation, administration and post-event work cost $1,000.

• Event crew, the food lead and the assessed first-aid provision cost $1,600.

• Prizes, including the agreed joint-winner arrangement, cost $400.

• Marketing costs $400.

• Insurance, permissions and professional checks cost $400.

• Contingency is $400.

The team allowance assumes the agreed public and judging quantities, the approved preparation and transport, and the team's serving labour are included in that deal. Check those terms with each team. The shared crew line covers the organiser's operation rather than paying those same team servers a second time. If actual quotes exceed an allowance, change the budget before proceeding.

Set the tasting pass at $55, with a hypothetical $4 selling and payment deduction absorbed inside that price. Another $6 per paid taster covers sample cups, spoons, cards, water and other attendance-related supplies. That leaves $45 per paid pass towards fixed costs and profit. The $4 is a fictional deduction for this calculation, not quoted Loopyah pricing.

At 160 paid passes, the event contributes $7,200 towards its $8,000 fixed cost and loses $800. At 180, contribution is $8,100 and profit is $100. At the full 200, contribution is $9,000 and profit is $1,000. We've treated the contingency as spent in all three results. Replace it with actual spending when settling the event, rather than counting it again as another cost.

Break-even requires $8,000 divided by $45, rounded up to 178 paid passes. That's a demanding target within a 200-pass allocation. The useful question is whether you can credibly sell that many at $55 while delivering an afternoon buyers value. If you can't, the format needs changing before you book it.

Discounts make the margin thinner. If 40 of the 200 passes sell for $10 less, retained income falls by $400 under our unchanged fee assumption. The sellout profit becomes $600. If shared equipment separately costs $500 more than budgeted, the original full-price result becomes $500. Both changes together leave just $100.

Don't treat that $100 as a successful event simply because the tasting sold out. The organiser's stated pay is already included, but there's little return for taking the commercial risk. You can improve the offer enough to support the price, reduce genuine costs, secure confirmed additional income or choose a smaller, simpler format. Removing required controls isn't a sensible cost reduction.

Handle sponsorship and cash without promising away the contest

A sponsor can fund a real part of the experience, such as the awards or shared tasting equipment. Keep the rights specific and check their cost. Cash paid for a branded area may also create printing, staffing or installation work that the original budget didn't include.

If a sponsor offers $1,000 and delivering the package costs $300, its contribution before any further deductions is $700. Under the unchanged example, that would raise full-price sellout profit from $1,000 to $1,700. Use only a confirmed amount after applicable fees, tax and fulfilment costs. Don't enter the headline cheque as pure profit.

Keep influence over the award out of the package. Naming a prize is different from choosing its winner. Explain that distinction before accepting money, especially if a sponsor also supplies a competing team. The contest's credibility is part of what your visitors and contestants are paying to participate in.

Prepare a cash calendar alongside the profit budget. List deposits, team payment dates, equipment balances and expected receipts when money will actually be available. A profitable forecast won't pay next week's venue deposit if the money arrives after the event. Put your own funding or borrowing in the calendar and include its real cost where relevant.

Set a sales review before the next major commitment becomes unavoidable. Compare paid sales and available cash with the remaining costs, refund obligations and cancellation terms. In our example, 178 is the full-budget break-even figure. It doesn't mean waiting until the afternoon before opening to decide whether 178 sales will happen.

Give buyers a reason to choose your afternoon

Once the operation is confirmed, promote what makes this particular lineup worth tasting. Introduce the accepted teams and explain the differences between their recipes, using information they've checked. A short account of a team's approach tells a buyer more than another poster announcing that the competition will be fierce.

Keep the same tasting allowance in every promotion. If a team describes the event as unlimited samples while your ticket page promises one per entry, visitors will arrive with the wrong expectation. Supply teams and partners with the approved offer, service hours, price and ticket link, then check what they publish.

Show the scale honestly. Our fictional event is an afternoon tasting competition with eight entries. Explain the sample size and the award programme so people can decide whether the outing suits them. Don't promote an extreme heat challenge unless you've separately planned and assessed that activity. Spicier food isn't the same promise as better food.

Ask partners for specific support you can follow up. A participating food business might introduce its entry to its existing audience, while a relevant local publication might feature the lineup. Agree the publication date and what each person will share. Being named as a partner doesn't establish that anyone will actually see the offer.

Review paid purchases against your decision dates. If interest is high but sales are weak, look at the questions buyers keep asking. They may not understand the portions, the setting or what justifies the price. Fix a missing explanation before buying more reach. If the offer itself isn't worth the price to that audience, revise the event while you can still change its commitments.

Rehearse the day with separate contestant and public arrivals

Build the working schedule backwards from approved service. Our example uses public tasting from 1 pm to 3 pm, ballots closing at 3.10 pm and awards at 3.30 pm. Visitors can remain for the announcement, with public closing at 4 pm. The venue booking runs from 8 am to 6 pm for preparation, checks and packdown.

Those hours are invented planning choices. The food lead must confirm that preparation, transport, holding and judging arrangements support them. If an authority requires different access or inspection timing, change the schedule. The public programme can't overrule a failed opening check.

Contestants have allocated arrival windows before the public arrives. The receiving team checks identities, the accepted recipe and required records, then follows the food lead's acceptance process for the delivery. A team with an unresolved problem waits in the controlled arrangement the plan provides; it doesn't begin serving because its banner is already up.

In this example, the panel receives its separately allocated judging samples before public tasting begins. The exact collection and tasting window must fit the approved holding method. It also needs enough time for scoring, checking totals and any retaste without drawing staff away from public opening duties.

Brief the whole team on roles. The producer coordinates the event. The food lead controls the agreed food decisions. Booth teams serve their own accepted entries. Door staff check admission and issue cards and ballots. Stewards manage routes, while the voting team controls collection and counting. Assign cover for breaks and simultaneous problems instead of writing one person's name against several jobs at once.

Rehearse a lost sample card, a wrong ticket, a dropped serving utensil and a booth temporarily closing. Walk through how the right person receives each problem and what the visitor hears. Useful rehearsals expose a missing instruction while there's time to fix it.

Use Loopyah's attendee email tools for confirmed preparation information to ticket holders, such as arrival times, the tasting allowance, access details and how voting works. On site, pair messages with signs and staff announcements as appropriate. Someone already queuing for food needs an immediate clear instruction.

Plan for a missing entry before it happens

The most difficult failure is a booth that can't provide the advertised food. Your replacement plan should identify what you can safely and legitimately deliver, who approves it and what you tell visitors. It shouldn't depend on buying an unreviewed batch from whoever answers the phone.

Separate a short interruption from a lost entry. If the responsible food lead can approve resuming service, stewards can redirect visitors and explain when to return. If service cannot resume, stop describing the full lineup as available. Review the appropriate replacement or refund remedy under your terms and applicable consumer requirements, then give staff a consistent response.

Fair voting needs attention too. An entry absent for a substantial part of tasting hasn't had the same exposure as the others. Publish how withdrawal or service failure affects eligibility and ballots already cast. Resolve that with the competition lead before the event, while nobody knows which team might be affected.

Keep records of what happened and when. Which entry stopped, what stock or equipment was involved, who made the decision and what visitors were told? Preserve food and incident records under the responsible operators' procedures and any authority instructions. Urgent medical help must never wait for someone to finish investigating a recipe.

At closing, the food lead and teams control remaining food and equipment shutdown. Give them time to complete the agreed process before power or water disappears. Then reconcile admissions, issued cards, ballots, remaining supplies, refunds and final invoices. Keep enough detail to distinguish a portioning problem from a failed batch or a slow service position.

Decide whether the next edition deserves a bigger budget

Review the event as a paid experience and a business. Did visitors receive the samples they bought? Could they reach every booth, find somewhere to eat and understand the voting? Did contestants receive the facilities and payments you promised? Were the judging and public results checked without disputes you could have prevented?

Then replace every budget allowance with the actual number. Include extra preparation, late equipment charges, refunds and the time spent resolving problems after the public left. Compare the final result with the return you wanted, and identify which change caused each shortfall. A busy room won't tell you that.

Before opening the next edition, complete a short decision record. Write the accepted food-service method, confirmed team quantities, tested handover process, assessed ticket cap, retained income per pass and the sales decision date. Add every unresolved issue with a named owner and a deadline. Keep sales closed while a missing answer could change what you are able to deliver.

If you're developing a broader event around the competition, our paid food festival planning guide covers vendor deals and the wider programme. Expand only after you've costed what the addition changes. A bar, music stage or extra category needs its own delivery arrangements and a reason buyers will pay for it.

For the next cook-off, start by fixing the weakest part of this one. That might mean fewer passes, a clearer tasting allowance, better booth staffing or a higher price supported by a better experience. Reopen sales when the food operation, contestant agreement and budget support the same promise you put on the ticket page.