> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/learn-revhero/learn/08-working-with-recommendations.md).
# Lesson 8 · How to use Rate Recommendations
Lesson 8 — accept, modify, override or skip. Learn which one a date needs, how to move a long stretch in one pass, and how to judge whether the recommendations suit your hotel.
{% hint style="info" %}
**In this lesson.** You will be able to choose between the 4 actions on a recommendation, move a stable stretch of dates in one pass, and measure over a month how much to trust the recommendations at your property. **About 35 minutes.**
{% endhint %}
## What a recommendation is
Revhero suggests a rate for every date on your calendar. It is a suggestion, and it becomes a rate on sale only when you send it.
A recommendation takes account of several things about the date, each covered by its own page:
* [Room nights on the books](/revhero-docs/automation/rate-recommendations/what-it-considers/room-nights.md)
* [Pickup](/revhero-docs/automation/rate-recommendations/what-it-considers/pickup.md)
* [Market demand](/revhero-docs/automation/rate-recommendations/what-it-considers/market-demand.md)
* [Demand for your property](/revhero-docs/automation/rate-recommendations/what-it-considers/property-stay-demand.md)
* [Seasonality](/revhero-docs/automation/rate-recommendations/what-it-considers/seasonality.md)
* [Your minimum rate](/revhero-docs/automation/rate-recommendations/what-it-considers/minimum-rate.md)
* [Pricing lead time](/revhero-docs/automation/rate-recommendations/what-it-considers/pricing-lead-time.md)
What it cannot know is everything outside those. A group block you agreed by telephone, a floor closed for maintenance, a festival that has just been announced, a competitor closing for refurbishment — revhero sees none of it. **That gap is your job**, and it is the reason the next section exists.
## The 4 actions
For any date you have 4 choices. The words are the same on the Dashboard widget and on the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board.md).
*Accept, modify, override or skip. Only the first 3 change what you send.*
| Action | When you use it | What happens |
| ------------ | ------------------------------------------------ | --------------------------------------------------------------- |
| **Accept** | The suggestion matches your own view of the date | The recommended rate becomes your send rate |
| **Modify** | The direction is right, but the amount is not | Your edited rate becomes the send rate |
| **Override** | You know something revhero cannot know | Your own rate becomes the send rate |
| **Skip** | You disagree, and want nothing to change | Your current rate stays. Revhero suggests again on its next run |
The distinction worth learning is **modify** against **override**.
**Modify** means you agree with the direction and not the size. The recommendation says up, and you also think up, but €10 rather than €25.
**Override** means you have information the product does not have. The recommendation says down, and you know a conference has just been confirmed in the city.
Writing down which of the 2 you did, and why, is the single most useful habit in this course. It is the record that later tells you whether your overrides were insight or habit.
## Accepting many dates at once
Most of your calendar is unremarkable. Working through 60 ordinary dates one at a time is how people run out of time before they reach the dates that mattered.
1. Click **Bulk Update → Copy From → Recommended Rates**.
2. Choose the period.
3. Click **Apply**. The recommended rate fills the `Send Rate` column for every row in the period.
4. Click **Send** and read the preview as usual.
You still see everything before anything leaves. The speed comes from not opening 60 dates by hand, not from skipping the review.
{% hint style="warning" %}
**Bulk Update respects your yield mode.** Base touches the base only, and Room touches the selected room. If it did not change what you expected, check the mode before you assume it failed.
{% endhint %}
The practical routine is: sweep the stable stretch in 1 pass, then open the few dates from your lesson 6 short list one at a time.
## Read the colours first
The **Rate Recommendation** calendar shows the recommended rate against your current rate for every date, and each date carries a background colour for the direction.
**Read the pattern of colours before you read any number.** A block of dates all pointing the same way tells you something about the period. A single date pointing the other way tells you something about that date. Both are quicker to see as a shape than as 30 figures.
## How much to trust the recommendations
You should not trust recommendations blindly, and you should not dismiss them either. Measure them.
[Daily Performance](/revhero-docs/your-hotels-performance/daily-performance.md) shows what was recommended for dates that have now passed. Once a month, take 20 dates that have gone by and compare 3 things: what was recommended, what you actually sent, and what the date achieved.
After 2 or 3 months you will know something valuable and specific: whether your own changes beat the suggestions, and on which kinds of date.
{% hint style="info" %}
**Watch for a change you make every time.** If you always move the recommendation in the same direction by about the same amount, the cause is usually your price range or your supplement structure, not the recommendation. Fix it in [Pricing](/revhero-docs/setting-your-rates/pricing.md) instead of typing the same correction every morning.
{% endhint %}
## Worked example
The 50-room hotel, on a Thursday morning. Your window is the next 60 days.
| Stretch | What you see | What you do |
| ------------------------------ | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| 42 ordinary midweek dates | Recommendations within a few euro of your current rate | **Bulk accept.** One pass, read the preview, send |
| 8 weekend dates in peak season | Recommendations €15 to €20 above your rate | **Open each one.** Read in the 6 steps from lesson 5 |
| 15 August | €162 against your €145 | **Modify** to €160. The direction is right, and you prefer a round number |
| 22 August | €171 against your €150 | **Override** to €150. A group holds 20 rooms that night, and you want the remaining rooms to sell |
| 5 September | €98 against your €120 | **Skip.** You disagree. A city marathon is that weekend, and you expect late demand |
Five different decisions, and only 1 of them needed a date-by-date review of 60 rows.
Note the last 3 rows. Each one is a decision you can explain in a sentence. Write those sentences down.
## Try it on your own hotel
1. Open [Rate Recommendations](/revhero-docs/automation/rate-recommendations.md) and read the calendar as a pattern. Where do the colours change?
2. Pick a stable stretch of at least 10 midweek dates with small differences.
3. Use **Bulk Update → Copy From → Recommended Rates** on that stretch.
4. Read the preview properly. Run the 3 checks from lesson 7.
5. Send.
6. Now take the 3 dates from your lesson 6 short list. Decide **accept**, **modify**, **override** or **skip** for each, and write 1 sentence saying why.
7. Start a note somewhere — a document, a notebook, anything — headed *dates I overrode, and why*. Add those sentences to it.
Step 7 is the exercise that keeps paying. In 3 months it will tell you whether you are adding value or adding noise.
## Check yourself
**1.** A recommendation says raise the rate by €25. You agree with the direction but think €25 is too much. Which action?
Answer
Modify. You agree with the direction and disagree with the size. Override is for when you hold information revhero does not have.
**2.** You bulk accepted 60 dates and only your base room changed. Why?
Answer
You were in **Base** yield mode, which touches the base only. That is usually what you want, because everything else derives from it. If you genuinely need every combination, switch to Custom.
**3.** Every morning you move the recommendation down by about €10 before sending. What does that pattern tell you?
Answer
Something in your setup is probably wrong rather than the recommendation — most often your price range or your supplement structure. Fix the cause in [Pricing](/revhero-docs/setting-your-rates/pricing.md) rather than making the same correction every day.
## What you learned
* A recommendation is a suggestion. It becomes a rate only when you send it.
* Modify means you disagree about size. Override means you know something the product cannot.
* Sweep the stable stretch in 1 pass, and open only the exceptions.
* Measure the recommendations against your own decisions over a month.
## Next
* [Lesson 9 · Min Rate and Max Rate](/revhero-docs/learn-revhero/learn/09-your-price-band.md) — the floor and ceiling that bound every send.
* [Using recommendations in practice](/revhero-docs/automation/rate-recommendations/using-in-practice.md) — the daily reference.
* [Autopilot](/revhero-docs/automation/rate-recommendations/autopilot.md) — for when you are ready to let revhero apply recommendations on the dates you allow. It is off until you turn it on.
***
**Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20learn%2F08-working-with-recommendations.md) and quote this page: `learn/08-working-with-recommendations.md`. Say what you expected to find — that is the part we can fix.