How Accurate Is Your Forecast? Benchmarking MAPE Across Hotel Departments

The rooms forecast drives the schedule, the purchase order and the owner call, and then it vanishes without a grade. This is the owner's guide to scoring the forecast the way you score RevPAR: which error metric to use, what published error ranges look like, how to catch the bias that sank the 2025 budget cycle, and how to put a dollar figure on every point of error before it lands in the labor line.

The forecast nobody grades

The revenue manager submits a 90-day rooms forecast on the first of the month, the director of finance rolls it into a P&L reforecast, the executive housekeeper turns it into a schedule, the executive chef turns it into a purchase order, and the general manager presents it to ownership. Thirty days later the actuals arrive, everyone looks at the variance to budget, and the forecast itself quietly disappears. Nobody asks how far off it was, whether it missed in the same direction as last month, or which department paid for it.

Forecast accuracy touches labor, purchasing, pricing and owner credibility all at once, and few independent hotels track it with any discipline. The 2025 budget cycle showed what that costs. According to HotStats data published by HotelData.com, US rooms revenue finished the third quarter of 2025 13.2% below budget and 11.9% below budget year to date. Even after hotels reforecast mid-year, rooms revenue still trailed the revised forecast by 4.7% in the quarter and 5.2% year to date. Budgets were too high, and the mid-year reforecasts were still too high. Same direction, twice.

Labor is where the forecast does the most damage, because it is scheduled against the forecast before the actuals exist. Actabl's 2025 Hotel Labor Costs & Trends Report found that from January to September 2025 hours per occupied room fell 13.5% in guest services, 7.1% in housekeeping and 14.6% in management, as operators worked against rising wages and softer revenue. You cannot cut hours to demand you did not forecast correctly. Precision in labor is downstream of precision in forecasting, and precision in forecasting starts with measuring the error.

What follows is a framework for scoring the forecast: which error metric to use and when, what published error ranges look like, how to detect the systematic bias that MAPE hides, and how to translate a point of forecast error into dollars of labor, food, and revenue so the whole executive committee understands what accuracy is worth. It ends with a 90-day implementation plan that a revenue manager and a controller can run without buying anything.

A forecast that is never scored is not a forecast. It is a guess with a spreadsheet around it. The moment you start grading it, it starts getting better, because the people who make it finally know what better means.

Why hotels do not score their forecasts

The reasons are structural, not personal. First, the forecast has too many owners. Rooms belongs to revenue management, F&B covers belong to the outlet managers, banquet revenue belongs to catering sales, and the consolidated P&L forecast belongs to finance. Each group produces its number on its own cadence, in its own spreadsheet, using its own definition of the forecast date. There is no single version to score, so nobody scores any of them.

Second, the forecast is overwritten. The 90-day forecast submitted on September 1 for October is replaced by the one submitted on October 1, which is replaced by the 10-day forecast, which is replaced by the day-of pickup. By the time October actuals land, the original September 1 view no longer exists in the system. You cannot measure the error of a number you did not keep. Plenty of accuracy programs die right here, on day one. The property has no archive of what it said it would do.

Third, the metric is politically uncomfortable. A revenue manager who is scored on RevPAR performance has every incentive to forecast conservatively so that actuals beat the number, and a director of sales who is scored on booking pace has every incentive to forecast group aggressively so that the pipeline looks healthy. Both are rational, and both introduce bias that compounds when finance sums them. Scoring the forecast exposes those biases. That's why it's useful, and why people resist it.

Fourth, most hotels have never seen what good looks like. Nobody has told the GM what a reasonable error looks like for a property like theirs, so there is no target to manage to.

Choosing the right error metric

MAPE, mean absolute percentage error, is the default for a reason. It is intuitive, it is unit-free, and a GM can understand "we were off by 12% on average" without a statistics lesson. Calculate it by taking the absolute difference between forecast and actual for each day, dividing by the actual, averaging across the period, and expressing the result as a percentage. A 30-day forecast that predicts 220 rooms on a night that actualizes at 200 contributes a 10% error for that day.

But MAPE has failure modes that matter in a hotel. It blows up on low-volume days, because dividing a small absolute error by a small actual produces a huge percentage; WFM Labs suggests WAPE or MAE instead where actuals run near zero. A resort forecasting 6 banquet covers on a Tuesday that actualizes at 3 has a 100% error on that day, which will swamp the month. MAPE also treats over-forecasting and under-forecasting asymmetrically: you cannot be more than 100% under, but you can be infinitely over. And, most important for a hotel, a forecast can carry a respectable MAPE while being consistently wrong in the same direction, because the absolute value strips the sign.

Keep MAPE. Pair it with two companions. The first is weighted MAPE, usually written WMAPE or WAPE, which sums the absolute errors and divides by the sum of actuals. It weights busy days more heavily than slow days, which is what you want: being off by 20 rooms on a 300-room sellout night matters more than being off by 2 rooms on a 30-room night. WFM Labs calls WAPE a preferable default wherever volumes vary a lot from interval to interval, which describes most hotel departments. The second companion is bias, sometimes called mean percentage error, which is the same calculation as MAPE without the absolute value. Bias tells you the direction of the error; Demand Planning LLC describes it as persistent deviation that signals a systemic problem rather than random noise. A forecast with 12% MAPE and +9% bias is over-forecasting almost every day. Far more useful than 12% MAPE alone. It's also the pattern the 2025 numbers above point to.

The practical recommendation for a full-service hotel is simple. Report MAPE and bias for rooms at every horizon, report WMAPE and bias for every labor-driving department, and use MAE in units for any outlet or revenue center that regularly sees single-digit daily volume. Present all of them on one page. Forget statistical purity. The executive committee should see the same scorecard every month and know which number to react to.

Accuracy benchmarks by property type

"What MAPE should we hit" depends on the horizon, the department and the property's demand pattern. That answer is useless to an owner, so start with the published ranges. Hospitality Net and Lighthouse both cite the cross-industry rule of thumb that a MAPE under 10% is excellent and 10% to 20% is acceptable, and Hospitality Net notes that many hotels work in the 15% to 25% range. Its examples: a large city-centre hotel with steady business travel may run closer to 10% to 12%, while a 50-room independent in a seasonal destination might find 20% is the best it can do in unpredictable peak months. Cloudbeds says hotels have been told a 15% to 20% forecasting error is "normal."

Academic results run tighter because they measure the model, not the whole process. The classic Weatherford and Kimes comparison of forecasting methods found pickup and regression produced the lowest error on Choice Hotels data, while exponential smoothing, pickup and moving averages held up best on Marriott data. A simple pickup model is a respectable place to start. More recently, an extension of the additive pickup method tested on a 32-room hotel on Elba cut 28-day MAPE from about 23.9% to under 5%. Those numbers come from a clean dataset and a model nobody edited afterward. The ranges below are for the forecast that actually reaches the schedule.

None of those ranges is split by horizon or department, so set your own by horizon once you have history. A few rules of thumb. First, the 7-day rooms number drives the housekeeping schedule, and with most of the business already on the books it should be your tightest; if it is not, look at data hygiene before demand. Second, restaurant covers are the hardest line in the building to forecast because they depend on in-house capture, local walk-in, weather, and competitive openings, none of which the PMS sees. That is why they are the first place to deploy a model with external inputs. Third, banquet definite business should be nearly perfect a week out, and if it is not, the problem is the BEO process, not the forecast.

Detecting bias: the error that MAPE hides

Return to the 2025 numbers. Rooms revenue was 11.9% below budget year to date, and the reforecast was still 5.2% too high. Random error would land over some periods and under others and average out near zero. Missing high on the budget and again on the reforecast looks like bias, and bias has a cause: a growth assumption baked in during budget season, carried into a year that, per Hotel Online reporting the STR and Tourism Economics forecast, produced a 0.3% RevPAR decline, the first non-recessionary decline on record. Nobody revisits an assumption when nobody measures the direction of the error.

The tool for catching this is the tracking signal, borrowed from supply chain control charts and explained by Arkieva. Sum the signed errors over the last several periods, divide by the mean absolute deviation, and watch the result. A forecast with no bias hovers near zero. Arkieva treats a value beyond plus or minus 4.5 as out of control, the point to recalibrate. The tracking signal's real use is that it catches a small consistent bias long before it becomes a large one. A forecast that runs 3% high every month has a MAPE that looks fine and a tracking signal that climbs steadily until someone has to explain it.

In a hotel, bias almost always has a human signature. Revenue managers under-forecast so that they beat the number. Sales directors over-forecast group so that the pipeline looks full. Outlet managers over-forecast covers so that they are staffed for the good night. Finance smooths everything toward budget so that the owner call is calm. None of these people are doing anything wrong by their own scorecard. The forecast accuracy program exists to give them a shared scorecard, and the bias column is where the conversation starts.

Translating error into dollars

The reason forecast accuracy is worth an owner's attention is that every point of error has a cost, and the cost lands in three places: labor scheduled for demand that did not arrive, food purchased for covers that did not show, and revenue left on the table when the forecast was low and the hotel priced or staffed as if demand was soft. The labor cost is the largest and the easiest to compute. Labor is scheduled against the forecast, not the actual, so a high forecast turns into unproductive hours and a low one into overtime and slow service. Deputy's guide to hotel staffing puts it simply: accurate forecasting helps prevent over and understaffing, where overstaffing wastes resources and understaffing means long waits for guests.

The food cost is smaller per point but compounds fast in a hotel with multiple outlets and banquets. The Champions 12.3 study of hotel kitchens found that every dollar invested in reducing kitchen food waste returned about seven dollars in operating savings; across 42 sites, kitchens cut waste 21% on average within a year, and some pilot properties lowered food costs by 3 percent or more. A case study of four Warsaw hotels published in Sustainability found that on average 72.55% of the wasted food was lost in the serving department, buffets and plate waste included, which is exactly the waste that a better cover forecast prevents, because production is set the day before against the forecast.

Here is the worked translation for a hypothetical 250-room full-service hotel at 70% occupancy, $220 ADR, one restaurant, one bar, and a modest banquet operation, with an assumed $48 labor cost per occupied room and an assumed 32% food cost. The exact dollars will differ at every property. What matters is that a controller can rebuild this table for their own hotel in an afternoon and put a number on the accuracy program before the first meeting.

Summed, a 5-point forecast error at this hotel carries somewhere between $290,000 and $425,000 of annual exposure before the credibility line. Even if you only win back a slice of it, that pays for a spreadsheet and a monthly meeting, which is all the first phase requires.

Owners do not fire general managers for missing the forecast. They fire them for missing it in the same direction three quarters in a row and not knowing why. Bias is the number that ends careers, and it is the one number almost nobody reports.

Where AI actually helps, and where it does not

The forecasting vendor market has been loud about machine learning for a decade, and some of the claims are true. The figure everyone quotes comes from a 2017 McKinsey report, which said reductions of 20% to 50% in forecasting errors are feasible with AI in supply chain management. That is a supply chain number, not a hotel one. The mechanism carries over, though: a spreadsheet pickup model uses a handful of variables, while a machine learning model can add weather, local events, competitor rates, search trends and cancellation behavior. The hotel evidence points to where the gains land. In the Elba pickup study, the improved method matched the classic one at 1 to 3 days out and pulled ahead from 7 days, with the gap widening at longer horizons. Close in, most of the business is on the books and a good pickup model is already near the ceiling.

The part vendors say less about is that a model cannot fix a process. Steve Morlidge studied 300,000 forecasts at eight supply chain companies and, as SAS's Mike Gilliland reports, found 52% were less accurate than a no-change forecast. All that process, and more than half the time it lost to repeating the last number. Forecast value added analysis, laid out step by step in SAS's white paper and the IBF series on FVA, measures each step of the process against the step before it and asks a blunt question: did this person or this meeting make the forecast more accurate, or less? In a hotel the steps to test are the DOSM's group adjustment, the GM's gut check and finance's smoothing. Some will help. Some won't. Measure them before you defend them.

So the honest sequencing is this. First, archive and score the forecast you already have. Second, run FVA to find out which steps of your process help and which hurt, and remove the ones that hurt. Third, and only third, replace the statistical core with a model that uses more inputs, because by then you will have a clean baseline to prove it against. Skip to step three and you've bolted a better engine to the same leaky process, which is how hotels conclude that AI does not work. Properties that want help with the modeling layer often find it useful to start with a structured forecasting assessment rather than a software purchase; that is the work our AI Revenue Optimization & Forecasting engagement is built around, and the first deliverable is always the accuracy baseline described in this article.

A 90-day implementation plan

None of this requires new software. It requires a controller, a revenue manager, a shared spreadsheet, and a standing 30-minute meeting. The milestones are deliberately unambitious in the first month, because the archive is the hard part and everything else depends on it.

Two operating rules make this stick. The first is that the forecast is locked at submission. Finance can produce a separate reforecast, sales can produce a separate pipeline view, and the GM can annotate all of it, but the number the revenue manager submitted on the first of the month is the number that gets scored, and it does not change. The second is that accuracy and bias go on the revenue manager's and the department heads' scorecards with a weight that matters. People forecast to whatever they are scored on. Score them on beating forecast and they will sandbag. Score them on accuracy and they will forecast.

What the scorecard should look like

The monthly scorecard fits on one page and answers four questions in order. How accurate was the forecast at each horizon that drives a decision? Was it biased, and in which direction? Which step in the process added or destroyed accuracy? What did the error cost? A workable layout lists rooms occupied, rooms revenue, restaurant covers by meal period, banquet covers, and total labor hours down the left side; shows 7-day, 30-day, and 90-day MAPE or WMAPE with the bias in parentheses across the top; colors any cell outside the target you set; and closes with the tracking signal trend and the dollar translation. Once the archive exists, it's a short monthly job for the controller.

The scorecard changes the conversation at the executive committee. Instead of "why did we miss budget," the question becomes "the 30-day rooms forecast has run 6% high for four months, the tracking signal is at 5.1, and it is costing us roughly $14,000 a month in housekeeping hours; what assumption are we carrying that is wrong?" That is a question with an answer, and it is a question that makes the revenue manager, the controller, and the department heads allies rather than suspects.

The owner call changes too. A general manager who arrives with a forecast that has a track record gets asked different questions than one who arrives with a forecast that has a story.

Frequently Asked Questions