Event Weekend Pricing From Your Own PMS: A Worked Example

RevPARGenius pricing guides · Worked example series

Reviewed by Mark Joefer, Hotel Market Intelligence Researcher · 13 October 2026 · 9 min read

Event nights are where small properties most often price like it is any other Tuesday. The booking comes in early, the calendar fills, and nobody looks at the rate again until the weekend has passed.

This guide uses a worked example, a fictional 40-cabin NZ holiday park, to show four steps any GM can run from a PMS export: find the event nights, check when they sold, set an event floor, and review afterwards.

How do you find your event nights in a PMS export?

Start with the calendar, not the market. Export date, rooms sold, occupancy and ADR for the next 90 nights, then add a column for anything you know is happening: public holidays, school holidays, local festivals, sports fixtures. In the worked example, ten nights carry an event flag.

Taken together, the ten nights ran at 94.0% occupancy and an ADR of NZ$120. The 90-night ADR was NZ$119. In other words, the park charged almost exactly the same on its event nights as on every other night, while the illustrative middle for those nights was NZ$195, 62.5% above the park's rate.

Only one of those labels needs care in real life. NZ Labour Day falls on Monday 26 October 2026, so the long weekend runs 24–26 October. The other flags in this example are synthetic. On your own calendar, if a night stands out and you do not know why, the driver isn't confirmed in your data; check the local events calendar before you price it.

When did the event nights actually sell?

Rate decisions for an event weekend are only useful before the rooms are gone. The second step is to check pickup: how many rooms were on the books 60, 30, 14 and 7 days before each event night, and at what rate.

The worked example includes a separate reservation sample of 580 confirmed bookings. Its median lead time is 14.5 days, with the middle half of bookings made between 6 and 30 days before arrival. A quarter of bookings (24.1%) were made more than 30 days ahead. That sample does not reconcile exactly to the nightly totals, so we use it for timing only.

Most PMS platforms can produce an "on the books" snapshot by date. If yours cannot, save a copy of the occupancy report once a week. Four weekly snapshots are enough to see whether event nights fill earlier than ordinary nights.

How do you set an event floor rate?

An event floor is the lowest rate you will accept on an event night, whatever your pricing rules or channel settings would otherwise do. It stops the event weekend selling at the ordinary weekday rate by default.

Three inputs help set it:

• Your own ordinary-night rate for the same day of the week. In the example, ordinary Saturdays sell at about NZ$122.
• A market reference for that night, on the same search basis. In a live setting this is the market middle, published only when 15 or more properties are priced. In the example it is illustrative only.
• Your break-even occupancy at the new floor, so you know how much occupancy you can give up. Our break-even occupancy check before you raise rates walks through the formula.

Suppose the park set a floor of NZ$150 across its ten event nights, still below every illustrative middle in the table. At 94.0% occupancy and NZ$120 today, break-even at NZ$150 is 75.2%. Put simply, the park could sell about 7.5 fewer cabins a night on those nights and still earn the same room revenue.

The illustration is a sensitivity. It shows the size of the decision, not a promise. If the event nights are already mostly booked when you read this, the floor only applies to the cabins still unsold.

How should you review an event weekend afterwards?

The review is what makes next year's decision easier. Within a week of the event, write down four things in a simple log:

• Final occupancy and ADR for each event night, against the ordinary nights either side.
• When the last room sold. If it sold weeks before arrival, the floor may have room to rise next time.
• Rooms still unsold at the floor. If there were several, the floor may have been too high, or the event smaller than expected.
• Length-of-stay patterns. Did event guests book two or three nights, or just the peak night? That decides whether a minimum stay is worth testing.

The same park's ordinary nights tell a similar story. Our worked example on high occupancy and a flat rate runs the same checks across all 90 nights, so you can compare event nights with the rest of the calendar.

What should you do this week?

1. Export the next 90 nights and add an event column. Include Labour Day weekend (24–26 Oct 2026), Christmas Day (Fri 25 Dec), Boxing Day (Sat 26 Dec) and New Year's Eve (Thu 31 Dec) where they fall inside your window.
2. Compare event-night ADR with ordinary nights on the same day of the week.
3. Check how full each event night is today and how many days remain until arrival.
4. Set a floor for any event night still under 70% sold, and note the break-even occupancy at that floor.
5. Load the floor in your PMS or channel manager so it applies across every channel.
6. Book a 15-minute review for the week after each event.

Frequently asked questions

How far ahead should I set event weekend rates?

Set them as soon as the event is confirmed and before the first bookings arrive. In the worked example, a quarter of bookings were made more than 30 days ahead, so a late rate change would miss a large share of guests.

What is an event floor rate?

It is the lowest rate you will accept on an event night, regardless of what your usual pricing rules would set. It stops event nights selling at the ordinary rate by default while still letting the rate rise if bookings come in quickly.

Should I use a minimum stay on event weekends?

A minimum stay can help when guests want the peak night only and the shoulder nights stay empty. Check your own length-of-stay data first, and test it on one event before applying it everywhere.

What if I do not know why one night is busy?

Treat it as unconfirmed. Check the local events calendar, your tourism board listings and your own booking notes before pricing it as an event, so a one-off group booking is not mistaken for a recurring event.

Will a higher event rate hurt my reviews?

Reviews usually reflect whether the stay matched what the guest paid. Keep the product, the welcome and the cleanliness consistent on event nights, and make sure your direct website shows the same or better value than the booking sites.

Your PMS tells you how full the event nights are. RevPARGenius shows what nearby properties are asking for the same nights, so your floor has a real reference.

Data sources: RevPARGenius worked example (synthetic PMS and reservation data for a fictional 40-cabin NZ holiday park, 90 nights from 14 Oct 2026; market middle column is an illustrative assumption). Public holiday dates: NZ Labour Day Mon 26 Oct 2026; Christmas Day Fri 25 Dec 2026; Boxing Day Sat 26 Dec 2026; New Year's Eve Thu 31 Dec 2026. Analysis run October 2026. Last reviewed October 2026. RevPARGenius is a hotel market intelligence platform. It is not affiliated with any online travel agency or hotel chain.

Research methodology and disclosures: Market figures in this article are calculated by RevPARGenius from room rates publicly displayed on online travel agency (OTA) channels, on one search basis (1 night, 2 adults, 1 room, cheapest offer shown). We publish a market figure only where at least 15 properties were priced. The figures are advertised asking prices. They do not show occupancy, bookings, negotiated corporate rates or revenue achieved. Worked examples marked as synthetic use invented data. This article is general information, not pricing advice: each hotel sets its own rates independently. RevPARGenius and CloseMode are commercially affiliated platforms.