A request for a dashboard hides three different problems.
When an owner or a general manager says the hotel needs a dashboard, it is almost always one of three complaints, and only one of them is a software problem.
The first is that the figures exist but nobody agrees what they mean. Two people quote occupancy for the same month and produce different numbers, both defensible. That is a definitions problem, and building a dashboard on top of it simply distributes the disagreement faster and in a nicer typeface.
The second is timing. The pack arrives on the fourteenth, describing a month that ended a fortnight earlier, by which point every decision it might have informed has already been taken by default. That is the complaint reporting software genuinely fixes, and it is worth paying for.
The third is that nobody owns the decision the number is supposed to inform. Everyone can see the figure; no one is accountable for acting on it. No software has ever solved that, and buying some tends to postpone the conversation by a year.
| What people say | What is actually wrong | What fixes it |
|---|---|---|
| We have no visibility | The figures sit in four systems and nobody assembles them | A person with an hour a week, then software if that fails |
| The numbers never agree | Two teams are using different definitions of one word | One written definition per number, agreed once |
| We get it too late | The pack lands after the decisions it should have informed | Reporting software, genuinely |
| We have too many reports | Nothing in the pack has changed a decision in a year | Deleting reports, not adding a dashboard |
| I want it on my phone | The owner reads from a distance on a Sunday evening | A one-page summary, not a licence for everybody |
Occupancy and ADR mislead on their own.
Take a 40-room hotel across a 30-night month. That is 1,200 available room-nights, and it is the denominator behind almost everything worth knowing.
In March the hotel sells 960 of them at an average of £90. That is 80% occupancy, £86,400 of room revenue and a RevPAR of £72. In April it sells 720 at an average of £130. That is 60% occupancy—a figure that will worry an owner who asks only about occupancy—£93,600 of room revenue and a RevPAR of £78. April was quieter, looked worse on the number most people ask for first, and earned £7,200 more.
RevPAR, revenue per available room, is occupancy multiplied by ADR. That is why it is the first figure worth having: it cannot be flattered by discounting into a full house, and it cannot be flattered by holding rate into an empty one. Either lever on its own moves one of its two components and gives the other away.
ADR carries its own trap. It is an average of what was sold, never of what was offered. A month with thirty rooms sold at £200 and 690 sold at £127 produces almost the same ADR as a flat month at £130, and the two months need completely different responses. An average that never moves is not evidence of stability; it is evidence that nobody has looked underneath it.

| Measure | March | April |
|---|---|---|
| Available room-nights (40 rooms × 30 nights) | 1,200 | 1,200 |
| Room-nights sold | 960 | 720 |
| Occupancy | 80% | 60% |
| ADR | £90 | £130 |
| Room revenue | £86,400 | £93,600 |
| RevPAR | £72 | £78 |
RevPAR does not know what the room cost to sell.
Two hotels finish April with an identical RevPAR of £78 and identical room revenue of £93,600. The first sells 70% of that through commissioned channels; the second sells 30%. At 15% commission, the first pays £9,828 and the second £4,212. The gap is £5,616 in a single month—about 6% of room revenue—and it appears nowhere on a report that stops at RevPAR.
This is not an argument for switching distribution off. Reach costs money and frequently earns it, and a hotel that fills a soft February through a channel has bought something real. It is an argument for a second column. Once the cost of the sale is visible, a channel decision becomes a comparison rather than an argument about principle.
Payment fees, booking-engine charges and the cost of a cancelled-and-rebooked stay belong in the same column. None of them is large on its own; together they are the difference between a month that looked fine and a month that was.
The industry already has a vocabulary for this. USALI, the lodging industry’s standard for financial and operating reporting, has a mandatory adoption date of 1 January 2026 for its 12th revised edition. A 40-room independent does not need to adopt a full accounting standard. It does need its definitions to stay still from one month to the next, and borrowing them from a published standard costs less than inventing them.

| Measure | Hotel A | Hotel B |
|---|---|---|
| Room revenue | £93,600 | £93,600 |
| RevPAR | £78.00 | £78.00 |
| Share sold through commissioned channels | 70% | 30% |
| Commission at 15% | £9,828 | £4,212 |
| Room revenue after commission | £83,772 | £89,388 |
| Room revenue after commission, per available room | £69.81 | £74.49 |
Six numbers an operator can read in ten minutes.
The test for inclusion is not importance. It is whether somebody could act on the figure within the week. A number that only matters at budget time belongs in the budget, not on a weekly page.
Six is not a magic quantity. The constraint is that the whole set fits on one page and that every line has an owner who could do something about it on Monday morning.
Go deeperHotel performance insightsThis is the set of numbers. Who reads it, who owns each action and how last month’s decisions get reopened is a separate discipline.
↗| Number | The question it answers | What makes it wrong |
|---|---|---|
| Room-nights sold, against the same week last year | Are we ahead or behind on volume | Weeks that do not align—Easter and half term move |
| ADR for the week, net of VAT | Did the volume come from rate or from discount | Complimentary and house-use rooms left in the average |
| RevPAR for the week | Did rate and volume move in the same direction | Rooms out of order counted as available, or not counted at all |
| On the books for the next 30 and 60 nights | What can still be changed | Comparing with last year’s final figure instead of the same lead time |
| Share of the week’s bookings taken direct | Whether the channel mix is drifting | Counting a booking by arrival date rather than booking date |
| Enquiries with no reply after 24 hours | Whether demand is being lost before it is counted | Enquiries arriving in a channel nobody monitors |
Last month is history. On the books is the decision.
Almost every hotel report describes a period that has already finished. Nothing on it can be changed. The one figure an operator can still act on is what is already sold for nights that have not happened yet.
On 1 August a hotel holds 340 room-nights for September. On 1 August last year it held 400 for the September that followed. The useful number is not last September’s final occupancy. It is the 60 room-nights it is behind at the same lead time, and it is available now rather than in October. That figure is what justifies opening a rate, releasing an allocation or spending on a campaign—while there is still a September to sell.
Two words describe this, and both are worth using precisely. Pickup is what was added over a period for a future period. Pace is where the hotel stands compared with the same point last year. Pickup tells you the direction; pace tells you whether the direction is good enough.
The catch is that pace only works if somebody recorded the position at the same point last year. Most hotels discover in their first year of trying that nobody did. Some systems can reconstruct it from booking dates; many cannot, and cancellations usually make the reconstruction unreliable. A single line written down each week costs nothing and settles the question permanently.

Most reporting arguments are definition arguments.
The fastest way to make a hotel distrust its own figures is to let two systems answer the same question differently, both of them correctly.
Take occupancy in that 40-room hotel again. Four rooms are out of order for the whole month, so 120 of the 1,200 room-nights cannot be sold. The hotel sells 885. Against 1,200 available room-nights that is 73.8%. Against the 1,080 it could actually sell, it is 81.9%. Eight points of difference, one month, no error anywhere—and two people who will each defend their number in a meeting.
The same applies to VAT. An ADR quoted gross is not comparable with an ADR quoted net, and a hotel that mixes the two across systems will spend a year arguing about rate positioning it never actually lost. HMRC’s VAT Notice 709/3 also covers deposits and cancellations: a deposit taken and retained when a guest cancels is not automatically outside the scope of VAT, and where that money lands in your reporting is a decision somebody has to make once, in writing.
The CMA’s price transparency guidance pushes on the same seam from the guest’s side, covering mandatory fees, taxes and charges within the price shown. If a mandatory charge appears in the total the guest sees, decide once whether it is room revenue or other income. Otherwise two reports will disagree with each other and with the guest’s receipt.
None of the questions below has a right answer. They have a hotel’s answer, and the value comes from writing it beside the number rather than from choosing well.

| Question | Two reasonable answers | What it changes |
|---|---|---|
| Are out-of-order rooms available? | Yes, they are physical rooms / No, they cannot be sold | Occupancy and RevPAR, by several points |
| Do complimentary and house-use rooms count as sold? | Yes, they are occupied / No, they earned nothing | Occupancy up and ADR down, or neither |
| Is ADR gross or net of VAT? | Gross, as the guest paid / Net, as the accounts record | Every rate comparison the hotel will ever make |
| Is a booking counted on the day made or the day of arrival? | Booking date, for demand / Arrival date, for revenue | Whether a report describes selling or staying |
| Does a cancelled and rebooked stay count twice? | Yes, two transactions / No, one stay | Direct share and conversion, badly |
| Is a no-show charge room revenue? | Yes, it was for the room / No, it is other income | RevPAR, and the VAT treatment behind it |
An average is a good place for problems to hide.
A month closes at 68% occupancy and an ADR just under £111. Read on its own, that is an unremarkable month with no obvious problem in it.
Split it by day of week and it stops being one month. Friday and Saturday run at 90% and £140. Sunday to Thursday run at 60% and £95. The property is two businesses sharing a car park, and only one of them has anything wrong with it. A rate rise applied across the month damages the half that was already nearly full and does nothing for the half that was not.
Four splits usually pay for themselves in an independent hotel: day of week, length of stay, booking source and rate plan. Beyond that, be careful. Segment far enough and every cell contains three bookings, at which point the numbers move for reasons that have nothing to do with the business.
| Segment | Room-nights available | Sold | Occupancy | ADR | Room revenue |
|---|---|---|---|---|---|
| Friday and Saturday | 320 | 288 | 90% | £140 | £40,320 |
| Sunday to Thursday | 880 | 528 | 60% | £95 | £50,160 |
| Whole month | 1,200 | 816 | 68% | £110.88 | £90,480 |
Some hotels need fewer reports, not more.
A rule worth applying once a year: if a report has not changed a decision in six months, it is not information. It is reassurance. Remove it from the pack and see whether anybody asks for it back. Most of the time nobody does, and the half hour it consumed goes somewhere useful.
For a single independent property running one property management system and one booking engine, the honest answer is often that no reporting software is required. The weekly set above, on one page, plus a forward view and a written definition for each number, is a spreadsheet and twenty minutes a week. That is not a lesser solution; for that shape of business it is the correct one.
Reporting software earns its place when a specific piece of manual work exists to be replaced. The list below is deliberately concrete. Notice that none of the items is a desire for better insight—each one is work a person is currently doing by hand, or failing to do at all.
- More than one property, where the same question is asked four times.
- Figures living in three or more systems that do not talk to each other.
- A month-end pack that takes somebody more than half a day to assemble.
- An owner or asset manager reading from a distance who needs the same view monthly.
- A decision that must be made faster than the current reporting arrives.
- A forward history nobody is keeping, where past positions are already lost.
What to ask before buying reporting software.
A demonstration shows charts built from clean sample data on a good day. The questions worth asking are about your data, and about the day one of your sources changes.
Ask them in plain language and treat anything that needs a follow-up call as still unanswered.
- Which systems it reads from, and whether it reads or waits to be sent.
- How often figures refresh, and what a stale figure looks like on screen.
- Whether a definition can be edited, or only chosen from the supplier’s list.
- What happens to twelve months of history when a room type or rate plan changes.
- Whether the numbers export, in what form, on the day you leave.
- Who is told when a source stops sending, and how quickly.
See how a reporting module keeps a definition, a source and an owner beside the number itself.
↗Settle the numbers before buying a dashboard
Answer each item from your own hotel. Anything unticked is a decision to make first—buying reporting software will not make it for you.
checked
Current guidance behind this article
This guide combines primary guidance with practical hotel workflow analysis. Product capabilities and integrations should still be verified against the property’s systems, operating rules and current supplier documentation.
- HFTPUniform System of Accounts for the Lodging Industry
The lodging industry’s standard for financial and operating reporting; the 12th revised edition has a mandatory adoption date of 1 January 2026.
- HM Revenue & CustomsHotels and holiday accommodation (VAT Notice 709/3)
UK VAT treatment of accommodation, including deposits, cancellations and retained payments.
- UK Competition and Markets AuthorityPrice transparency (CMA209)
Guidance on mandatory charges, drip pricing and partitioned pricing under the DMCC Act 2024.



