Who Is Allowed to Say No to Revenue?

Most hotels know who can bring in business. Very few know who can refuse it.

The Monday commercial meeting has one item that matters. A group wants 120 rooms for three nights during what the forecast already shows as a peak week. The rate sits below expected transient ADR, and the request includes a waived meeting room and two complimentary suites.

The sales manager wants it. It closes her quarter. The revenue manager is uneasy, but a forecast is a forecast and the contract is real. The general manager looks around the table. Nobody says no.

Then someone says the sentence that ends most of these discussions: "It's revenue."

The group signs. Five weeks later, the city announces a conference for the same dates. The hotel turns away transient demand at rates the group never came close to paying.

This scene is a composite, but I have sat through versions of that meeting in several markets, on both sides of the table. What stays with me is not that the decision was wrong. Good hotels misjudge demand. It is that nobody in the room had the authority to make a different one.

The bias towards yes

Hotels have a structural bias towards accepting business, and it is easy to understand. Rooms are perishable. Empty inventory creates anxiety. Sales is measured on production, and nobody wants to explain to an owner why the hotel refused money.

So organisations drift into an unwritten rule: if the business is available, take it and adjust later. Sometimes you can adjust. Often you can't. A contracted rate restricts pricing for a year. A discounted account sets an expectation. A large block displaces demand you never get to see. The revenue appears in the report. The opportunity cost never does.

Revenue management has understood displacement for decades, so the idea is not new. What is missing is not the analysis. It is the authority to act on it.

In most hotels, the analysis can say no, but no person can. That makes it a governance failure, not an analytical one. You cannot fix it with a better report. You have to fix it with clearer rights.

The Right-to-Refuse Framework

I use a three-part model: Rights, Test, Ledger. Rights decide who can refuse. The Test decides when they should. The Ledger decides whether they were right.

Part 1: Rights

Every significant commercial decision needs four roles, named in advance and written down.

Propose. Who brings the business to the table? Usually sales, sometimes revenue or distribution.

Refuse. Who can say no, on what grounds and up to what value? Refusal rights should sit with the person closest to the economics, not the person closest to the client.

Override. Who can overturn a refusal? This is usually the commercial director or general manager, and it is where most hotels fail.

Own. Whose results carry the outcome, whichever way the decision goes?

Then set escalation triggers that fit your hotel. Typical triggers are business touching forecast compression dates, agreements running longer than a year, or any single piece of business above an agreed share of a segment's monthly revenue. Below the triggers, the refusal right sits with the functional lead. Above them, the decision goes to a named person.

One rule holds the whole system together. I call it the Override Rule: anyone may override a refusal, but the override is recorded under their name, and they own the outcome.

This does not stop senior leaders from overruling the numbers. It stops them from doing it anonymously. When an override carries a name, it gets made more carefully, and it gets made less often.

Part 2: Test

The right to refuse is dangerous without a shared test, because authority without criteria turns into personality. Four questions are enough.

1. What does the hotel actually keep? Not the headline rate, but the net value after commissions, concessions, complimentary rooms, space waivers and servicing cost. A strong rate with a heavy concession stack can be weak business.

2. What better demand could it block? This is displacement, asked honestly and asked early, against the forecast rather than against an empty calendar.

3. Which freedom does it consume? As I argued in the previous edition on commercial optionality, every commitment spends some rate, inventory, customer, channel or capacity freedom. The question is whether the price covers what is being spent.

4. What would make us regret accepting it? Name the failure condition before signing: a compression week, a concentration threshold, a rate the market starts quoting back. If you can describe the regret clearly, you can usually price it.

The Test has three outcomes, not two: accept, reshape or refuse. In practice, most commercial refusals should become reshapes. That means different dates, a shorter term, a rate floor, fewer concessions, or an attrition clause that protects the forecast.

The best "no" is usually a counter-offer. A hotel that can only say yes or no will say yes far too often, because refusing outright feels too costly. A hotel that can reshape rarely needs to refuse at all.

Part 3: Ledger

This is the part almost no hotel has.

Every hotel tracks the business it accepts. Almost none tracks the business it refuses. So nobody learns whether its refusals were wise, timid or reckless, and each Monday meeting starts from instinct again.

The Turn-Down Ledger records every significant piece of business the hotel refuses or reshapes.

• the opportunity and its value;

• the dates and inventory requested;

• which Test question it failed;

• the alternative demand the hotel expected instead;

• the name of the decision owner;

• what actually happened.

Review it every quarter, as a learning mechanism rather than a way to assign blame. From it comes one number: Refusal Accuracy. This is the share of reviewed refusals where the protected inventory, rate or terms went on to produce more net value than the business the hotel turned away.

Read the number with judgement.

Very high Refusal Accuracy usually means the hotel is refusing only the obvious cases. It is being timid, and it is still saying yes to marginal business it should reshape.

Low Refusal Accuracy means the hotel is refusing on instinct or on optimistic forecasts, and it is leaving real money behind.

The goal is not a perfect score. It is a score honest enough to improve the next decision.

Incentives decide whether rights are real

None of this works if the incentives punish the people exercising the rights.

If sales is paid almost entirely on volume, every refusal costs someone their bonus, and the refusal right exists only on paper. If revenue is judged only on rate, it will resist valuable base business. People are not being irrational. The system is producing the behaviour it was designed to produce.

So the Right-to-Refuse Framework needs one protection. A refusal or reshape made on the agreed Test, and recorded in the Ledger, should never count against the person who made it. Where the Ledger later shows the refusal was wrong, the lesson belongs to the decision model, not to the individual's scorecard. Otherwise authority is theoretical, and the old rule returns: take the business.

What changes when refusal becomes a right

Hotels that make refusal a right see three shifts, and none of them is dramatic.

Commercial meetings get faster. Everyone knows who decides, and on which test.

Peak inventory stops being sold before anyone has checked its alternatives.

The Ledger builds judgement. After a year, the hotel knows which kinds of business it misjudges, whose overrides tend to be right, and where its forecasts are too optimistic. That knowledge compounds in a way no single good decision can.

The bigger shift is cultural. Once someone can say no, the word "yes" starts to mean something. Salespeople bring better-shaped business because they know it will be tested. Revenue managers argue with evidence instead of discomfort. General managers override less, and with more care, because their names are on the page.

The principle

The strongest commercial organisations are not the ones that capture the most available revenue. They are the ones that know why they accept what they accept, and who is allowed to decide otherwise.

Revenue generation asks what we can sell. Commercial leadership asks what we should sell, on what terms, and at what cost to the business we will never see.

So the next time someone in your commercial meeting says "It's revenue", don't argue. Ask the question the Right-to-Refuse Framework was built for.

Who in this room is allowed to say no, and would they be protected if they did?

If nobody can answer, the hotel doesn't have a commercial strategy yet. It has a habit of saying yes.

Revenue follows clarity.