You Report for 15 Hours a Week. Forecasting Gets the Leftovers.
You do not run out of hours. You run out of hours in the right place. Below is a measurement you can run on your own calendar this week: three buckets, no new software, and a number at the end that tells you where your forecast actually sits.
Three Buckets Show Where the Week Goes
For five working days, log your time in 30-minute blocks against three buckets. Do not estimate at the end of the day. The gap between what you think you spend and what the log shows is the reason the exercise works.
- Assemble. Pulling, cleaning, and reconciling numbers from the PMS, the channel manager, the RMS, the accounting system, and last month's file.
- Decide. Reading the forecast, changing a rate, briefing sales, approving a campaign, calling the group that has not signed.
- Prove. Building the pack, writing the commentary, presenting what already happened.
Every block goes in exactly one bucket. A meeting where you present numbers is Prove, even when a decision happens at the end of it, because the hours went into preparing the presentation.
Ten Hours Assembling, Fifteen Hours Proving
In the training rooms I run and the hotel groups I work with, the pattern is consistent. The typical day splits into two hours of assembling and interpreting, three hours of deciding and acting, and three hours of reporting.
Across five days, that is 10 hours assembling, 15 hours deciding, and 15 hours proving what already happened. Of 40 hours, 25 produce no decision. If your day runs longer than eight hours, check where the extra hours land. In almost every log I see, they land in the third bucket, because the third bucket has deadlines and the second one does not.
What those 25 hours cost at the profit line is a longer calculation: Read about the full arithmetic in the Profit-Oriented Revenue Management whitepaper.
Forecasting Has No Hour of Its Own
Read the three buckets again. Forecasting is not in any of them.
Assembling is not forecasting. It is the work you do before you can forecast. Proving is not forecasting either. Forecasting lives in the minutes between the two, which means it is never scheduled, never protected, and always the first thing to move when the pack is late.
A forecast built in leftover minutes is a forecast you do not fully trust. An untrusted forecast produces no action. When the forecast produces no action, the only visible proof that the revenue function did anything is the report, so the reporting hours grow again. The loop closes on itself.
Name the Decision or Cut the Report
Take every recurring report you produce. For each one, name a decision that changed because of it in the last 90 days. Not the person who reads it. The decision, with a date.
Reports that pass the test stay exactly as they are. Reports that fail get one of three treatments: a longer interval, a shorter format, or a stop date. Send the stop date to the recipient and ask them to object. Most will not.
The reports are not the problem. Most of them are careful, correct, and well built. Careful work with no decision attached is still an hour you cannot spend on next month.
What the Week Looks Like Rebuilt
Here is a target worth arguing about: 3 hours assembling, 30 hours deciding and acting, 7 hours proving.
Assembling drops only when the numbers arrive already joined, so nobody spends Monday morning reconciling four systems by hand. Proving drops when the report is a byproduct of the forecast instead of a separate build. Neither one drops because you work faster. Both drop because the work is arranged differently, and arranging it runs longer than one post: start with the guide to Forecasting.
Ask for the Hours, Not the Tool
Take the five-day log to your commercial director. Do not open with a request for software. Ask which of the 15 proving hours they are willing to release, and what they expect in return for them.
A log turns a complaint into a proposal. A complaint asks for sympathy. A proposal asks for a trade, and a trade is something a director can approve.
The reallocation only holds when the assembly hours stop coming back every Monday. Demand Calendar is a total-revenue forecasting and profit system for hotels. It sits alongside your RMS and PMS, not instead of them.
Run the log for five days first. Whatever your split turns out to be, you stop arguing about whether you are busy and start arguing about what the hours are buying. The second argument is the only one that changes next month.
