Your GM does not need another dashboard before the revenue meeting.

Most hotels do not need another place to look at numbers.

They need a better way to arrive at the decision.

A typical commercial meeting can already have more than enough information available:

• PMS reports
• pace and pickup exports
• RMS recommendations
• channel production
• web analytics
• media performance
• CRM activity
• market or rate intelligence
• restaurant or ancillary reporting
• somebody's spreadsheet that explains the other spreadsheets

The problem is not scarcity.

The problem is that the meeting often begins before the reporting work is finished.

Someone asks why pace moved. Another person opens a different date range. Marketing has campaign results but not the rate context. Revenue has the rate context but not the landing-page result. The GM asks whether the movement is material. Nobody is sure whether the owner saw the same version.

Twenty minutes disappear before the team reaches the first real decision.

That is not a meeting-efficiency problem.

It is a briefing problem.

A dashboard answers “what can I inspect?”

A brief should answer:

What changed, what matters, what is supported by evidence, and who owns the next action?

Those are different jobs.

Dashboards are useful because they allow exploration. A skilled revenue manager may need to move between segments, dates, room types, channels and market views to understand what happened.

The GM usually does not need the entire exploration surface at the start of the meeting.

The GM needs the result of the exploration, with enough evidence to challenge it.

That is the distinction.

A good commercial brief does not hide the source data.

It stops forcing every person in the room to reconstruct the source data independently before a conversation can begin.

The brief should be shorter than the meeting.

This sounds obvious. It is surprisingly easy to violate.

If the “brief” contains every KPI because somebody might ask about it, it has become another report.

A useful brief is selective.

It should usually contain five types of information.

1. Material movement

Not every change deserves a meeting.

The brief should identify the movements that are large enough, unusual enough or commercially important enough to require attention.

Examples:

• pace has weakened in a period that was expected to build
• direct contribution is falling while total demand remains healthy
• one source market is replacing another at a higher acquisition cost
• a high-value package has traffic but weak booking completion
• a daypart or outlet is carrying activity but not contribution
• cancellations changed enough to affect the remaining pricing decision

The definition of material should be explicit.

Otherwise “interesting” becomes whatever somebody noticed five minutes before the meeting.

2. Evidence

Every important sentence should be challengeable.

If the brief says:

Direct performance weakened because paid traffic quality deteriorated.

The team should be able to see what evidence supports that statement.

If the evidence only proves that direct bookings fell and paid traffic also changed, the sentence is too confident.

The correct language may be:

Direct bookings fell while paid traffic mix shifted toward lower-converting sources. The available data supports a traffic-quality investigation but does not prove causation yet.

That is less impressive prose.

It is better commercial reporting.

3. Decision

The brief should identify where a decision is required.

Not every observation needs an action.

Some things should simply be watched. Some need investigation. Some need a rate decision. Some need marketing to stop spending. Some need reservations to change response behaviour. Some need no action because the movement is expected and already understood.

A report that turns every red number into a task creates noise.

A briefing system should distinguish information from decision.

4. Owner

“Team to review” is not an owner.

Commercial issues disappear when ownership is collective enough that nobody feels late.

The brief should identify the accountable role for the next step.

That may be revenue, marketing, e-commerce, reservations, sales, F&B, finance or the GM.

The role can delegate the work.

The ownership should not disappear with the delegation.

5. Follow-through

A good brief remembers what the last meeting decided.

If the team agreed to:

• change a restriction
• rebuild a landing page
• stop a campaign
• call a specific segment
• correct parity
• test an offer

the next relevant brief should show whether that action happened and what changed afterwards.

Otherwise the organisation produces the same insight repeatedly and calls it analysis.

Different roles need different briefs from the same evidence.

One of the worst reporting habits in hotels is taking the same document and changing the distribution list.

A GM, revenue manager, owner and e-commerce lead are not asking the same question.

General Manager

The GM usually needs:

• what changed materially
• the financial or operational consequence
• what needs a decision today
• what is unresolved
• who owns it

The GM should be able to move into the source when needed without being forced to live there.

Revenue and commercial leadership

This view can go deeper on:

• pace
• pickup
• segment mix
• channel economics
• restrictions
• pricing decisions
• demand periods
• cancellation behaviour
• forecast risk

The purpose is still the decision, not the density of the page.

Owner or asset team

The owner view needs a different discipline.

It should separate:

• fact
• management interpretation
• action
• risk
• result of prior action

Owners do not need every operating detail.

They do need enough evidence to understand whether management is reacting intelligently to the result.

Marketing and e-commerce

This view should connect activity to commercial conditions.

Campaign performance without availability, price, offer, channel cost and booking-path context is incomplete.

A campaign can have a healthy cost per click and still be commercially wrong for the dates it is filling.

The brief should make that connection visible before the next media budget is approved.

The brief should separate fact from explanation.

This is one of the most important controls in the whole system.

A number is not an explanation.

An explanation is not a number.

The brief should make the distinction visible.

For example:

Fact: Direct conversion fell from the prior comparable period.

Fact: Mobile booking-engine entry remained stable.

Fact: Booking-engine completion fell.

Inference: The main leak appears to be after engine entry rather than before it.

Decision: Review mobile checkout failure and rate/policy presentation before adding more traffic.

That chain is useful because each step can be challenged separately.

When the explanation is written as if it were the source fact, bad confidence enters the meeting very quickly.

AI belongs in the explanation layer, not in the source numbers.

This matters more now because language systems can produce a very convincing commercial paragraph from weak evidence.

A safe architecture separates the work.

Deterministic layer

The system should calculate:

• dates
• periods
• totals
• variances
• ratios
• thresholds
• exceptions
• source references

through defined rules and approved data.

Language layer

A language model can help:

• make the exception easier to read
• summarise the evidence
• structure the brief by role
• draft a clear question for the meeting
• identify missing context that requires a person

It should not invent a number because the source was absent.

It should not turn correlation into causation because the sentence sounds better.

And it should not approve the commercial action.

The accountable person still owns that decision.

Unknown is a valid output.

Commercial reporting gets dangerous when completeness is treated as more important than truth.

If the source file is late, say it is late.

If two sources disagree, surface the disagreement.

If attribution cannot prove which campaign produced a booking, do not distribute the booking across campaigns to make the report look complete.

If a reason is plausible but not supported, label it as a hypothesis.

A system that says “unknown” at the right time builds more trust than one that always produces an answer.

A useful daily brief and a useful weekly meeting pack are not the same thing.

The daily rhythm should be short.

It may focus on:

• material pace changes
• urgent exceptions
• today and near-term demand
• failures in direct conversion
• parity or availability issues
• actions that are late

A weekly commercial pack can go wider:

• segment movement
• channel economics
• campaign contribution
• forecast movement
• rate strategy
• owner-relevant risks
• action outcomes

Monthly owner reporting changes again.

The mistake is not having multiple rhythms.

The mistake is rebuilding the commercial truth independently for each rhythm.

The goal is one evidence layer, not one document.

This is the product principle behind Katalyst Brief, the working public name for Katalyst's hotel commercial briefing and evidence system.

The product is being designed so the PMS, RMS, CRS, analytics platform and source reports continue to own the facts they are supposed to own.

Katalyst Brief sits above those sources and turns approved inputs into role-specific briefs, exceptions and follow-through.

It is not an RMS. It does not become the pricing authority. It is not an autonomous AI revenue manager.

And it is not being presented as a live production hotel deployment today. The current stage is platform foundation.

The public Katalyst Brief product page keeps those boundaries explicit.

What should happen before the next revenue meeting

Try this without buying anything.

Before the meeting, ask one person to prepare a single page containing:

1. The five most material commercial movements.
2. The evidence behind each one.
3. What is fact versus inference.
4. The decision required, if any.
5. The accountable owner.
6. The unresolved actions from the previous meeting.

Then run the meeting from that page.

Open the dashboards only when the discussion needs deeper evidence.

If the meeting becomes shorter and the decisions become clearer, the organisation did not have a dashboard problem.

It had a briefing problem.

For the wider systems principle, read Hospitality systems fail at the decision, not the software.