Original book · Free PDF

The Wedding Venue Hotel Handbook

The operating manual for hotels whose calendar is run by other people's weddings.

by Thibault Van de Sompele 2026 · HappyChef 95 pages Reading time: 121 min read

This book is written in English. This page is available in your language; the full book is English-only.

Forty-two Saturdays a year decide whether your hotel makes money. The other three hundred and twenty three days live in their shadow: housekeeping rotas built around wedding turnovers, kitchen development aimed at banqueting first, regulars who can't get a table because the terrace is set for a marquee. On paper the wedding calendar looks extraordinary — deposits landing eighteen months out, a single Saturday that outguns a slow week of room revenue. Off paper, the head chef just quit because he hasn't had a full weekend since March, the corporate accounts stopped calling two years ago, and nobody is entirely sure whether the rest of the hotel makes any money at all once you strip the wedding line out. This book is the system that stops that drift: the real contribution of one wedding after staff and displaced revenue, a break-even price for closing your doors to one couple, a script for the twenty-minute tour that decides next year's calendar, and the run sheet, kitchen and roster that get a 120-guest Saturday through the door in one piece.

The big idea

A wedding-venue hotel is a genuinely good business when weddings are priced, sequenced and systemised with real numbers behind every decision — the danger isn't hosting weddings, it's letting an unmeasured calendar quietly decide your strategy, exhaust your team and hollow out the other three hundred and twenty days.

Who should read it

Read this if you own or manage an independent hotel, country house or estate with 15-80 rooms where weddings are your largest revenue line and you've never put a hard number on what one actually earns you after staff, breakages and displaced room nights. Skip it if you run a pure event space with no rooms or regular trade to protect, or if weddings are a minor sideline rather than the calendar's main event — the frameworks here assume weddings are already dominating your P&L and your problem is getting them under control, not attracting your first one.

Key takeaways

  • Calculate your Calendar Dependency Ratio before changing anything else — it tells you exactly how concentrated your profit really is, not what you assume it is.
  • A wedding's invoice total is not its profit; net out labour, breakages, comped rooms and displaced revenue before you call any date your best one.
  • Price exclusive use against a real break-even, not a habitual supplement, or you're subsidising your best couples' privacy out of your own margin.
  • The show-round is a designed sales product, not a building tour — script the route, lead it with the same one or two people, and score every visit.
  • Systemise the wedding coordinator's relationships into a written playbook before a resignation forces you to reconstruct nineteen files from email archives.

What's inside — all 20 chapters

A full book, not a blog post. Every chapter below is a complete chapter in the free PDF and the online edition.

  1. When The Calendar Owns The Hotel
  2. The Economics Of One Wedding
  3. Exclusive Use: The Most Expensive Word In The Brochure
  4. The Two-Year Funnel
  5. The Show-Round As Product
  6. Pricing The Day: Seasons, Days And Demand Tiers
  7. Packages, Minimums And Per-Head Maths
  8. Deposits, Payment Schedules And Cancellation Terms
  9. The Wedding Coordinator Problem
  10. The Run Sheet: Operating The Day
  11. Feeding 120 At Once: Banqueting Kitchen Systems
  12. The Bar, The Band And The Neighbours
  13. Rooms On A Wedding Night
  14. The Weekday Problem
  15. Suppliers, Kickbacks And The Preferred List
  16. Reputation With A One-Year Delay
  17. Staffing The Saturday Spike
  18. Marketing To Couples Who Have Never Heard Of You
  19. Capital Projects: The Barn, The Marquee, The Licence
  20. The Balanced Venue

The Economics Of One Wedding

The invoice a couple pays is revenue, not profit, and it hides four cost categories most owners never separate out: the labour a wedding actually requires beyond normal staffing, the breakages and comped rooms folded quietly into hospitality, and the revenue the date would have earned anyway. On an illustrative 100-guest wedding, a €24,090 invoice nets down to roughly €16,750 of gross contribution once direct costs are removed — still excellent, until you subtract what that Saturday would have earned in room and restaurant trade if the wedding hadn't taken the property over.

That last step, displacement, is the one almost nobody counts, and it's why a peak summer Saturday and a quiet January one can carry wildly different true value even at similar invoice totals. The Wedding Contribution Sheet runs all four steps for every booking, and once owners build the habit across a season of weddings, it consistently reveals that the highest-invoice wedding of the year is rarely the most profitable one.

Exclusive Use: The Most Expensive Word In The Brochure

Closing your entire property for one couple is a real premium product, but most venues price the exclusivity supplement out of habit rather than calculation, and habit usually loses. The Exclusivity Break-Even adds up every room, restaurant cover and bar sale a wedding displaces on that specific date, converts it to displaced contribution margin, and sets that as the floor the exclusivity supplement has to clear before privacy is worth more to you than running the wedding alongside normal trade.

In a worked example, an exclusivity supplement priced at €3,500 against €5,275 of displaced contribution actually makes the exclusive version less profitable than the non-exclusive one, despite the bigger invoice. A hybrid protected-wing model — ring-fencing one restaurant, lounge and room block rather than the whole property — often captures most of what couples actually want from exclusivity while giving up far less displaced revenue.

Pricing The Day: Seasons, Days And Demand Tiers

Flat wedding pricing feels fair and costs you twice over: it underprices your most in-demand Saturdays, where displacement is highest, and underprices the wedding as a tool for filling dates that would otherwise sit empty. The Tiered Rate Card splits the year into peak Saturdays, shoulder dates, off-peak weekends and midweek, priced with a gap wide enough to genuinely shift a meaningful share of couples off oversubscribed Saturdays and onto dates your hotel needs filled.

Pair the card with a Demand Calendar built from enquiry volume, not booking volume, because enquiries reveal true demand before your own pricing has shaped it. A fully booked Saturday calendar tells you nothing about what a higher price would do — the only way to find out is to raise the peak tier on far-out dates and watch conversion.

Packages, Minimums And Per-Head Maths

A package that feels generous and one that is generous are different claims, and the gap between them is where margin quietly leaks — most often at the menu tasting, where a couple swaps in a pricier dish and nobody rebills the package. The Package Builder costs every element per head, including a labour allocation, so a €98-per-head wedding breakfast that looks like a 63% margin on paper stays that way in practice rather than eroding one unbilled upgrade at a time.

Guest-number minimums protect the other half of the equation: your kitchen brigade and banqueting team are sized to the booked headcount, not the final one, so a contractual minimum stops a shrunk guest list from quietly eating your fixed-cost margin.

The Run Sheet: Operating The Day

Every wedding that goes wrong goes wrong in one of two ways: something drifts off the clock, or a dietary number was wrong. The Master Run Sheet covers five parallel tracks — kitchen, service, rooms, grounds and suppliers — and shows exactly where they intersect, because the pinch point between photos finishing and the wedding breakfast starting is where an ordinary fifteen-minute overrun turns into a cascading late evening.

The fix is building deliberate slack into at least two transition points rather than stacking tasks end to end, paired with a Dietary Matrix cross-referencing every guest's requirement against their seat, checked once at the final-numbers deadline and once more at a mandatory pre-service briefing on the day itself.

Feeding 120 At Once: Banqueting Kitchen Systems

À la carte cooking is pull-based; banqueting is push-based, and treating the two the same is why kitchens back up the moment a wedding hits full capacity. Every dish on a banqueting menu has to pass the Banqueting Menu Criteria List — does it hold for twenty minutes, is it mostly prepped ahead, does the pass-finish step take under 45 seconds, does it plate consistently without individual judgement calls — because a dish that's only excellent in the ninety seconds after it leaves the pan will disappoint a real share of a 120-cover room.

A properly built plating line, one person per element rather than one person per plate, can move eight to ten finished plates a minute once rehearsed, which is the difference between a synchronised room and one where table one is on dessert while table twelve is still waiting.

Staffing The Saturday Spike

A 120-cover Saturday might need sixteen people on site against four on a Tuesday, and the venues that burn through good staff are the ones that ask the same core team to absorb that swing every single weekend with no system behind it. The Wedding Roster Template builds headcount off the run sheet's five tracks rather than a generic covers-per-chef ratio, and splits staffing into three deliberately managed pools — core, casual and agency — so agency becomes genuine overflow, not a routine crutch.

A written Fatigue Policy, capping consecutive weekend wedding shifts and tracking hours across the season, is the piece most venues skip and the one that most directly predicts whether good staff make it through to October.

Capital Projects: The Barn, The Marquee, The Licence

A permanent marquee, an orangery or a licensed ceremony room is real money and a multi-year commitment, and the Capital-Project Appraisal Template forces the payback case onto two separate lines instead of one optimistic blend: additional wedding count the asset genuinely enables, and rate uplift it allows across weddings you were already going to book anyway. Conflating the two produces an overly rosy business case, because most venues are constrained by demand for prime dates, not physical space.

In a worked example, a €340,000 permanent marquee pays back in just under five years on the combined case, or over eight years on the conservative case that assumes zero additional wedding volume — a materially different number, and the one worth actually committing capital against.

Put it into practice

  1. Calculate your Calendar Dependency Ratio from last year's P&L before making any pricing or staffing decisions.
  2. Run your last three weddings through a full Wedding Contribution Sheet to find your true net contribution, not your invoice total.
  3. Price exclusive use against a calculated break-even for at least one peak and one off-peak date.
  4. Set up a funnel tracker logging every enquiry by source, stage reached and outcome for the next quarter.
  5. Script your show-round route and designate one or two people to lead every visit rather than rotating whoever's free.
  6. Build a tiered rate card with at least four demand tiers and a genuine price gap between them.
  7. Write a Coordinator Playbook and test it by asking your coordinator to hand over one active file cold.
  8. Build a Wedding Roster Template off your run sheet's five tracks and add a written fatigue policy for consecutive weekend shifts.

Where the book falls short

The book is written for a hotel where weddings are already a significant share of revenue; a venue doing one or two weddings a year will find some of the systems, such as a dedicated coordinator or a wedding-specific roster, more than it currently needs, and the euro pricing examples will need recalculating for your own market.

Our verdict

If Saturdays already run your calendar and your weekdays are starving because of it, this is the first book to treat that imbalance as the actual problem worth solving.

About the author

Thibault Van de Sompele is the founder of HappyChef, a reservation and operations platform for independent restaurants and hotels across Europe. He built it after watching the same problems repeat across hundreds of businesses, and wrote this book to put what he learned in one place.

Frequently asked questions

How much should I charge for exclusive use of my wedding venue?

Enough to clear your Exclusivity Break-Even: add up every room, restaurant cover and bar sale you're displacing on that specific date, convert it to contribution margin, and price your exclusivity supplement at or above that number. It moves a lot between a peak Saturday and a quiet Sunday, which is why a single flat supplement almost always underprices your best dates. If full exclusivity doesn't clear the break-even on a given date, a hybrid protected-wing model — reserving one wing rather than the whole property — usually gets you most of the way there for less displaced revenue.

How do I calculate the true profit on a wedding, not just the invoice total?

Use a Wedding Contribution Sheet: start from the gross invoice, subtract direct costs (food, beverage, wedding-day labour, breakages, comped rooms), which gets you gross contribution — then subtract a realistic displacement estimate for that specific date, which gets you net contribution. Most owners find their highest-invoice wedding of the year isn't their most profitable one once displacement on a peak Saturday is properly counted.

What's a good staff-to-guest ratio for a wedding banquet?

A common working ratio for plated banqueting service is one server per 12-15 covers, tighter for a more elaborate service style, with kitchen brigade sized to your plating line's actual throughput rather than a generic covers-per-chef ratio. Build the full headcount off your run sheet's five tracks — kitchen, floor, bar, rooms, grounds/coordination — rather than reconstructing it from memory for every wedding.

How do I stop wedding season from burning out my staff?

Split your team into three deliberately managed pools — core, casual and agency — so no single group absorbs the whole Saturday swing, and put a written Fatigue Policy in place capping consecutive weekend wedding shifts (a common standard is no more than three before a mandated weekend off). Cross-train core staff across two or three roles during quieter weekday shifts so a casual no-show doesn't force an emergency agency call every time.

Why do wedding venue reviews take so long to appear, and how do I manage them?

Wedding reviews often land eight to twelve months after the actual day, once the couple is back from honeymoon and has seen their professional photos, so by the time a review appears the operational conditions that caused it are long gone. Manage it earlier in the relationship instead: calibrate expectations clearly before the day, recover visibly and acknowledge problems when they happen rather than fixing them silently, and run a structured Post-Wedding Follow-Up Sequence at one week, six to eight weeks, and the first anniversary to prompt reviews from satisfied couples before only complaints get written unprompted.

This is our own original book, free to read and free to download — not a summary of someone else's work.

Back to top

More book summaries

All book summaries