In plain words
If a past night MAYA compared with was not a normal night (a festival, a buyout, a renovation), set it aside. From the next it is left out of every comparison. Say it happens every year and, once reports from two different years agree on about the same date, the window around it is skipped every year.
Where you do it
Open the change log (or Why this price? on a night: Find out why a price changed), find a change with Show the numbers under it, and click it. Open Which nights were compared?, then List the nights. Each past night in that list has Not a fair comparison? on its right. Click it and a short form opens under that night.
There is no page where you type a date in by hand. You set a night aside from the list of nights MAYA compared with, one night at a time. The change log keeps 90 days of runs, newest first, with Older at the bottom for the runs before the newest 10, so this works for any change from the last 90 days. The numbers behind a change walks through the three layers.
The form
The form asks "What made Fri, Nov 14 2025 not a fair comparison?" and offers a dropdown, Choose a reason…, with twelve reasons. Pick one, choose how far it should reach where that choice is offered, and click Set this date aside. Never mind closes the form without saving. While it saves the button reads Saving….
| Reason | Choices it offers |
|---|---|
| Holiday Not on MAYA's List | this date, every year, seasons |
| Local Event or Festival | this date, every year, seasons |
| Sporting Event or Tournament | this date, every year, seasons |
| Conference or Convention | this date, every year, seasons |
| Renovation or | this date, seasons |
| Utility or Amenity Outage | this date, seasons |
| Group Buyout | this date only |
| Nearby Competitor Closed or Sold Out | this date, seasons |
| Severe Weather | this date, every year |
| Road, Transit, or Flight Disruption | this date only |
| Booking Data Looks Wrong | this date only |
| Other | this date, every year, seasons |
Other needs a few words in the box that appears ("Tell us in a few words what happened"), up to 300 characters. When a reason offers only "this date", no choices are shown and the date is set aside on its own.
A property keeps up to 500 nights set aside. At 500 the form says "This property already has 500 nights set aside. Undo some first." Only a past night from the last 3 years can be set aside, the nights MAYA compares with.
The three choices
When a reason allows more than one, its choices appear (two or three, as the table shows). The first is selected, and each one does everything the one above it does.
Just set aside this one date (recommended). This night stops being used in comparisons, and in the reading of your seasons, from the next . It is never treated as a pattern that repeats.
This happens every year around this time. The night is set aside now, the same as above. On top of that, MAYA counts it as one report of a yearly pattern. Once it holds reports of the same reason, at about the same time of year, from 2 different years, it leaves a window of 5 days either side of that point out of comparisons every year.
This should also change how our seasons are read (advanced). The night is set aside now, and it counts toward the yearly pattern too. On top of that, once it holds reports at this level from 3 different years, the same window is also left out when MAYA reads your seasons (the stretches of your year that book differently). One correction can never change how your seasons are read on its own.
Two things about counting years. A report counts as one year however many nights it covers, so a renovation you flag on three nights is one year of evidence, not three. And reports older than 3 years stop counting.
What changes, and when
From the next (about every five minutes) the night is left out of every comparison and out of the reading of your seasons. Any or booked so far vs usual rule that is checked from then on compares against the nights that remain, so the "usual" number for a night can move. Both conditions leave a set-aside night out, so one set-aside night changes both.
If setting a night aside leaves fewer than 5 compared nights, the reading is held within one step of Normal, so a rule waiting for Much Faster Than Normal, Surging, Much Slower Than Normal or Stalled will not fire on it. A compared night that shows "no history for this night" does not count toward the 5.
MAYA does not go back and redo prices. A price a rule already set stays until that rule next acts, or its change comes off in the usual way.
Once you have set a night aside, its row in the evidence list reads "Set aside. Not used from the next run on." A night you have already set aside shows "Set aside" instead of the Not a fair comparison? link, so there is nothing to do twice.
For a reading built from (nearby nights compared with the same nights a year earlier), the night you set aside is the year-ago night of each pair, and the starting point night. That is where a night that was not normal usually sits.
Example: The Harbour Inn sets a Saturday aside
Sam opens Show the numbers under a 25% raise to Deluxe on Saturday, November 14, 2026. In the block for the past week, 10 bookings arrived against about 5 usual: Much Faster Than Normal, the level "Hot-week surge" waits for. The compared nights include Sat, Nov 15 2025 with "1 booking in the same stretch". That was the weekend the coast road was closed. Sam clicks Not a fair comparison?, picks Road, Transit, or Flight Disruption (this date only), and clicks Set this date aside.
The row now reads "Set aside". From the next run, that Saturday is left out. The for Saturday, November 14, 2026 stays about 5: the five Saturdays had 1, 4, 5, 5 and 6 bookings, and with five nights the highest and lowest were already left off the average. But only four compared Saturdays remain, so the reading is now held within one step of Normal. The same 10 bookings would now read Faster Than Normal, short of what "Hot-week surge" waits for. The raise it already made stays, and it counts only bookings made since that raise anyway, so the difference shows on the next Saturday whose comparisons included that night.
Your corrections
On the Change Log tab, under the heading, sits a panel titled Your corrections. Click Show to open it and Hide to close it. Everyone on the property can read it.
Each night you have set aside is one line: the night, then "You told us this date was affected by road, transit, or flight disruption, so we leave it out of comparisons." For Other, your own words appear instead of the reason.
Under those, two kinds of note can appear:
- Still counting. "We have seen this reported in 1 year of the 2 different years we would want before treating "Local Event or Festival" near June 10 as a pattern that repeats every year." The same shape appears for the seasons choice, ending "as a change to how we read the season around here."
- Now applied every year, in amber. "Reports across 2 different years flagged "Local Event or Festival" near June 10, so we now leave it out of comparisons every year." For the seasons choice it ends "out of comparisons and out of our seasonal calculations, every year."
When the panel has nothing in it, a short note explains what it is for.
Undo
Each line in Your corrections has Undo. Click it and the night is compared with again from the next run, unless it sits inside a window still applied every year from your other reports (shown in amber in Your corrections). Any yearly pattern it counted toward is counted again from the reports that remain, so a window applied every year can go back to "still counting".
If nothing is removed, the panel says "Nothing was removed" and adds that it may already be gone, or that removing it needs manager access.
Who can set a date aside
Setting a night aside, and undoing it, needs Revenue Manager access or higher. Everyone on the property, Viewers included, can open the evidence and read Your corrections.
Holidays MAYA does not have
MAYA matches nights around 17 US holidays by their position relative to the holiday rather than by date. It has no other countries' holidays and no local events. When a past night was a holiday or an event MAYA does not have, set it aside with Holiday Not on MAYA's List (first in the Choose a reason… list) or Local Event or Festival, and choose This happens every year around this time. After reports from 2 different years within about 5 days of each other on the calendar, a window of 5 days either side of that date is skipped every year. A holiday that moves more than that from year to year, such as Lunar New Year, Eid or Whit Monday, never builds up to a yearly window: set it aside each year with Just set aside this one date. Which past nights your rules compare with (advanced) lists the 17 holidays MAYA has.
Closed periods are different
A is a stretch you confirmed as closed on the review screen. A card there asks whether you were closed between two dates, or whether your property is normally closed at that time of year. Those nights are left out of comparisons too, and out of the reading of your seasons, without any setting aside. There is no screen to add a closed period by hand, and MAYA does not treat a future closure as closed, so those nights are still priced. Checking what MAYA found covers the closure findings.