In 1991, INFORMS gave its Franz Edelman Award, the prize for applied operations research, to three analysts from American Airlines for a paper titled Yield Management at American Airlines. The airline had been building the method since the late 1970s, with its chief executive Robert Crandall as internal champion, and by 1989 the head of its research group was writing in the journal Interfaces that an effective yield management system could add five to seven percent in incremental revenue, according to the INFORMS history of the company. Hotels adopted it within the decade and car rental and cruise lines followed, but function rooms, on the whole, did not.
Pricing an event venue like a hotelier means holding one base rate, moving it with a small set of published multipliers for season, day of the week and booking lead time, and never quoting a figure you later revise for the same date and scope. What follows covers each multiplier, the grid they produce, the words you use to explain a price that changes, and the two things yield management will never do for a venue whose real problem is demand.
Start from a base rate you can defend
Every multiplier in this article is applied to one number. Get it wrong and the whole grid is wrong by the same percentage, so the number deserves an afternoon. The base rate is the price of your reference slot in a shoulder month, confirmed a month or two ahead: for a seminar venue that is a weekday, for a venue that lives on private events it is a Saturday. If you have never worked out what that slot costs you to open, do that first. The arithmetic, the competitor read and the floor price are covered in how to set the right price for a seminar room, and this article assumes you have that figure in hand.
Two cautions. Do not use your current published rate as the base if that rate was itself set by copying a neighbour, because you would then be yielding around someone else's mistake. And do not build the base from your best month. Hotels anchor on a shoulder-season day precisely because the anchor has to be a price you are content to sell at for most of the year.
Season multipliers: three bands, not twelve
Sheryl Kimes, writing in the Cornell Hotel and Restaurant Administration Quarterly in 1989 in The Basics of Yield Management, lists the conditions under which the method works: fixed capacity, demand that can be segmented, perishable inventory, a product sold in advance, demand that fluctuates substantially, and low marginal sales costs set against high marginal production costs. A venue meets all six. The one that drives the season lever is the fifth, and you measure it from your own booking history rather than from what the trade press says about the industry.
The mapping itself, month by month with inquiry volumes and confirmation rates, is the subject of our article on seasonality and slow months. Its output is what you need here: the months you turn business away, the months you discount to fill, and the rest. Those become your three bands.
- High: months where you refused or lost dates for lack of capacity at least twice in the last two years.
- Low: months where you gave discounts you had not planned, or where confirmed events ran at under half your high-band count.
- Shoulder: everything else. The base rate lives here, at a multiplier of 1.00.
Resist the urge to make twelve bands. A client can keep three in mind, and as the section on communication shows, that matters more than precision.
The weekday lever, and why it is the touchiest
Fridays and Saturdays carry private events; Tuesdays to Thursdays carry corporate ones. Demand for the two rarely peaks in the same week, which makes a weekday multiplier the second most valuable lever you have. It is also the one clients like least.
Kimes and Jochen Wirtz tested this directly. In Has Revenue Management Become Acceptable?, a study of restaurant customers in Singapore, Sweden and the United States published by Cornell in 2003, time-of-day pricing and lunch-versus-dinner pricing were perceived as fair, while weekday-versus-weekend pricing was rated neutral to slightly unfair. The same study found that framing the difference as a discount rather than a surcharge improved perceived fairness in all three countries.
The practical consequence is a rule about which number you publish. Publish the highest price in each season row as the rate, and present the other days as that rate with a stated reduction. The arithmetic does not change, but clients take it better. Richard Thaler gave Cornell hoteliers the same advice in 1986, in a piece reprinted alongside Kimes's 1994 paper on perceived fairness of yield management: set your stated price at the highest you ever intend to charge, then discount from it.
Lead time: the hotel lever that translates least
Hotels charge more close to arrival because business travellers book late and pay whatever the rate is that day. Kimes's 1989 paper contrasts that curve with the group-business curve, where a hotel has over 70 percent of its rooms reserved a month or more ahead and has sold almost everything three weeks out. Event venues sit on the group curve. Your late demand is not an executive who will pay a premium; it is an assistant whose first venue fell through, or a couple who will not pay more because their planning slipped.
So for most venues the lead-time lever works in one direction only:
- Far out, more than four to six months: do not cut the rate. Offer better terms instead, such as a longer free option period, a gentler cancellation ladder or set-up the evening before. The usual deposit at signature still applies.
- Standard window, one to four months: grid price, no adjustment.
- Inside a month: fill the date if you can, quietly, on a case-by-case quote. Never publish a last-minute discount, or you will teach your market to wait.
A premium for late bookings is defensible only if you genuinely turn work away in that window. Very few venues do. If yours does, apply it to the grid price and say so in the quote, for reasons the next two sections make clear.
Build the grid
The formula is one line: grid price = base rate × season multiplier × day multiplier. Lead time is handled in the quote, not in the grid. Here is an illustrative grid for a venue whose reference product is a weekend day at £3,000, with round multipliers chosen for legibility rather than taken from any benchmark, and results rounded to the nearest £10:
| Season | Friday to Saturday (1.00) | Sunday (0.90) | Monday to Thursday (0.85) |
|---|---|---|---|
| High (1.25) | £3,750 | £3,380 | £3,190 |
| Shoulder (1.00) | £3,000 | £2,700 | £2,550 |
| Low (0.80) | £2,400 | £2,160 | £2,040 |
Two tabs in a spreadsheet are enough to start: one for the base rate and the multipliers, one for the grid they generate. The test of your set-up is what happens when you change a multiplier. If every quote template picks up the new figure, you have a pricing system. If three people have to be emailed, you have three grids, and within a quarter they will disagree.
Telling clients the price moves
In the UK this is now a legal question as well as a commercial one. The Competition and Markets Authority's price transparency guidance, CMA209, issued under the Digital Markets, Competition and Consumers Act 2024 and summarised on gov.uk, requires the total price up front in any invitation to purchase. A "from" price is permitted provided it includes every mandatory charge, and where the total genuinely cannot be calculated in advance you must show how the customer can work it out, with the same prominence as the price itself. Fines run to 10 percent of turnover or £300,000, whichever is greater. The rules protect consumers, so they bite hardest on your wedding and party business, but one pricing page is easier to run than two. A published grid with its multipliers stated passes the test. A "from £2,040" banner with the high-season Saturday price buried in a PDF does not.
The research on fairness points the same way. In Kimes's 1994 survey of hotel guests, a 10 percent increase for bookings made within three days of arrival was rated moderately acceptable when the policy had been advertised and customers were told they could pay less by booking earlier, and fairly unacceptable when the identical policy was applied without telling anyone. Rated worse still, at 6.45 on a seven-point scale where 7 meant highly unacceptable, was the practice of letting reservation agents knock up to 20 percent off for customers who pushed. In plain terms, that is what a venue does when it quotes a fixed price and then negotiates.
Kimes's 2004 Cornell report on restaurant revenue management puts the rule for rate fences in one sentence: they can comprise almost any set of rules as long as they somehow make sense to the customer. Season and weekday make sense to everyone. In practice:
- On the website: the grid itself, or the three season bands with the weekend rate for each and the midweek reduction stated. Not a lone "from" price.
- In the first reply: "For a Thursday in October our rate is £3,190; the same Thursday in November would be £2,550." The comparison does the explaining, and it answers the question the organiser was about to ask.
- Never: a number for a date, followed two emails later by a different number for the same date and the same scope.
Rolling it out, and what it will not fix
- Pull two years of confirmed events with date, day of week, price charged and how far ahead each was confirmed. Mark the months where you turned dates away.
- Set three season bands and two or three day types. Choose multipliers you can say aloud to a client without flinching; you can widen them later.
- Re-price the last ten quotes you sent using the new grid. If the high cells look wrong to you, they will look wrong to clients.
- Put the grid in the quote templates and keep availability in one calendar next to it, so the person answering inquiries sees date and rate together. Yield management falls apart with double bookings: a date sold twice ends in a refund, whatever the price.
- Review quarterly, comparing revenue and confirmed events per band with the same quarter a year earlier. Still full in high season at the new rate? Move that multiplier up a notch.
What the method will not do is create demand. Kimes's list of conditions assumes the fluctuation is already there. A venue that is quiet in every month has a positioning or visibility problem, and a multiplier of 0.80 will not solve it. Nor will a grid rescue slow replies. An organizer usually has several venues in play and tends to sign with the first one that answers properly, at whatever rate, so a well-built grid sent on day four loses to a plain quote sent on day one. If you are choosing a system to hold the grid, the calendar and the quotes together, our buyer's guide to venue management software covers what to look for; Joinways is one of the tools built for that job.





