Suggested changes on a rule

The red mark

The mark is a small red circle with an exclamation mark, right after the rule's name in the Name column of the Rules tab. Click it, or move to it with the Tab key and press Enter, and a panel opens under it: a heading, what we found, what we suggest and, if you can change rules, what the change would do to your prices now, with two buttons. How we check this, at the bottom, opens this page. The Escape key or a click outside the panel closes it, and opening another rule's panel closes the first. A screen reader names the mark after the rule: "Suggested change for Slow nights".

A rule has at most one mark, of one of two kinds:

• A cut rule whose recent cuts have not paid for themselves, headed "Recent cuts have not been affecting pace enough to pay for themselves." Read When recent cuts have not been affecting pace enough to pay for themselves.
• A rule that has not acted in 60 days, headed "This rule has not acted in 60 days." Read When a rule has not acted in 60 days.

When a rule could have both, the first kind wins.

A rule with no mark is not a rule that works or fails. We only show a mark when we are confident, and most rules never get one: a cut rule needs many checked nights before we can say anything about its cuts, and a rule that acts now and then is never quiet. There is never a mark on a rule that is off, or on a demo property. We look again once a day, early in the morning at your property, and a mark stays only while that check keeps finding it. Editing the rule or switching it off takes the mark away at once, and any later suggestion is about the rule as it is then. A new name, or a change to only the sold-out or cancellation boxes, keeps it.

When recent cuts have not been affecting pace enough to pay for themselves

This kind is only for rules that cut. A cut lowers the price for every guest who books, the ones who would have booked anyway included, so it pays for itself only when it brings in enough extra bookings to make up for that. We count what each night the rule cut booked in the 14 days after each cut, or the days left before the night when that is sooner, and compare it with how similar past nights booked over the same days. Taken together, over all the nights it cut, when what the cuts brought in falls short of what the lower price cost, and we are confident of it, the rule gets a mark.

The similar past nights are your own: the same weekday at the same time of year, from before your rules started changing your prices, so the comparison is never with nights your rules priced. We also allow for how the night was booking when the rule cut it. A night that is behind often stays behind, so a rule that cuts nights that are behind is compared with how your past nights that were just as far behind, with no price change, went on to book.

A cut made in the overnight run counts from that day. A cut made later in the day counts from the next day. If one of your raise rules raised the price during those days, we stop counting on the day it did. A night is checked about a month after it has passed, once its bookings have settled.

We count each night once, however many times the rule cut it, so this count is not the Fired count. Only nights cut by the rule as it is now count: after an edit, or after a suggested change, the count starts again.

What is left out. These nights are never counted, for the rule or against it:

• cuts made while your property was simulating, or before MAYA was sending prices to your property system (on Mews, it does not send them yet);
• a cut your floor held, so that the price did not move;
• a cut taken off early by a price you typed, an edit to the rule, switching the rule off, or going live from your current rates;
• nights that had another price change on them in the two weeks before the cut, from a rule or a price you typed, and nights another rule cut during the days we count;
• nights that would have filled anyway, where the usual bookings alone take most of the rooms left;
• closed nights, nights with no rooms to sell, and nights cut more than about three months ahead.

A cut that came off by itself, because bookings came in and the night no longer met the rule, or because it sold out, still counts: that may be the cut working.

How sure. One night says very little, because bookings vary a lot from one night to the next. A suggestion needs at least 10 nights it cut, spread over several weeks, and usually many more, and the nights taken together have to say clearly that the cuts fell short. A suggestion about a cut comes only after many nights that rule cut have been checked. A small cut, such as 5%, or a rule that only acts on top of a stronger rule, may never collect enough nights for one.

The three steps

A cut rule's suggestions come in order, each only after the one before:

1. A stricter condition. Only the part of the condition that changes is named, in the words of the Conditions column. We pick the new value from what each night read when the rule cut it, so that about half of those nights would still have been cut. The booking window is never the part we change, nor a booking speed set to exactly one level, nor a part already as strict as it goes, such as booking speed at most Stalled. On a booking speed or pickup rule, a change is not suggested when it would leave this rule, or another booking speed or pickup rule of yours that moves the price the same way, never able to act, because the other one would always act first.
2. A bigger cut, when no stricter condition can be found, or after a stricter one was made and the nights the rule cut since still fall short. The finding ends "The cut may be too small to make a difference.", and the suggestion reads "We recommend a bigger cut: 10% instead of 5%." A bigger cut is not suggested when your floors already hold many of the rule's cuts, or on a cut on low pickup that can cut far-out nights again and again (A cut on low pickup, far out).
3. Turning it off, only after an earlier suggested change was made and the nights the rule cut since still fall short. It needs more checked nights than the first two steps, and the same answer at two checks in a row. The suggestion reads "We recommend turning this rule off.", with Turn it off and Keep it on.

Each step counts only the nights the rule cut after the last change, so each needs new cuts of its own. Turning off is never suggested unless an earlier suggested change was made since you last edited the rule or switched it on. If you switch it back on, we start checking it again from that day. An edit you make yourself starts the steps again from the first; a new name alone does not.

When a rule has not acted in 60 days

A rule that has changed no price in the last 60 days, and has no change on a price now, may get a mark showing the night that came closest to meeting its condition, and a looser condition. Every day we run your rules over every night ahead without changing anything, and keep how close each night came to meeting each rule's condition. The panel names the closest night, the day it was read on, and how far short it was, in the Conditions column's own words.

The looser value is the smallest change that would have met the condition on 1 or 2 nights in the last 60 days, never more, so a quiet suggestion catches at most 2 nights. A quiet rule's first change should be small, so you can see what it does before going further, and a rule whose closest night was far from its condition gets no suggestion. Raise rules get this kind too, and their panel says "raise" where a cut rule's says "cut".

Before the button works, the panel checks which nights the change would move now. If bookings have moved since the suggestion was worked out, and the change would now move the price on more than 2 nights, the button stays off with "Bookings have moved since this was worked out, and this would now change the price on 6 nights. That is more than this suggestion is meant to change, so we will check it again tomorrow."

A rule made stricter on a cut suggestion is never loosened back to where it was before: "Its condition was made stricter on Fri, Nov 20 2026 because its cuts were not paying for themselves, so this stays stricter than the below 70% it had before."

When there is no quiet suggestion. None of these gets one:

• a rule that is off;
• a rule added, edited, or switched off or on in the last 60 days;
• a rule with a first or last night set under Which nights;
• a rule that was waiting on nights in that time, after you went live from your current rates or saved it with Skip price adjustments;
• a rule whose whole condition was met on some night and still did not act: something else held it back, such as its wait, a stronger rule or a ceiling, and a looser condition would not change that;
• a rule with a "Tune ... ?" card open from Get suggestions from my data;
• a rule on a demo property.

A change made while your property was simulating counts as acting. We need a reading on nearly every one of the 60 days, at least 54 of them, and the readings start on the day this check began on your property, so no rule gets a quiet suggestion before it has had 54 days of readings. Only a few rules on a property show one at a time, the smallest changes first.

What the button does

Make that change saves the one change the panel names. It is saved as an edit with Apply price adjustments, so it does what any edit saved that way does. A standard rule keeps each cut where the edited rule is true, at the new amount, and takes it off where it is not. A booking speed or pickup rule starts fresh: its earlier cuts come off, and it cuts again at once, one time, wherever the edited rule is true, even on a night it had cut more than once. It ends the waits that going live from your current rates left on the rule, it ends the Skip price adjustments the rule was saved with (a rule imported from PIE is saved that way, on the nights PIE had already changed), so the nights that Skip kept as they were can change too, and it clears the rule's Stop for this night answers. The note above the button lists every night whose price this changes, and why.

Everything else about the rule stays as it is: its name, its other conditions, its days and dates, its room types, its boxes and its place in the list. No window with a calendar opens, and there is no Skip: the note shows what the window would. It is worked out as the panel opens, with "Checking which nights this changes now." until it is ready, and the button waits for it. Its lines, one for each kind of change, name up to five nights and then how many more:

• "This cuts 3 nights now that it was not cutting: ...": nights the edited rule starts to cut. When the rule was waiting on some of them since you went live from your current rates, the next line says "Making this change ends that wait." When the Skip price adjustments the rule was saved with left some of them as they were, it says "This rule was saved with Skip price adjustments, which left 2 of these nights as they were. Making this change ends that."
• "This makes the cut bigger on 6 nights now: ..." and "This makes the cut smaller on 2 nights now: ...". On a booking speed or pickup rule, a night it had cut more than once gets one cut instead: "An edited booking speed or pickup rule starts fresh, so those cuts become one."
• "This takes the cut off 4 nights now: ...": nights that no longer meet the edited rule.
• "This rule was saved with Skip price adjustments, which kept its earlier cut on 2 nights: ... Making this change ends that.": nights above whose earlier cut that Skip kept on the price, which the change now moves or takes off.
• "It also changes the price on 1 night where another of your rules now acts differently: ...".
• "It also clears your Stop for this night answers on 3 nights: ... The rule can change those nights again."
• "This changes no price now.": no night's price moves.

On a booking speed or pickup rule, the cuts that stay are made again as fresh cuts, so the rule's Fired count goes up by one and its fire log says the rule was edited, so MAYA started it fresh.

If bookings or prices change between the note and your click, and the nights come out different, the panel says "Bookings or prices changed while this was open." and shows the new note: click again to save it. When they come out the same, it saves with no line. Once saved it says, for example, "Saved. Sellable occupancy is now below 80%." or "Saved. Its cut is now 10%.", then closes, and the list reads your rules again, without the mark. If the nights can't be worked out just then, it says "We could not check which nights this changes just now." with Try again, and a save that does not go through says "That did not save. Try again in a moment." Read Messages explained.

Turning it off takes none of its cuts off. Turn it off switches the rule off, as its switch does, and the panel says so first: "Turning it off takes none of its cuts off. They stay on their nights, and it makes no new cuts. To take them off as well, use Delete and choose Delete Rule and Undo Its Changes." There is no note to wait for. Once saved it says "Saved. This rule is off." Read Delete.

Who can do this

Revenue Managers, General Managers and Hotel Admins can make a suggested change or keep it as it is. Everyone else who can see the rules list sees the mark and the panel's words (the heading, what we found and what we suggest), then "Only a Revenue Manager or above can make this change.", with no buttons and no check of the nights. MAYA's own staff looking at your property see the words only, unless they have switched on support mode to change something for you. Read Roles: who can do what.

Keep it as it is

Keep it as it is closes the suggestion and takes the mark away. The rule stays exactly as it is. The panel says when the suggestion can come back:

• After a cut suggestion: "Saved. We will not suggest this again until at least 10 more nights it cuts point the same way." It comes back only at a later check, with at least 10 more checked nights than when you answered, still saying the same.
• After a quiet suggestion: "Saved. We will not suggest this again unless it stays quiet for another 30 days."

Keep it on, under a suggestion to turn a rule off, works the same way. Editing the rule clears your answer along with its checks, and any later suggestion is about the rule as you edited it. A new name, or a change to only the sold-out or cancellation boxes, keeps your answer.

Who did what

A change made with Make that change under the red mark is an edit like any other: the change log shows what it did to prices, not who made it. Neither the suggestion nor Keep it as it is has an entry of its own. MAYA support is the exception, as everywhere: a suggested change or a Keep it as it is that our staff make for you shows as a "Changed by MAYA support" item. Read Who did what.