Checking what MAYA found

How you get here

The review opens on its own at the end of the five questions, or from the progress page once there is something to look at. It also opens from the dashboard banner (below), and after Get suggestions from my data on the Rules tab. You can open it directly at maya-rms.com/onboarding/review.

The cards come from the history import. MAYA reads your history twice on a first import: once after the first three years are in, and again once every year is in. If the review is open when the second read finishes, the cards refresh: one can be sharpened, added or taken away.

Anyone on the property can open the review and read it. Answering a card needs a Revenue Manager, General Manager or Hotel Admin. Below that, pressing any card button shows "Only a Revenue Manager or above can answer this.", and the card stays. The "Is … actually a room?" card, and the room count strip's ticks, need a General Manager or Hotel Admin: below that they are greyed out, with a ? that says who can.

Screen one: does this match reality?

The first screen is headed "First: does this match reality?". It appears only when there are data-check cards waiting. Each card is a question with two buttons, or a single Got it when there is nothing to answer.

At the bottom, Continue to recommendations. The small print under it says that anything you skip stays available later. That is true: an unanswered card waits for you.

"Were you closed …?"

MAYA found at least 14 days with no rooms booked, with the property open in the 30 days before and the 30 days after: something booked on at least a quarter of those days, so a property open only at weekends counts as open. The stretch before your first ever booking is not a closure, and neither is a gap that runs up to today.

A closure can hold a stray booking (a comp, a staff stay, a contractor, a test): up to 7 nights in a row, each with no more than a quarter of the rooms you have booked on a usual night (two rooms at least), as long as at least 85% of the stretch's days are empty. A stray at the very start or end of a stretch, with less than a week of empty days beyond it, is left out of the dates with those days, as long as 14 empty days remain. Any other booked night ends the stretch. So a quiet month with an empty night here and there is never asked about: the nights in between had guests. Two closures with a reopening of 14 days or fewer between them are asked about as two closures, and the reopening is in neither, even when some of its nights were empty. At most three strays or reopenings are looked past in one go.

The card shows the dates, for example "Were you closed Mar 2 to 21, 2025?", and how many days it found, and says when some had a stray booking, for example "We found 20 days in a row with nothing booked except 2 nights". Buttons: Yes, we were closed and No, we were open.

• Confirm: those dates are recorded as a closed period for the whole property. From then on they are left out of every comparison MAYA makes: they are never one of a night's similar past nights, and they play no part in how your seasons are read.
• Dismiss: MAYA never asks about those dates again.

A closure changes nothing about future nights. Your rules still run on every night in the window, closed or not. To keep a future night off sale, close it in your property system.

"Is your property normally closed …?"

The same closure at the same time of year in at least two different years (starts within 21 days of each other) becomes one seasonal card, labelled like "mid-December to mid-February" or "all of August". A year whose closure was split by a short reopening counts as one closure here, from its first day to its last. The card says in how many different years the closure appears. The years need not be back to back. Buttons: Yes, that's our season and No, we were open.

Confirming records every instance it found. When older years reveal more instances of a confirmed season, they are added without asking again. After a Get suggestions from my data run, new instances are proposed as a card instead. Dismissing a season means none of its years is asked about again.

"Is X actually a room?"

Property systems list every bookable space as a room type: event rooms, spa slots, courts, parking. MAYA asks about a type when one of two things is true:

• its name does not read like a bedroom (words like parking, boardroom, meeting, treatment, or a word like spa, court or hall with no bedroom word beside it), or
• it has at least 20 bookings, every one exactly one night, while your property's typical stay is two nights or longer.

A type that is a tiny share of your bookings (under half a percent) at an unusual rate is mentioned as extra weight, never as the reason on its own.

Buttons: Not a room, which takes the type out of your counts, and It's a real room.

• Not a room: the type leaves your sellable occupancy, your RevPAR (revenue per available room: a night's room revenue divided by the rooms you can sell, which sets the calendar's colours) and the room count you are billed for. A rule that changes it still prices it.
• It's a real room: the type is recorded as a room, in your name, and MAYA does not ask again.

Either answer that changes the type also checks the room count you are billed for again straight away. Either answer needs a General Manager or Hotel Admin, since it changes the room count you are billed for. Below that, the card's buttons are greyed out and a ? beside them says "A General Manager or Hotel Admin can answer this." The card stays until one of them does. A Revenue Manager's answer that reaches MAYA some other way is refused with "Only a General Manager or above can answer this." You can change the answer any time on the PMS tab under Room types. Read Room types and rooms out of service.

"Hid duplicate room type"

Two active room types shared the same name once punctuation and capitals are ignored, and one of them had no bookings with a rate (a night at $0, or with no rate, doesn't count). On a first import MAYA hides the empty one straight away, so it does not sit in your occupancy as rooms you cannot sell. The card records this and adds a line beginning "We already did this for you".

Buttons: Good call keeps it hidden. Undo makes the type active again.

After a Get suggestions from my data run, and on any import of a property that is already live, the empty duplicate is only proposed. The card then asks "Hide duplicate room type "Standard"?", with Hide it and Keep it, and nothing is hidden until you press Hide it.

MAYA checks the room types again when you press the button. Hide it hides the type only while it still has no bookings with a rate, your property system still lists it, and another active room type with its name has bookings with a rate; otherwise you see "This room type isn't an empty duplicate any more, so it wasn't hidden." and the card stays. Undo brings a type back only if your property system still lists it; otherwise you see "This room type can't be brought back from here." and the card stays.

"Some X rates look like typos"

For a room type with at least 30 nights on record, its single highest rate is far above what the room type normally sells for: about ten times its usual rate or more. Usually it is a test booking or a mistyped rate.

The card gives the usual (median) rate and, under it, where the highest rate is, so you can look the booking up in your property system: the night or nights it is on (three or more in a row as a range), the reservation number and, when your property system recorded it, the day it was booked, for example "Highest: $4,850 on Apr 10 and 11, 2019 (reservation 4417201, booked Jan 30, 2019)." Several rooms of one reservation are named once, and a semicolon separates one reservation from the next. When the same rate is on more than three reservations, the card names the first three by night and says how many more. When more than 200 room nights carry it, the card says so instead of counting the reservations. On Mews the reservation number is the reservation's long id. The card shows nothing about the guest.

A card raised before these details were read gives only the highest amount. Get suggestions from my data adds the nights and the reservation to a card you have not answered yet.

Buttons: Probably a typo and Those are real. Either answer is recorded and changes nothing else. MAYA never builds a ceiling from a room type's single highest rate.

A mistyped high rate can still matter in one way. The ceiling you gave in the five questions only goes on a room type whose highest rate read so far fits under it. If Suite's $9,999 typo had already been read when you saved a $600 ceiling, your $600 does not go on Suite, whichever button you press here. (If the typo was read only after you saved, Suite got your ceiling like the others.) The Guardrails column on the Rate Simulator tab shows the ceiling each room type has, and so does "Your floors and ceilings" lower on the review: type the ceiling you want in Suite's Ceiling box. Read Floors and ceilings.

"Some stays have no rate"

More than 2% of the stay nights MAYA imported came through with no rate, or a rate of 0. Usually comps or gaps in the data. The card says how many. One button, Got it. There is nothing to fix.

"Some old stays reference deleted room types"

Some stay nights point at room types your property system no longer has. They still count in your history totals but cannot be priced. The card says how many. One button, Got it.

Screen two: recommendations and the finish

The second screen is headed "Recommendations from your data". The heading's small print promises rules and guardrails your history supports. On a first import there are no cards here: the starter rules and your floors and ceilings are built for you (both listed below), and the box reads "No new recommendations this time." Suggestion cards appear on this screen only after Get suggestions from my data. Read Getting suggestions later.

When nothing at all is waiting, the box reads "Nothing left to review" and says your data looks clean. Under it, in small text, "N items already handled" counts the cards you have answered.

Then, in order:

1. The room count strip (next section).
2. On a ThinkReservations property, the rate type MAYA reads your rates from and sends its prices to: "MAYA reads and writes: Best Available Rate", with anything that needs you, and the Rate type list for a General Manager or Hotel Admin. It shows once MAYA has read your rate types. Read Seeing and picking the rate type. Under it, Also moves with MAYA lists your other standard rate types with rates of their own, all ticked when you set up: once you are live each one ticked gets the same change as your main rate on its own rate. Untick any you want MAYA to leave alone. Read Your other standard rates.
3. Your floors and ceilings, a floor box and a ceiling box for every room type that is a room (see below).
4. Your starter rules, in a box headed "While you were here, we built your first pricing rules". The box lists the starter rules your import built, and it stays after anyone on your team runs Get suggestions from my data. While your property is in simulation it ends with Keep them and Remove them and start with a clean slate, which take the place of Finish: both finish the review the way Finish does and take you to your dashboard. Read Your starter rules. On a live property the box shows "✓ Live: your rules are now managing prices" and Finish is below it.
5. On a Cloudbeds property, the line "Have rules in PIE? Import from PIE". The link opens the Rules tab with Import from PIE open, to bring your PIE rules and price limits across from a screenshot. Read Import your rules from PIE.
6. Finish, to go to your dashboard, when the starter rules box is not offering its two buttons: no starter rules, nothing left of them to remove, or a live property. It marks the review as done, and opens the dashboard only once that is saved. It reads "Finishing up…" while it works. Finishing needs a Revenue Manager or higher. Below that you stay on the review and see "Only a Revenue Manager or above can finish the review." with a Go to my dashboard link beside it. The review is not marked done and the banner stays. If the save fails you stay on the review and see "Couldn't finish the review. Try again." Press Finish again. If it reads "Your review couldn't be marked as finished. Reload the page and try again.", reload first.

You do not have to press Finish. Close the page whenever you like and everything you answered is kept.

There is no Go live on the review. The amber strip at the top of the review says your property is simulating, with no button: you go live from the same strip on your dashboard once you finish here. For a General Manager or Hotel Admin its ? says so: "You go live from this strip on your dashboard, once you finish here." Read Going live.

The room count strip

The strip reads "We're counting 4 room types as rooms" and asks whether anything there is not one. One chip per active room type, with its name and how many units it has. A chip is ticked once the type counts as a room, and the number in the question counts the ticked chips. On a property with room groups (on ThinkReservations, its Room Group column), the chips sit in one row per group, each led by the group's name, with room types in no group last under "Other". The question and each chip work the same.

Ticked types are what MAYA divides by for sellable occupancy, and what it counts for the revenue per room behind the calendar colours and for the room count you are billed for. Untick anything nobody sleeps in. An unticked type is still priced if a rule changes it.

• Room types whose name is certainly not a bedroom (parking, boardroom, meeting, treatment and the like) arrive unticked, as MAYA's proposal. Tick one to say it is a room.
• A type nobody has answered for yet shows unticked with a "needs your answer" tag, the same as on the PMS tab. A name that only might not be a bedroom (a "Pool Cabana", a "Spa Deluxe") starts this way. It is left out of your bill and out of the count in the question, and it still counts in occupancy. Tick it if guests sleep there and it joins your bill. If they do not, tick it and untick it again: it is then answered as not a room.
• A tick saves at once, and checks the room count you are billed for again. There is no confirm, and nothing here holds up Finish. On the PMS tab later, ticks wait for Save instead.
• A type you tick while your property is in simulation joins the starter rules you have not edited, to measure and to change. Read Your starter rules.
• Ticking or unticking needs a General Manager or Hotel Admin. Below that the chips show what is saved, greyed out, and the "?" says "A General Manager or Hotel Admin can change which room types count as rooms." A Revenue Manager's tick that reaches MAYA some other way is refused with "This needs General Manager access or higher on this property." On a live property a change re-prices every night of the window from the next cycle, nearest nights first.
• Thirty changes in ten minutes is the limit, per person. The same thirty also cover prices you type or clear by hand and rooms you take out of service in those ten minutes. Past it you see "That's a lot of room-type changes at once. Give it a minute and try again."
• If a tick fails to save it snaps back and you see "That didn't save" with an invitation to try again.

The "?" beside the strip opens the panel the ? beside Room types on the PMS tab opens, less that one's last line about Save: titled "What counts as a room", it says the same as this section, says what the "needs your answer" tag means, and ends "Tick one while you're in simulation and it joins the starter rules you haven't edited." Below General Manager it says what the ticks mean and what the "needs your answer" tag means, and ends "A General Manager or Hotel Admin can change which room types count as rooms."

Your floors and ceilings

Under the strip, a box headed "Your floors and ceilings" lists every room type that is a room, one line each, whether or not it has a limit: its name, then a Floor box and a Ceiling box, each with your property's currency symbol. A box shows the amount set, or reads "none" when there is no limit. Your answers to the five questions and your own rates during the import set them (read Floors and ceilings). On a property with room groups the lines come a group at a time, each group led by its name, in group order with numbers in order, and room types in no group last under "Other". Every room type keeps its own two boxes.

Not listed: a room type that is not a room (unticked on the strip), and one that may not be one until you answer: a name that reads like somewhere nobody sleeps, tagged "needs your answer" on the strip, or one with an "Is X actually a room?" card still open. Answer it and the list reads again: a room joins, a non-room stays out. With no room listed the box is not there.

• Type an amount and leave the box, or press Enter, and it saves. "Saved" shows under the line. There is no confirm.
• Empty the box and leave it to remove that limit: the floor goes back to $1.00, or the ceiling to $99,999.99, which hold nothing back. Escape puts back what is saved.
• An amount has to be between $1 and $99,999.99, and a floor below the room type's ceiling (a ceiling above its floor). Otherwise nothing saves and the line says why, for example "A floor needs to be below the ceiling of $780." or "Type an amount between $1 and $99,999.99, or leave the box empty for no floor."
• Scrolling the mouse wheel or trackpad over a box never changes it: the box lets go and the page scrolls. A box you were typing in keeps what you typed, saves nothing and says "Not saved": click back in and press Enter to save it. A box whose save was refused says "Not saved" too, until it holds what is saved.
• The import never writes over a floor or ceiling you set, changed or removed here, even if it is still reading older years.
• Changing them needs a Revenue Manager or higher. Below that the boxes are greyed out and the box ends "A Revenue Manager or above can change these."
• Up to 120 saves in ten minutes, enough to set both boxes on every room. Past it you see "That's a lot of changes at once. Give it a minute and try again."
• If a save fails, you see the reason, or "That didn't save. Try again."
• The "?" beside the heading says what floors and ceilings do, that you type over one to change it, that an empty box means no limit, and that room types that aren't rooms, or may not be until you answer, aren't listed. On ThinkReservations it adds that the other standard rates MAYA moves aren't held by them.

Going live sends a price no lower than a room type's floor and no higher than its ceiling, even on a night whose own rate in your system sits outside them, so the go-live confirm counts those nights. Read Going live.

The banner on your dashboard

A blue banner appears at the top of the dashboard when your property is connected, the first results are in, there are cards waiting, and you have not finished the review since the newest card arrived. Its heading says your booking history has been read, the line under it says how many things are worth a quick look, and it ends with the link Review →. It shows once per page load. Finishing the review (Finish, Keep them or Remove them and start with a clean slate, as a Revenue Manager or higher) clears it until a newer card arrives, for example from the second read of your history.

Coming back, and changing an answer

You can leave the review at any point and come back through the banner or the review's own address.

Answered closure cards, "Is X actually a room?" cards and duplicate cards are not asked again. Cards about typos, stays with no rate and deleted room types can come back after Get suggestions from my data, because each read is a fresh look. A typo card can also come back at the second read of your first import, if the older years hold an even higher rate for that room type.

What you can still change:

If a card answers itself with "Finding was already resolved", a colleague or another tab got there first, and the list refreshes. If it says "Only a Revenue Manager or above can answer this.", your role is below Revenue Manager, so the card cannot be answered from your login and it stays. Ask a Revenue Manager or above to answer it. Read Messages explained.