The numbers behind a change

Where the button appears

Show the numbers sits under a change in the change log, after its sentences. A booking speed rule that measures the whole property (every booking speed starter rule does) is usually read on each night it could act on, and that reading goes under every room type's change on the night. So with such a rule on, most changes have the button, whichever rule made it: a standard rule, a pickup rule, a price you typed, or a rate changed in your system. The evidence describes how the night was booking, not necessarily the rule that made this change.

The button can be missing when no booking speed reading for the night goes under that change, for example when each booking speed rule is switched off, stopped on the night or waiting there, or has nothing new to count yet after a recent change. When the reading shows has more.

A booked so far vs usual rule that is on puts its reading under a change on any room type it changes, whichever rule or price made that change. That is also where you see a night it left alone for too few similar nights. When a change carries both kinds, each block is headed "Booking speed" or "Booked so far vs usual". Read Booked so far vs usual below.

Anyone on the property can open it, whatever their role. Setting a night aside from inside it needs Revenue Manager access or higher.

Click the button and the panel opens with "Loading the numbers from that run…" while MAYA fetches what the run recorded. Then you see one block for each window a booking speed rule read on that night, whether that rule acted or not. With the starter rules that is usually four: the past month twice (once up to now for the rules that raise, once in full days up to yesterday for the rules that cut), the past week and the past day. A rule that counted only from a change still on the night adds a block of its own. Each block is read on its own, so their levels can differ.

To find the block behind a booking speed rule's change, read the first sentence of each. Usually it is the block for the rule's Measured over setting: "In the last 7 days" for a 7-day rule that raises, "In the 7 full days up to yesterday" for one that cuts. But a rule may find the night already raised within that stretch, by itself or a stronger rule. Then it usually counts only the bookings since, and its block begins "The newest raise still on this night's price". A rule that cuts works the same way after a cut, with "The newest cut still on this night's price".

Say "Warm-date bump" raises a night on a Monday, and "Hot-week surge" raised it the Friday before. The surge changes the price by more, so it is the stronger rule, and the bump counts only the bookings since the surge's raise: its block starts "The newest raise still on this night's price" and covers those 4 days, not 30. The bump's raise never moves where the surge counts from. When the surge raises the night again within 7 days of its own raise, its block starts the same way. Two rules that count from the same raise over the same days show the same count. The usual number can still differ: a rule that raises on "at least" a pace reads it over its own whole window, so the bump's says "over a whole month" and the surge's "over a whole week".

If a change turns out to carry no reading, the panel says "No booking numbers were saved for this change." If the fetch fails you see the error and Try again. Close folds the panel away.

The first layer: what arrived, what is usual, and the reading

Three sentences, then sometimes a fourth.

What arrived. "In the last 7 days, 9 bookings arrived for this night, with 40 days still to go before arrival." The stretch matches the rule's Measured over setting. For a rule that cuts it counts full days only, ending yesterday: "In the 7 full days up to yesterday, 9 bookings arrived for this night, ...". When the rule measures some room types only, the count names them: "In the last 7 days, 9 Standard and Deluxe bookings arrived for this night, ...". A booking that holds several rooms counts once. On Mews, each room is its own reservation and counts on its own, unless Count bookings made together as one is on and counts it with others.

What is usual. "By this point, nights like this one usually get about 5 bookings over the same stretch." When similar nights had fewer than 1 booking over that stretch it reads "almost no bookings". The number is what the similar nights had received over the same stretch of their own booking curves, at the same distance before arrival. It is their average, with the highest and lowest left off when there are 5 or more similar nights, and rounded to a whole number wherever it is shown.

The reading. "That reads as Faster Than Normal." This is the level the count and the usual number produce together. Booking speed has the seven levels and where the lines fall.

A note when a fixed check moved the level. Sometimes the numbers point one way and a fixed check keeps the reading nearer Normal. One of three notes then appears:

After the night has already been raised or cut

Once a booking speed rule, or a stronger booking speed or pickup rule that moves the price the same way, has changed a night, it usually counts only the bookings made since that change, so it doesn't count the same bookings twice. A standard rule's change never restarts the count. A stronger rule's change that going live from your current rates took off still counts here, though it is no longer on the price (Counting after a change). The first sentence then names the stretch:

"The newest raise still on this night's price, by the rule behind this reading or a stronger rule, was made on Fri, Oct 2 2026. In the 4 days from that raise on, 3 bookings arrived for it, with 39 days still to go before arrival."

When the raise was earlier the same day, the second sentence reads "Later that day," instead: "... was made on Fri, Oct 2 2026. Later that day, 2 bookings arrived for it, with 42 days still to go before arrival." After a cut it reads "The newest cut still on this night's price", then "In the 3 full days after that, up to yesterday," since a rule that cuts counts whole days from the day after its cut.

On the day of a raise only the bookings that arrived after it are counted, so a burst later the same day is not lost. The "usual" sentence usually compares over that same shorter stretch of the similar nights. A rule that raises on a fast pace (at least Faster Than Normal, Much Faster Than Normal or Surging) is the exception: the bookings since the raise alone have to beat what the similar nights get in its whole window, and the sentence reads "nights like this one usually get about 5 bookings over a whole week".

A change that comes off because of cancellations no longer counts, so the rule goes back to counting from the change before it, or over its whole window. After a price you type, the rule waits its wait, then reads its whole window again, bookings from before your price included.

When there was no history to compare with

A night with no usable similar nights and nothing nearby to read from gets no reading at all, and no booking speed rule is allowed to act on it. The first layer then reads:

"There isn't enough booking history yet to say what is usual for this night." "Booking speed wasn't rated for this night, so rules that watch booking speed left it alone."

You will see this on a change made by some other rule on a night whose booking speed was checked but could not be read.

The second layer: "Which nights were compared?"

Click Which nights were compared? and a short list appears under the first layer. Each line says how the similar nights were chosen. The lines are worked out from the nights themselves, so they always agree with the list under List the nights.

For a rule that cuts, the first line is "A rule that cuts counts full days only, up to yesterday, on this night and on the nights it is compared with alike."

When the night had already been raised or cut, the next line says so: "Once a rule or a stronger one has raised this night, it counts only the bookings made after the newest of those raises still on the price, the rest of that day included, and reads the nights it is compared with over the same days. A weaker rule's raise, or any cut, doesn't move where it starts." For a rule that raises on a fast pace the middle reads "and those alone have to beat what the nights it is compared with get in a whole week" instead. There is a matching line for cuts.

Then, for an ordinary comparison:

• The days of the week. When every night compared is the night's own weekday: "Only other Friday nights were compared, since each night of the week books in its own way." When too few of those matched and other nights of the same kind were added, the line names them: "Too few other Friday nights matched, so Saturday nights were compared too, since they are also weekend nights. Friday and Saturday nights count as weekend nights, the rest as weekday nights." When none of the night's own weekday matched it says "were compared instead". A Wednesday can have Sunday, Monday, Tuesday or Thursday nights added, never a Friday or Saturday. Near a holiday the nights are lined up by the holiday, so their weekday can change from year to year: "Around Independence Day the day of the week changes from year to year, so the nights compared fall on Monday, Wednesday and Thursday." A holiday that always falls on the same weekday, such as Thanksgiving, gets the "Only other" line.
• The holiday or the season. A night near a US holiday reads "This night is near Thanksgiving, so it is compared with the same days around Thanksgiving in earlier years, not the same date." Any other night reads "Only nights in the same season of your history were compared: Peak Season (June 10 through August 31)." When too few nights matched in the season and nights of the same weekday from around the same time of year were added, it reads "Nights in the same season of your history were compared: Peak Season (June 10 through August 31). Too few matched there, so nights within 45 days of the same time of year were added." When none came from the season, it says so and that those nights "were compared instead". Seasons are stretches of your year that book differently, read from your own history, and this panel is the only place they appear on screen: in this line, and in the reasons under each night in List the nights. Which past nights your rules compare with (advanced) has more.
• When the search was widened. "Fewer than 4 nights matched closely, so the search was widened. Check the nights below and set aside any that were not normal." It means fewer than 4 nights matched on the strict rule (same weekday, same season), so MAYA allowed the same kind of night (a Saturday for a Friday, since both are weekend nights) or a nearby time of year. The lines above name what was added.
• Always last. "Closed periods, and any nights you have set aside as not normal, are never compared."

When the reading came from momentum

A night with no similar nights with any bookings on record is read from momentum instead: how nights near it are filling now, against how the same nights were filling a year ago. The list then opens with two lines that say exactly that ("Your history has no usable similar nights for this one, so the usual number comes from booking momentum instead." and "Momentum here means how nights near this one are filling now, compared with how the same nights were filling at this point last year."), and adds:

• "6 nearby nights could be paired with the same nights last year." (or "No nearby night could be paired with the same night last year, so there is no telling whether the pace has changed.")
• "Those nights are filling about 20% faster than they were a year ago." (or "slower", or "at about the same pace as a year ago" when within 5% either way)
• "The starting point was about 4 bookings, taken from how this same night was booking at this point last year (Fri, Nov 14 2025)." (or "taken from the typical pace of nearby nights" when the night itself has no usable history from last year)
• "Momentum is rougher than comparing similar nights, so treat it as a best effort, not a measurement."

Which past nights your rules compare with (advanced) describes momentum in full.

The third layer: "List the nights"

Once the second layer is open, and when there are nights to show, List the nights appears. Click it for one row per night. The nights nearest in time come first, up to 8. For an ordinary night that is usually the same weekday, week after week, from the same season: first any nights of that season that have already passed this year, then the same season last year, then earlier years if there is room.

Three rows from the list for The Harbour Inn's Friday, November 13, 2026:

A row can also read "no history for this night". MAYA has no bookings recorded for that night, usually because it falls before your history begins. It adds nothing to the usual number and does not count toward the 5 similar nights a full-strength reading needs.

Under each date, in smaller type, the reasons it was chosen, joined by semicolons: "a Friday; your Shoulder Season; about a year earlier". The season is your own, so its name on your screen can differ. When the match was loosened, the stricter matches are listed first, and a looser row can read "a Saturday, similar to a Friday; your Shoulder Season; about a year earlier" or "a Friday; a nearby time of year; 2 years earlier". The last reason says how long ago the night was: "earlier this year", "recently", "about a year earlier", "2 years earlier" or "3 years earlier".

A row for a night near a holiday reads like "Thanksgiving 2025; 2 days after the holiday; similar weekend placement". The last part appears when the holiday fell on a similar day of the week that year.

For a momentum reading the similar nights still come first, each reading "no history for this night", then the paired nights, listed on their year-ago date: "3 bookings at this point last year, against 5 bookings now for Fri, Nov 6 2026", with the reason "used to read how the pace has changed since last year". The starting point night reads "4 bookings at this point last year, the starting point for the estimate", with the reason "this same night a year ago".

On the right of each row is Not a fair comparison?. Once you have set a night aside, that spot reads "Set aside. Not used from the next run on." Setting a date aside walks through the form.

Booked so far vs usual

A booked so far vs usual block has the same three layers, one for each point of the day a rule read (read The same point before arrival).

The first layer. "12 of this night's 20 rooms to sell were booked, with 30 days still to go before arrival." When the rule measures some room types only, it names them: "7 of this night's 12 Standard rooms to sell were booked, ...". Then "By this point, similar nights usually had 7 rooms booked." and "That is 5 more than usual: 25% of the rooms to sell." (or "fewer than usual", or "That is the same as usual."). The percent is rounded down, so it never shows more than was there. With too few similar nights: "There aren't enough similar nights to compare with yet: 2 could be compared, and 3 are needed." and "Rules on booked so far vs usual left this night alone."

Which nights were compared? The same lines as booking speed's for the same night, since the nights are the same, then "Each similar night is read at the same number of days before arrival, up to the end of that day, for a rule on ahead." (or "up to the start of that day, for a rule on behind."). When a measured room type wasn't selling yet on some of the nights: "Suite wasn't selling yet on some of these nights, so those nights are read up to tonight's rooms to sell." With enough nights: "Up to 8 similar nights are averaged, each as a share of the rooms selling on it, leaving out the highest and lowest when there are 5 or more."

List the nights. Each night with its rooms by then: "7 of 20 rooms booked by then", or "6 of 18 rooms booked by then, read as 6.7 on tonight's 20 rooms to sell (Suite wasn't selling yet)". A night left out says why: "no history for this night", "left out: none of these room types were selling yet", "left out: too few of these room types were selling yet", "left out: some of its bookings have no booking date" or "left out: most of its bookings were entered after the night". Not a fair comparison? works the same, and a night set aside leaves both conditions.

How long the evidence is kept

MAYA keeps the detail behind a change for 90 days. Within that time the numbers open for any change in the change log. The log reaches back exactly that far: it opens on the 10 most recent runs that changed a price, and Older at the bottom adds the runs before them.