> 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/automation/availability-rules.md).

# Availability rules

Rules that change your rate for you when the rooms you have left to sell cross a level you choose.

An **availability rule** changes your rate for you when your availability crosses a level you choose. Your **availability** is the number of rooms you still have to sell on a date.

Most hotels already work this way in their heads: "if we are nearly full, raise the rate". A rule writes that down once. Revhero then applies it every time, day or night, without anyone having to notice.

You create and manage rules in **Rules Manager**, in the left-hand menu. It is the same screen where you set up [Autopilot](/revhero-docs/automation/rate-recommendations/autopilot.md).

## Every rule is one sentence

A rule says: IF this happens, THEN change the rate. As you fill in the form, the box at the bottom, **In other words...**, writes your rule out as a sentence. For example:

> IF daily **Availability** rises above **\[x]** THEN increase rate by **\[x]%** up to **\[N]** times

Read that sentence before you click **Save**. If it does not say what you meant, change the form until it does.

## Building a rule

### Application Period

Choose when the rule may run.

| Option         | What it means                                                                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Always**     | The rule may run on any date                                                                                                                     |
| **Date Range** | The rule runs only on the dates you pick in **Dates**, and only on the **Week Days** you leave selected. Use **Add Period** to add another range |

### IF — Rule Condition

| Field            | What you set                                  |
| ---------------- | --------------------------------------------- |
| **Rule Type**    | **Availability**                              |
| **Comparison**   | **Drops below** or **Rises above**            |
| **Availability** | The availability level that sets the rule off |

**Drops below** reacts to rooms selling: your availability is falling, so demand is strong. **Rises above** reacts to rooms coming back: cancellations, or a date that is not selling.

### Frequency Limit

**Max Executions** is the maximum number of times the rule can be applied during its active period. It is the brake on the rule. Set it on every rule, so you always know the most a rule can move your rate.

### THEN — Action

| Field           | What you set                                                         |
| --------------- | -------------------------------------------------------------------- |
| **Action Type** | **Increase rate by**, **Decrease rate by** or **Set rate to**        |
| **Value**       | The amount                                                           |
| Unit            | Next to **Value**, choose how the amount is read — for example **%** |

Click **Save** to keep the rule. **Cancel** leaves without saving.

## How rules behave

**A rule starts from your rate as it is now.** Each time a rule applies, it works from your latest send rate, including any change it made before. So two increases of 10% take a €100 rate to €110, then to €121 — not to €120.

**A rule's change stays.** When availability recovers and the condition is no longer true, Revhero does not put the old rate back. If you want a different rate, set and send it yourself on the [Yielding Board](/revhero-docs/setting-your-rates/yielding-board/send-rates.md).

**Max Executions stops a rule.** Once a rule has been applied that many times in its active period, it stops. Changing the rule, or switching it off and on again, starts the count again.

**An expired rule stays in the list.** When a rule's **Date Range** has passed, you can still see it and manage it in **Rules Manager**. It no longer runs, and it does not change any rate.

**Rules and Autopilot are separate.** Your Autopilot settings do not change your rules, and your rules do not change your Autopilot settings.

**Every change is recorded.** Each rate change a rule makes is written to the [Event Log](/revhero-docs/automation/event-log.md), so you can always see what changed and when.

## Examples

| What you want                     | The rule                                                                                       |
| --------------------------------- | ---------------------------------------------------------------------------------------------- |
| Charge more as a date fills       | IF **Availability** **Drops below** 5 THEN **Increase rate by** 10%, with **Max Executions** 2 |
| Respond when rooms come back      | IF **Availability** **Rises above** 20 THEN **Decrease rate by** 5%, with **Max Executions** 1 |
| Only push weekends in high season | The first rule, with **Date Range** set to the season and only **Fri** and **Sat** selected    |

## Good habits

* **Start with one rule** and watch what it does for a week before you add another.
* **Keep Max Executions low.** Because each change builds on the last, a high limit can move your rate a long way.
* **Use Date Range for seasons and events,** so a rule that suits August does not run in November.
* **Check the Event Log** after a busy day, to see which rules applied.

## If something looks wrong

| What you see                                 | What to do                                                                                   |
| -------------------------------------------- | -------------------------------------------------------------------------------------------- |
| A rule changed a rate you wanted to keep     | Switch the rule off or change it in **Rules Manager**, then set and send your own rate       |
| The rate kept rising after each sale         | Lower **Max Executions**, or the **Value**                                                   |
| A rule has stopped applying                  | It has reached **Max Executions**, or its **Date Range** has ended                           |
| Rooms came back but the rate did not go down | That is how rules work: a change stays. Add a **Rises above** rule, or set the rate yourself |
| You are not sure what a rule will do         | Open it and read the **In other words...** sentence                                          |

## Related

* [Autopilot](/revhero-docs/automation/rate-recommendations/autopilot.md)
* [Event Log](/revhero-docs/automation/event-log.md)
* [Sending rates](/revhero-docs/setting-your-rates/yielding-board/send-rates.md)

***

**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%20availability-rules.md) and quote this page: `availability-rules.md`. Say what you expected to find — that is the part we can fix.