Start with your own booking situation
The best starting question is simple: what is happening for these stay dates at this property?
Before changing a rate, look at the information your team has recorded. You do not need to turn the review into a finance lecture. You need enough context to make a responsible next decision.
Look for:
- The rooms left to sell for the dates you are reviewing.
- Whether bookings are arriving earlier, later, or at a similar pace to recent weeks.
- Which stay dates are filling, and which remain quiet.
- The booking sources that are bringing confirmed stays.
- Cancellations, date changes, or repeated guest questions that affect the real availability picture.
- Any property event, local holiday, group stay, or maintenance work already known to the team.
This is different from asking, "What is the hotel next door charging tonight?" A nearby rate can be useful context. It cannot explain the other property's room mix, guest type, booking pace, policies, or remaining availability. It also cannot tell you what your own guests are seeing as they decide.
Do not let discounts make the decision for you
A discount can be a deliberate move. It can also become a reflex when the team feels nervous about empty rooms.
The problem with a blanket discount is not that lower prices are always wrong. The problem is that it removes the question the hotel needs to answer: what changed, for which dates, and what are we trying to learn?
For example, a manager may see that a weekday has many rooms left to sell. Instead of lowering every room type for every future date, they can decide whether the issue is limited to that stay period, whether the room information is clear, whether a particular channel needs attention, or whether the current price needs a cautious test. The point is to make one decision that has a reason.
Write the reason down in plain language. "We changed these weekday rates because the next two weeks remain quiet after reviewing recorded bookings" is more useful than "market adjustment." Next Friday, the team can check what happened without relying on memory.
Run a short weekly room-rate review
A useful review can take place at the same time each week, with the person who can change rates and the person who understands current bookings. It does not need a complicated meeting.
1. Pick the stay dates that need attention
Start with the dates that have a real decision attached to them. They may be close to arrival, unexpectedly quiet, filling faster than expected, or affected by a known event.
Do not review every future date just because a calendar exists. A focused review helps the team see the difference between a rate decision and an administrative habit. For market context, read the Bali tourism figures with their limitations, then check the dates and rooms at your own property.
2. Check the booking record before the price
Confirm that the team is looking at the current picture. A room held in a notebook, an unrecorded direct booking, or an unresolved booking change can make the availability picture misleading.
This is where the basic daily discipline matters. A property management system records bookings. A channel manager handles a different job: helping manage availability and rates across channels. If your team is deciding which system problem it has, read Kiyo's guide to PMS vs channel manager.
For a pricing review, the immediate question is simpler: are the bookings, changes, and room rates that matter to this decision recorded where the team can see them?
3. Name one decision, not five vague ideas
Choose an action that the next review can assess. It may be to keep a rate, revise one date range, review a room type, or pause a planned promotion while the team checks booking information.
Avoid changing a rate, photos, policies, availability, and every channel at once. If everything changes, the team will not know what it is reviewing next week. One clear action is easier to explain at a shift handover and easier to improve.
4. Record the reason and the next check
Add a short note that states:
- The stay dates reviewed.
- What the recorded booking situation showed.
- The rate action chosen.
- What the team will check next week.
This note is not paperwork for its own sake. It protects the hotel from pricing by memory. It also makes it easier for another manager to understand why a rate is there when the owner is away.
Use competitors as context, not as a command
Competitor checks can help you notice that the local market is moving. They are not a substitute for knowing your own property.
When you look at another hotel, ask a better question than "Should we copy this?" Ask whether the comparison is meaningful. Is it the same location, room type, guest expectation, date, cancellation policy, and booking route? If not, it may still be useful inspiration, but it is not a direct price instruction.
The same applies to OTA pages. A public rate may not show every condition attached to the stay. Use it to inform a conversation, then return to your recorded bookings and operating plan.
A simple example of a better decision
Imagine an independent guest house reviewing the next two weekdays. The manager notices there are more rooms left to sell than expected. Before changing anything, the team checks that recent direct bookings and a changed reservation are recorded. They see that the quiet period is limited to those dates, not the whole month.
The team chooses one rate adjustment for those weekdays and records the reason. It does not claim the adjustment will create bookings. At the next review, they check whether the booking pace, guest questions, and remaining rooms changed. If the picture did not improve, the next conversation can consider a different cause rather than repeating the same discount.
That is the habit to build: observe, decide, record, review.
Keep pricing connected to the rest of the hotel
Room pricing does not sit alone. A guest's decision is affected by the room information, policies, booking path, and confidence that the stay will match the description.
If the next question is whether a direct booking path is easy to understand, use the five-minute direct booking path test. If the question is about the cost and role of each channel in the mix, use the guide to OTA costs in Indonesia. Those are different decisions. Keeping them separate helps the team avoid a pricing meeting that tries to solve every commercial problem at once.
This boundary matters for your data too. Booking performance can inform a rate review. It is not the same as profit, cash received, or a guarantee about demand. Treat it as evidence for the next decision, not a verdict on the business.
How Kiyo fits a weekly pricing habit
Kiyo gives the property a practical place to bring pricing and booking-performance work together. Its Revenue workspace includes the revenue dashboard, room pricing, forecasting, channel commission views, and Pickup & Pace in one menu.
The useful part is not a promise that software will choose the perfect price. It is that the team can review its recorded booking picture and room pricing without starting from scattered messages or memory. The workspace depends on the property having the required permission and recorded booking channel and rate data. Forecasts remain estimates, and the figures are not an accounting profit or cash-received report.
The why-Kiyo line is straightforward: when a hotel can see its recorded booking performance and room pricing in the same working area, it can make the next rate decision with a clearer reason.
Your next pricing review
Choose one day next week for the review. Bring the current booking picture, identify the stay dates that need a decision, make one clear action, and leave a note for the next review.
That small discipline is more valuable than copying a price you do not understand. It gives your team a way to learn how this property books, one decision at a time.
Add Kiyo to your preferred sources on Google
