Overrides are useful. They let a revenue manager respond to a specific event, owner request or unusual booking pattern. The problem starts when nobody reviews them.
How overrides accumulate
Each override is set for a good reason, but reasons expire. An event passes, an owner changes their mind, or a market recovers. The override stays in place and keeps overruling the settings that were designed for the portfolio.
A simple governance routine
- Keep a log of every override with its reason, owner and end date.
- Review all active overrides on a fixed schedule, for example monthly.
- Remove or replace overrides that no longer have a clear reason.
- Move repeated overrides into customization group settings instead.
What to record for each override
| Field | Example | Why it matters |
|---|---|---|
| Reason | Local festival, higher demand | Shows whether it still applies |
| Set by | Revenue manager | Creates accountability |
| End date | Last night of the event | Prevents forgotten overrides |
| Review date | Monthly review | Keeps the log current |
The goal is not zero overrides. It is that every override in place today is one you would still choose to set.