A GM will sometimes ask for a rate move you do not agree with. "Cut Friday's rate by €20, the comp set is at €185 and we are at €210, we will lose conversion." A practitioner-level revenue manager pushes back. The skill is doing it in a way that respects the GM's authority while protecting the property's revenue strategy.
When to push back
How to push back
Start by agreeing with the GM's underlying concern: "I hear you on conversion. The numbers actually look like this." Show the data — the pace, the comp-set context, the historical realization of the requested move. Offer a counter that addresses the concern without violating the strategy: "Instead of cutting BAR by €20, can we open the advance-purchase to 14-day prior with a 7% discount? That gives the same effective rate to the price-sensitive booker without anchoring our published BAR lower for everyone else."
If the GM insists after seeing the data, execute the move and document the disagreement in the meeting notes: "GM requested BAR cut against forecast recommendation; will track pickup response over next 7 days." This is not passive-aggression — it is the audit trail that protects you when the move underperforms and the post-mortem starts.
When to fold
Some calls are the GM's to make even when you disagree. A request driven by an owner conversation you were not in, a brand-standard requirement, a guest-perception decision rooted in operational context — these are GM territory. Push back once, accept the call, execute well, and revisit if the results validate your original concern.
The pattern over a year
A revenue manager who pushes back 1-2 times per month earns the right to have their analytical view trusted. A revenue manager who pushes back 8 times per month gets reclassified as "difficult." A revenue manager who never pushes back becomes invisible — the GM stops bringing decisions to them and starts making rate calls themselves. The middle ground is the practitioner's territory.