``` RMSE = square root of ( average of (Actual - Forecast)^2 ) ```
Why squaring changes the verdict
Two forecasts, four quarters each, identical average error in dollars.
| Q1 error | Q2 error | Q3 error | Q4 error | MAE | RMSE | |
|---|---|---|---|---|---|---|
| Forecast A | $100K | $100K | $100K | $100K | $100K | $100K |
| Forecast B | $0 | $0 | $0 | $400K | $100K | $200K |
RMSE never falls below MAE. When the two are close, errors are uniform. When RMSE runs far above MAE, the forecast is mostly fine and occasionally catastrophic, and the tail is where your risk lives.
RMSE stays in dollars
RMSE inherits the units of the thing being forecast, so a revenue RMSE is a dollar figure. That makes it directly readable against a decision. An RMSE of $600K on a quarterly forecast means a plan that commits every dollar of forecast revenue will be short by roughly that magnitude in a bad quarter.
The tradeoff is that dollar-denominated scores do not travel. You cannot compare an enterprise team's RMSE to an SMB team's RMSE, and you cannot compare this year's RMSE to last year's if the business doubled. Use RMSE inside a fixed scope and use a percentage metric across scopes.
What drives RMSE up
Timing variance is the usual culprit in B2B revenue, because a deal that closes one week past quarter end contributes its entire value to the error. ORM groups each opportunity with a machine learning model and predicts a close curve for the group, with those curves running from 1 to 80 weeks and most of the expectation landing before week 12. Groups with long, flat curves are the ones that generate the tail RMSE punishes.
The other driver is a model running on stale assumptions. ORM's read is that the most common reason a forecast fails is that something in the business or the market changed and the forecast was built on old assumptions. That failure does not produce steady drift. It produces one quarter that misses badly, which is exactly the shape RMSE is built to expose. Track it alongside forecast accuracy and your broader sales forecasting process metrics.
Frequently Asked Questions
How do you calculate RMSE for a revenue forecast?
Square the error for each period, average the squares, then take the square root. Errors of $0, $0, $0 and $400K across four quarters give a mean square of 40,000 in thousands-squared units and an RMSE of $200K.
What is the difference between RMSE and MAE?
MAE averages the absolute errors and treats every dollar of miss the same. RMSE squares first, so a single large miss dominates. Two forecasts with identical MAE can have very different RMSE, and the one with the higher RMSE is the one that occasionally blows up.
Is RMSE better than MAPE for sales forecasting?
RMSE is better when the cost of a miss rises faster than its size, which is the case for headcount and infrastructure commitments you cannot reverse mid-quarter. MAPE is better when you need a percentage that compares across teams of different revenue scale.
What counts as a good RMSE?
RMSE is in dollars, so there is no portable benchmark. Judge it against the size of the decision it informs. If RMSE exceeds the cost of the marginal hire or campaign your forecast approves, the forecast cannot safely drive that decision.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like root mean squared error (rmse) in forecasting into prescriptive action for your team.
Schedule a Demo