Most hotel software can produce forty reports. Most hotel owners read none of them, because forty reports is the same as no reports. Here is the short list — seven numbers, reviewed weekly, that between them describe whether the business is working.
Quick answer (for the impatient)
Seven numbers, weekly, always the same seven. Consistency beats comprehensiveness.
Compare against the same period last year, not last month — hospitality is too seasonal for month-on-month.
Two of the seven are forward-looking. Most owner reporting is entirely backward-looking, which is why problems get found late.
1. RevPAR, against the same week last year
The headline. It combines occupancy and rate into one figure, so it can't be gamed by discounting your way to a full hotel. See the full explanation. If you only look at one number, this is it.
-
Booking pace for the next 30 and 90 days
Rooms on the books for future dates versus the same point last year. This is the forward-looking half of the dashboard, and the one that gives you time to act. RevPAR tells you what happened; pace tells you what's about to. -
Channel mix, and contribution by channel
What share of your business came from each source, and — the part that matters — what each one contributed after commission and processing. Two channels at the same rate are not worth the same. See OTA economics.
Track this as a trend. Direct share falling is a strategic problem long before it's a visible one.
-
Cash position and receivables ageing
Cash in hand, plus what's owed to you and how old it is. Corporate business makes this essential — occupancy can be excellent while cash is tightening, and by the time that's obvious it's urgent. See seasonal cash flow. -
Payroll as a percentage of revenue
Your largest cost, expressed against your revenue rather than in isolation. The absolute figure tells you little; the ratio tells you whether staffing is tracking the business. Watch it especially through season transitions, when revenue falls faster than headcount does. -
Rooms out of order, and for how long
A small number that catches real money. A room out for two days is maintenance; a room out for three weeks is inventory nobody escalated. The duration matters more than the count, and duration is the part no standard report shows. -
Review score and volume, this month versus last
Your forward demand indicator. Deteriorating scores predict falling occupancy at a lag, which means this is an early warning rather than a vanity metric. Volume matters as much as average — see review strategy.
Why seven, and why weekly
Seven because that's about what fits on one screen and can be reviewed in ten minutes. Weekly because monthly is too slow to act on booking pace, and daily produces noise that looks like signal.
The discipline that makes this work is reviewing the same seven every week, including the weeks when everything is fine. A dashboard consulted only when something feels wrong has lost the ability to tell you that something is wrong.
What deliberately isn't here
Occupancy alone (misleading without rate), ADR alone (same), total revenue (hides the mix), and anything requiring manual compilation — because a number that takes someone an hour to produce will stop being produced by week five.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind The Seven Numbers a Hotel Owner Should See Every Monday does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Seven numbers, weekly, always the same seven. Consistency beats comprehensiveness. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: Compare against the same period last year , not last month — hospitality is too seasonal for month-on-month. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: Two of the seven are forward-looking. Most owner reporting is entirely backward-looking, which is why problems get found late. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
What if I own several properties?
Same seven per property, plus the group view. Resist averaging across properties — it hides the one that's struggling.
Should my manager see these?
Most of them, yes. Payroll ratio and cash may be owner-only depending on your role setup.
How far back should I compare?
Same period last year as the primary comparison, with a rolling twelve-month trend for context.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
The point of an owner dashboard isn't visibility into everything. It's noticing a problem while it's still cheap — which needs seven numbers looked at often, not forty looked at occasionally.
See how night audit produces the figures, how break-even frames them, or pricing.
Seven numbers, every Monday. Start free →
Comments