Revenue operations
A change window for calendar and pricing updates
Batch rate and availability changes, verify them across channels, and record who approved the change.
Published · 1 minute read
On this page
What to control
- Write the change and the effective date
- Apply it in one controlled window
- Verify each connected channel
- Record the approver and the rollback
Operating context
A rate change that reaches one channel but not another produces inconsistent prices and awkward conversations. Treat calendar and pricing updates as a change with a window, an owner, and a verification step.
Write the change in plain language: the property, the dates, the old rate, the new rate, and the reason. Note the minimum-stay or availability rule that changes with it.
A workable routine
Apply the change in one window, then verify each connected channel. A channel that still shows the old price is a live problem, not a sync delay to ignore.
Record who approved the change and how to roll it back. If a promotion performs badly, the team should be able to reverse it without reconstructing the original settings.
Review and evidence
Review the change after the period ends. Compare bookings, cancellations, and guest questions; keep the result with the rate history.
For related operating guidance, review the [turnover handoff brief](/blog/str-turnover-cleaner-handoff-brief) and the [guest response window guide](/blog/str-guest-message-response-windows). The [CISA cybersecurity performance goals](https://www.cisa.gov/cybersecurity-performance-goals) provide public baseline context for access and account controls.