How to organise a guest chef dinner series

You've found a chef whose food you love, the restaurant has a quiet evening available, and people are already asking when they can book. It's tempting to announce the collaboration and work out the details afterwards. Then the resident chef asks who is ordering ingredients, the guest asks how their payment works, and the restaurant manager discovers that both teams expected to keep the drinks income.

To organise a guest chef dinner series, agree how the visiting chef will work inside the restaurant before you sell the first date. Decide who controls the menu, who runs service, how costs and income are divided, and how the kitchen returns to its usual work afterwards. Build a dependable evening around those agreements, then give each dinner a specific reason for people to come back.

I'd start with one confirmed dinner and a realistic plan for the next dates. You can explain that you're developing a series without selling meals you haven't costed or chefs you haven't contracted. A series gives your team a chance to improve with each service. You lose that advantage if every visiting chef has to negotiate the same practical questions from scratch.

This guide covers choosing the collaboration, agreeing the money, preparing the kitchen handover and selling dates that feel connected without feeling interchangeable. We'll use a fictional restaurant example to make the decisions concrete.

Decide what stays consistent across the series

A guest chef series needs a promise that survives the changing names on the menu. Perhaps diners come to meet cooks working with regional ingredients, or to try food from independent restaurants outside their city. Explain what connects the dates in language a guest could repeat to a friend. "Interesting chefs" leaves too much of the buying decision unexplained.

Choose the evening's format alongside that promise. A visiting chef might write the whole menu and cook with the resident team. Two chefs might develop a menu together. Or the guest might contribute a particular course and join a conversation during dinner. Those arrangements require different preparation and shouldn't all be sold as a complete kitchen takeover.

There's a useful real example in Y Marram's description of its 2026 guest chef series. Visiting chefs cook their menus alongside the restaurant team, with a set banquet and a conversation with the guest chef. The description tells diners what to expect during the evening as well as who is cooking. Give your own buyers that detail before asking them to book.

For your own series, decide what a returning diner can rely on. That could be the table arrangement, arrival process, approach to drinks and opportunity to hear from the chef. Keep those parts consistent when they work. The menu can change considerably while guests still recognise the evening they enjoyed last time.

Then identify what genuinely changes between dates. A different region, cooking technique or collaboration can justify another booking. Changing the chef's name while offering much the same meal at the same price may attract that chef's followers, but gives your existing audience less to consider. Ask each guest to explain the dinner's particular appeal before you approve the announcement.

You also need to choose whether the restaurant closes its normal service. My preference for an unfamiliar collaboration is a dedicated sitting where the team can concentrate on the guest menu. If ordinary bookings continue, work through shared equipment and staffing explicitly. Our paid pop-up restaurant guide covers establishing a temporary dining service; here, you're deciding how visiting talent fits an operation that already has commitments.

Choose a chef who fits the kitchen and the audience

Start with the food and the working relationship. A large following may help you reach people, but it doesn't tell you whether the chef can deliver this menu with your equipment or whether those followers live within travelling distance. Ask what the chef wants from the collaboration and explain what your business needs from it.

Request an outline menu before agreeing a public price. You don't need every garnish settled, but you need enough detail to assess ingredients, preparation, specialist equipment and the number of people required. A chef who needs an extra preparation day and a travelling assistant changes the cost before anyone buys a ticket.

Discuss how much of the cooking the visiting chef will personally do. If their name is the main reason people book, a brief welcome appearance followed by somebody else delivering the meal is a different offer. Agree their presence during preparation, service and any guest conversation. Put the same expectation in the agreement and public description.

Ask about experience working in somebody else's kitchen. You're looking for practical answers about adapting a dish, briefing an unfamiliar team and resolving a missing delivery. Invite the resident chef into that conversation early. They know where the restaurant already struggles and can spot a menu that depends on equipment the venue doesn't have.

Promotion belongs in the discussion too, with specific commitments. Will the chef introduce the dinner in their newsletter, share the booking page or record a short explanation of the menu? Agree what they are comfortable doing and when. A willing introduction to a relevant audience is useful; an assumed promise that their followers will fill the room isn't a sales forecast.

Finally, check dates, travel and preparation availability together. A chef may be free on the dinner night but unable to arrive before service. If that means the resident team prepares everything without a proper briefing, you're buying a different collaboration from the one you imagined. Resolve it before signing, or choose another date.

Name the people who make decisions

Creative collaboration works better when operational authority is clear. The guest can lead the menu while the resident kitchen lead controls how unfamiliar work fits the premises and its safety procedures. During service, everyone needs to know who calls the next course and who can pause a dish. Two respected chefs giving different instructions won't help the person holding a hot tray.

Write a short responsibility list for this particular dinner. Name the person rather than writing "restaurant" or "guest team" against everything. In a small operation someone can cover several roles, provided those jobs don't require them to be in different places at the same time.

• The menu lead approves dishes, portions and agreed alternatives.

• The resident kitchen lead confirms equipment, storage, preparation access and the kitchen's operating procedures.

• The service lead coordinates the dining room, course calls and guest explanations.

• The event lead controls ticket information, budget changes, buyer communication and the agreed response to disruption.

• A named food safety and allergen lead resolves questions through the operation's approved procedures.

Talk through a disagreement before it happens. Suppose a supplier sends a different sauce and the guest chef wants to use it. The decision needs ingredient information and a safety assessment, as well as culinary approval. Nobody should feel obliged to serve it because the dining room is waiting or the visiting chef is well known.

Include the person managing drinks. If the restaurant retains the bar, its team still needs the course sequence, pairing decisions and expected finish. A wine explanation can delay a course, and a delayed course can leave drinks staff working beyond their booked hours. These are shared service decisions even when the income goes to different businesses.

Make approval limits practical. The guest chef might approve a culinary change, while the event lead must approve spending beyond the agreed ingredient allowance. The safety lead can stop food service under the operating procedures. Explain how to reach each person during preparation and service. Having names on a document is useful only if the team knows when to call them.

Agree the chef deal in writing

Settle the commercial arrangement before either business starts spending against it. Australia's business.gov.au guide to preparing a contract recommends specifying the work, payment and completion conditions clearly. Use that as a practical starting point, then get advice appropriate to the relationship and jurisdiction. Describing somebody as a contractor doesn't by itself determine their employment status or obligations.

For a guest dinner, the written brief should identify the date, preparation commitments, expected service and agreed public appearances. Attach the approved menu outline and list what each party supplies. If the guest brings an assistant, say who pays them, who supervises their work and how their travel is covered. Don't leave an entire person's cost inside "chef expenses".

Specify whether the chef receives a fixed fee, a share of defined income, or a combination. If there's a percentage, write the calculation in ordinary words and test it with an example. "Ten percent of retained meal-ticket receipts after refunds, selling charges and applicable sales taxes" is clearer than "ten percent of revenue". Drinks, tips, sponsorship and optional extras need separate treatment where relevant.

Agree complimentary places and discounts before selling. A visiting chef may want to invite a mentor or partner, while the restaurant wants a photographer and local press. Those people occupy seats and eat meals. Decide whose allowance pays for them and whether their places affect a guarantee or percentage payment. An invitation should never leave the other party discovering the cost afterwards.

Travel needs both an amount and a booking process. Agree acceptable costs, who books, who carries cancellation charges and what happens if a journey becomes more expensive. The same applies to accommodation and ingredient freight. A capped reimbursement can be workable, but only if the chef can actually make the trip within that cap.

Put payment dates beside the amounts. A preparation payment may be due before launch, with a balance after the dinner and any percentage calculated from agreed records. State what those records contain, when both parties receive them and how questions are resolved. Avoid a settlement that depends on someone remembering to send a spreadsheet after a busy weekend.

Discuss cancellation, illness and substantial changes explicitly. If the named chef cannot attend, decide how the businesses will assess postponement, replacement and cancellation, then handle buyers according to the offer and applicable consumer rights. A clause between the businesses doesn't erase obligations to guests. Have the proposed terms checked rather than copying a blanket "no refunds" sentence.

Also agree permission to use names, photographs and recorded material. Ask before publishing recipes or reusing a chef's footage in later advertising. Keep the practical approval route short enough to meet launch dates. A collaboration can be friendly and still deserve a clear record of what everyone has agreed.

Calculate what each dinner needs to earn

Cost the dinner before deciding that the chef's reputation justifies an expensive ticket. Diners still compare the complete evening with other ways to spend their money. Work out the price your costs require, then assess whether you can present an offer that people will willingly buy at that price.

The US Small Business Administration's break-even explanation separates fixed costs from the amount that changes with each sale. That is a useful starting method here. Your actual figures need the signed chef agreement, staff plan, venue arrangement and tested menu, rather than another restaurant's assumed margins.

Consider a fictional dinner with room to sell 40 meal tickets. This is an illustration in USD, not a price recommendation, staffing standard or safe capacity assessment. Assume the complete cost review produces these fixed amounts:

• Guest chef fee, including their agreed development and appearance work: $650.

• Resident kitchen work and staff meals, including preparation and clearing: $450.

• Dining room and door staff: $400.

• Venue access and the agreed share of operating overhead: $550.

• Guest travel and accommodation: $250.

• Marketing and event administration, including costed owner time: $200.

• Additional equipment use and cleaning supplies: $100.

Those amounts add to $2,600. Suppose each paid ticket leaves $115 after selling charges and applicable sales taxes, and ingredients plus guest consumables cost $35 for every diner served. Purchase costs include taxes the business cannot reclaim. Borrowing costs and business income tax are excluded, and there are no refunds in this base example. Replace these assumptions with your own consistent treatment of tax and costs.

Each paid diner leaves $80 towards the fixed $2,600. Divide $2,600 by $80 and you get 32.5, so 33 paid diners are the first whole headcount that covers the modelled costs. At 32 paid diners you lose $40. At 36 you make $280. Selling all 40 leaves $600. The room can look comfortably busy while the dinner still loses money.

Now include two complimentary guests within that same 40-diner limit. With 38 paid guests, retained meal income is $4,370, while food and guest consumables for all 40 cost $1,400. Subtract the fixed $2,600 and the result is $370. The two invitations reduce the full paid result by $230 because you give up two $115 receipts while still serving the meals.

This is also why you need to compare chef deals using the complete calculation. Suppose the alternative is $400 plus 10% of retained meal-ticket receipts. All other assumptions stay unchanged. At 40 paid diners the chef receives $400 plus $460, or $860. That's $210 more than the original $650 fee, reducing your $600 result to $390.

Under that alternative, the fixed amount falls to $2,350, but each paid diner leaves only $68.50 after meal costs and the chef's percentage. The first whole break-even headcount becomes 35. A smaller fixed fee hasn't automatically made the dinner easier to fund through sales. Our event break-even guide explains how to work through more complicated ticket and cost arrangements.

Review cash timing separately. Deposits, travel bookings and food purchases can fall due before ticket money is available to spend. List those dates and maintain a cancellation and refund plan appropriate to your commitments. The profit calculation tells you whether the dinner can work; the payment calendar tells you whether you can finance it.

Budget the series without hiding weak dates

Keep a budget for every dinner and another for the whole series. Shared launch work can be spread across dates for planning, but it must appear once in the total. If you charge the full launch cost to every dinner, you overstate costs. If you leave it out because it happened before the first service, you overstate profit.

In our fictional $200 marketing and administration line, assume $120 is an allocation of a $360 series setup cost across three planned dates. The remaining $80 belongs to each individual dinner. The three budgets therefore include that $360 once in total. If you cancel two dates, revisit the allocation; the original cash payment hasn't disappeared with them.

Suppose all other costs and prices match the first example, with no complimentary places. Sales of 40, 36 and 30 paid dinners produce results of $600, $280 and a $200 loss. Together the series makes $680 under those assumptions. That might be acceptable for your business, but you should see which date needs improvement before confirming another similar booking.

Don't assume every visiting chef will have identical costs. Someone travelling from farther away may need an additional night and more paid preparation. Another menu may use ingredients with minimum order quantities. Price and assess that dinner on its own terms. The existing series audience can help it sell, but doesn't cancel its invoices.

Set a sales review before the next substantial commitment becomes unavoidable. Ask what it costs to proceed, change or cancel from that point, as well as looking at the complete event result. Agree the decision with the restaurant and chef under your terms. Booking another date to recover the last one's loss only makes sense when the next date has a credible budget of its own.

Check what ordinary restaurant trade you displace

The dinner's own budget doesn't answer whether it is the best use of the restaurant that night. Compare the collaboration with a realistic ordinary service, allowing for the sales and costs that would change. A busy Saturday takeover has a different commercial consequence from using a room that would otherwise be closed.

Ask the restaurant to make that comparison using its actual records. Which normal bookings would it give up? Would preparation also prevent lunch service, or use staff who were needed elsewhere? Account for the work around the dinner as well as the hours guests occupy tables. Extra paid preparation can affect the following day's operation too.

Keep the comparison consistent so you don't count the same overhead twice. An allocated share of rent belongs in a full event budget, but it isn't automatically an extra cash payment caused by this dinner. Compare like with like and identify any separately agreed venue charge. The fictional example above measures the dinner itself and includes no drinks, tips or sponsor income.

You may decide a collaboration is worth a lower immediate return because it introduces relevant diners or develops the team. State that purpose and the spending you're willing to approve. Then check the result afterwards. "It was good exposure" doesn't explain whether the partnership achieved anything your business intended.

Walk the guest chef through a working kitchen

Arrange the kitchen visit while there is still time to change the menu. The resident chef should show the visitor how the operation actually works, including the less convenient parts. An oven might exist but be unavailable during lunch preparation. A fridge might look spacious when empty while being fully allocated on the proposed event day.

Follow the food through the building. Start at the delivery entrance, then check receiving, storage, preparation, cooking, plating and the route to the dining room. Include washing and waste. Ask the visiting chef to describe their busiest course along that route. You'll learn more from tracing its pans and plates than from asking whether the kitchen seems suitable.

Agree which parts of the usual business continue around the event. If the restaurant serves lunch, identify exactly when its team releases workstations and equipment. A promised afternoon of preparation is meaningless if the visitor spends it waiting for space. Include a delay response so everyone knows what happens when normal service finishes late.

Write down the handover in terms both teams can check:

• The access time, receiving person and agreed finish for the visiting team.

• The equipment and storage allocated to the dinner, including anything unavailable or faulty.

• The preparation completed by the resident team and what still needs doing.

• Deliveries expected, ingredient records and who approves substitutions.

• The cleaning, food safety and emergency procedures the visiting team must follow.

• The condition, stock and equipment required for the next normal service.

The Food Standards Agency's Safer food, better business pack for caterers covers areas such as cleaning, chilling, cooking and management records. It is a useful reference for smaller catering businesses in England and Wales; the page directs Northern Ireland businesses to Safe Catering guidance. Use the appropriate system where you operate and bring visiting staff into that system before they handle food.

Include any food prepared away from the restaurant in the discussion. Ask where it is made, who is responsible and how it will be transported, received and recorded. A container arriving in the chef's car should be assessed under the agreed controls. Familiarity with the chef doesn't replace the information the resident operation needs.

Finish the visit with written actions and owners. If a dish needs extra refrigeration, somebody must confirm the suitable equipment, cost and location. Don't mark the kitchen ready because everyone enjoyed the tasting. Mark it ready when the team has resolved the specific requirements that would otherwise prevent service.

Adapt the menu before promising it to diners

Ask for a dish specification that an unfamiliar team can use. It should explain ingredients, portions, preparation, finishing and the serving method, with the relevant safety information recorded through the restaurant's procedures. A photograph helps with appearance, but doesn't tell a cook how much sauce to prepare or which garnish belongs on an adapted plate.

Test the hardest moment of the menu. Suppose the main course needs last-minute frying while another component uses the same workstation. You need to find that conflict when there is time to change the dish. A successful plate cooked for two people doesn't demonstrate that the team can serve the whole dining room at the agreed pace.

For our fictional 40-diner service, imagine a plating area that comfortably accommodates eight plates at a time. That requires five batches for one course, before you include clearing space or a remake. This isn't a recommended workstation size or service speed. It's a prompt to rehearse the actual sequence and check what happens to the first plate while the final batch is prepared.

Keep the chef's intention while changing what the kitchen cannot reliably deliver. A cold component might free equipment, a simpler garnish might reduce finishing time, or a different course order might avoid conflicting tasks. Make that decision together and retest it. The resident team shouldn't quietly simplify the food during service because nobody raised the problem earlier.

Cost the revised menu again. A substitute ingredient can change purchase quantities, waste and preparation hours as well as flavour. Check staff meals, the chef's tasting portions and agreed spare meals separately from ticketed diners. Don't buy for 40 guests and discover that the budget assumed the whole working team would eat nothing.

Drinks deserve a service test too. Confirm the non-alcoholic offer and water provision, the glassware required and whether pairings arrive before each course. If the venue sells drinks separately, explain that to diners and agree when orders are taken. A restaurant can keep its bar income while still contributing properly to the dinner's timing.

Confirm who operates the food business and permissions

An operating restaurant is a helpful starting point, but you still need to establish which business does what. Tell the relevant authorities how the partnership works, including who sells the dinner, prepares food elsewhere and controls the kitchen. Ask what the arrangement changes rather than assuming that either every permission carries over or every visiting chef needs a new registration.

In England, Wales and Northern Ireland, the Food Standards Agency's starting a food business guidance says a new business or one taking over an existing business should register with the local authority at least 28 days before trading. Ask the authority how your proposed arrangement is treated. That timing is jurisdiction-specific and isn't a universal rule for chef collaborations.

Check alcohol and any entertainment against the premises' actual permissions. In England and Wales, GOV.UK's Temporary Events Notice guidance explains the route for certain licensable activities on unlicensed premises or outside an existing licence's terms. Confirm the appropriate route locally before promising a pairing, later finish or entertainment programme.

Resolve insurance and employment arrangements for the people and work involved. If the visiting chef brings staff or works across borders, check the requirements that apply to that particular visit. Specify responsibility without suggesting that a private agreement can transfer away statutory duties. The restaurant, guest team and event business should each understand their own position.

Keep the resulting confirmations with the dinner plan and act on any conditions. It's easy for a different person to add a welcome drink or move the finish time while writing promotional copy. Have the event lead check those changes against the confirmed operation before they become a public promise.

Carry dietary requests all the way to the right plate

Collect requests early enough for the kitchen to assess them before you confirm a suitable booking. Explain what the dinner can offer and how people should contact you before paying if they need an adaptation. A guest typing "nut allergy" into a booking note needs an informed response, not an assumption that the chef will sort it out on arrival.

The Food Standards Agency's allergen checklist for food businesses, applicable to England, Wales and Northern Ireland, addresses responsibility, ingredient changes and communication between kitchen and serving staff. Use it alongside the rules and procedures for your operation. In a collaboration, check that both teams work from the same current ingredient information and know who can answer a guest's question.

For example, a visiting chef might bring a dressing made with a different bought-in ingredient from the one used in rehearsal. The approved process needs to catch that change before preparation or service. Update the relevant records and assess affected requests. A familiar dish name doesn't tell the serving team what is actually in the version being plated tonight.

Have the kitchen and service leads agree how an adapted meal is identified and delivered to the correct person. Table and seat information can help when it is accurate, but guests may move. Staff need a reliable confirmation procedure and a clear response when something doesn't match. They should pause and ask rather than guess.

Keep sensitive request information restricted to the people who need it for delivery. The visiting chef doesn't need the restaurant's whole contact list, and a photographer doesn't need dietary notes. Our guide to dietary restrictions and food allergies at events goes further into collecting requests, confirming meals and managing service. Recheck those arrangements for every menu, including dates booked by returning diners.

Plan backwards from the first plate

Build the preparation timetable with the people doing the work. Start at the agreed first course, then work backwards through plating, cooking, preparation, deliveries and menu approval. Add enough paid time for the visiting team to learn the premises. A tight timetable that assumes everyone already knows where the equipment lives will disappoint you.

An illustrative planning sequence could look like this. These are decisions to schedule, not universal lead times:

1. Confirm the concept, available dates, chef outline and workable venue arrangement.

2. Check the kitchen, responsibilities, permissions, budget and contract before launch.

3. Test the menu and settle what the public offer can promise.

4. Launch tickets with agreed promotion and a sales review date.

5. Confirm assessed guest requests, purchasing and the staffing plan before the relevant deadlines.

6. Receive the kitchen handover, brief both teams and test the final service sequence.

7. Deliver the dinner, return the kitchen and settle the agreed accounts.

Choose deadlines according to real commitments. A special ingredient order might close before ordinary produce purchasing. An accommodation booking might become non-refundable earlier than the chef's final invoice. The sales review belongs before the next commitment you still have a meaningful choice about, rather than on an arbitrary day because another event used it.

Plan the chef's conversation around the food. If the guest speaks while the kitchen needs them to finish a course, assign that work properly or move the conversation. Ask a host to prepare focused questions and agree a finish signal. Diners may enjoy hearing how a dish developed; they won't enjoy waiting for a hot course while the introduction continues.

Include late arrivals, guest questions and clearing in the service plan. Explain which courses can still be served when somebody arrives late, subject to the kitchen's controls, and brief the door team on that answer. Schedule setup and closing separately from the advertised guest hours. Those hours still require people, access and payment.

Sell each date with a specific promise

Write the ticket page so someone unfamiliar with the series can decide whether to come. State who is cooking, what their involvement includes, the menu format, seating, arrival time, expected finish and complete price. Explain drinks, service charges and any extras accurately. A returning diner may remember the format; a new buyer shouldn't need that prior knowledge.

Describe the entrance, accessible facilities and table arrangement accurately, with a contact route for access questions before booking. Make communal seating clear if that is the format. People choosing a private dinner for an anniversary may want a different setting, and it's better for everyone if they know that before paying.

Tell people why this chef and this menu belong together. Explain a relevant ingredient, technique or collaboration in recognisable terms. "A menu built around the chef's coastal cooking, developed with the restaurant's vegetable grower" gives you something to substantiate. A chain of superlatives doesn't help diners understand what their evening contains.

Be precise about menu uncertainty. You can explain that seasonal ingredients may change while still making a clear promise about the meal. Agree the scope before launch and communicate significant changes appropriately. Avoid publishing a detailed signature dish as the main selling point if the chef hasn't confirmed they can deliver it.

Keep one controlled total of bookable places across restaurant reservations, chef invitations and public ticket sales. If a partner has an allocation, record who can release it and by when. A shared series brand doesn't prevent an overbooking when different teams each assume they have spare seats. Don't increase capacity because the first dinner sold quickly until the kitchen and room have been assessed for the change.

With Loopyah ticket selling, you can publish the dinner page with ticket types and share the booking route through both the restaurant's and chef's channels. Set the public ticket quantity after accounting for separately reserved places. Both partners can promote the same dinner without needing separate public inventories.

For an initial series, I'd usually sell dates separately until the cost and offer for each are settled. A series pass can help when every date is confirmed, but it adds questions about substitutions, transfers, cancelled dates and any discount. Explain those terms before selling one. Early access to a future date can be a useful benefit without taking money for an unconfirmed dinner.

Build an audience that returns for the programme

Coordinate promotion with the restaurant and chef so the explanation is consistent. A short film about the actual menu, a conversation between the chefs or a clear introduction to an unfamiliar ingredient can help people judge the offer. Agree the assets and approval dates. Don't make the resident team chase launch material while they are also preparing normal service.

Give the chef's audience a clear route into the restaurant's series. Explain the location, atmosphere and booking arrangement as well as the visiting name. After the event, your next invitation needs a fresh reason to attend. Someone who came for one chef may love the programme, or may have no interest in the next cuisine. Let the offer establish that rather than assuming all buyers want every date.

With Loopyah's attendee email tools, you can select buyer segments for relevant communication, while event updates and promotional emails are distinguished and promotional sends exclude opt-outs. Use that distinction properly. Arrival instructions belong to the dinner someone bought; an invitation to another chef's dinner is marketing and needs the appropriate audience and permissions.

Ask each partner to promote to its own audience through an appropriate route. Working together doesn't automatically authorise sharing mailing lists. Decide what guest information each team needs to fulfil the dinner and handle it accordingly. You can coordinate an announcement without copying buyer details into every collaborator's spreadsheet.

Track which promotion produces paid places, then ask returning diners what made the next date appealing. Our repeat attendance measurement guide explains why comparable opportunities and attendee records matter. Someone who has only been offered one suitable date hasn't yet had the same chance to return as a guest who has received several relevant invitations.

Return the kitchen and learn before the next dinner

Before doors open, take both teams through the final plan and unresolved exceptions. Confirm who calls courses, who answers dietary questions and who handles a guest complaint. Review the latest menu and request information together. If something essential remains unresolved, deal with it before the team starts serving.

During the dinner, record problems while the details are clear. A late main course might come from insufficient plating space, an unexpected conversation or a missing staff member. Those causes call for different changes. A simple note about what happened and when is more useful than deciding afterwards that everyone needs to work faster.

The return handover matters because the restaurant has another service to run. Walk through the kitchen with the resident lead, check equipment and cleaning, identify remaining ingredients and record anything damaged or unavailable. Deal with food through the operation's safety and stock procedures. Don't leave unlabelled containers for the breakfast team to interpret.

Agree who handles follow-up tasks before the guest team leaves. That includes borrowed equipment, supplier credits, outstanding charges and any incident documentation. Thank the team for the specific work that made the collaboration possible, then pay and settle according to the agreed timetable. A successful dinner can still damage a partnership if the administrative finish is careless.

Review the actual result against the budget, including extra preparation, unused purchases, refunds and paid hours. Separate the cost of correcting a problem from spending that will recur at every dinner. Ask the resident team what they need changed before another visitor arrives, and ask the guest chef which part of the handover was unclear.

Before announcing the next date, confirm the chef, revised menu and budget with the people delivering it. If extra preparation erased the expected profit, change the menu or agree the additional budget before opening sales. The resident team should have those changes in its plan when the next visiting chef arrives.