Revenue management, answered

How do I make sure an owner-negotiated or manually set rate doesn't get overridden in the background without me knowing?

Lock the rate at the property level with a hard override flag, then document it in your rate log with an expiration date and the reason. Without that paper trail and a clear internal review step, background rate changes will silently undo manual entries during routine calendar updates.

By Jack Murphy, Head of Revenue Management at UpRev. Running pricing for US vacation rental managers since 2017.

Use a Tiered Rate Authority System

Establish clear internal rules about who can set rates and at what level. Owner-negotiated rates should sit at the top tier and require a named manager to manually release them before any other rate adjustment applies to that date range. This prevents a junior team member or a routine pricing review from unknowingly overwriting a commitment you made to an owner. Document the authority tier in your operating procedures so every team member knows the hierarchy.

Maintain a Living Rate Lock Log

Keep a shared rate lock log that captures the property, the locked date range, the agreed rate, the owner contact who requested it, and a hard expiration or review date. Review this log at the start of every weekly pricing cycle before any calendar changes go out. If a locked rate is approaching its expiration, flag it proactively with the owner rather than letting it lapse silently. A simple shared spreadsheet maintained consistently beats any informal verbal agreement.

Build a Pre-Publish Audit Step Into Your Workflow

Before any pricing update goes live for a property, run a quick conflict check against your rate lock log. If a date range on the update overlaps with a locked rate, that property gets pulled from the batch and reviewed separately. This single step, done consistently, is how experienced revenue managers protect owner relationships and avoid the awkward conversation after a guest books at the wrong rate. Make it a non-negotiable part of your publish workflow, not an afterthought.