How does MASE scale forecast errors, and what does a MASE above 1 mean?
answer
- an error divided by another error
- the benchmark is a copy-forward rule
- the scaling constant comes from training data
- one step ahead, at the seasonal lag
- 1 is the break-even line
basics
~20 sMASE divides the forecast's mean absolute error by the mean absolute error of a one-step naive rule computed on the training data. The result is unit-free, and a value above 1 means the model averaged larger errors than that naive benchmark.
solid answer
~50 sMean absolute scaled error takes the mean absolute error of the forecast on the held-out window and divides it by a scaling constant: the mean absolute error of a one-step naive forecast measured in-sample on the training data. For a seasonal series with period m, that naive rule predicts each period with the value m periods earlier, so the denominator is the average of `|y_t - y_{t-m}|` over the training sample; for a non-seasonal series m is 1 and the rule is "tomorrow equals today". Because numerator and denominator share units, MASE is unit-free and comparable across series measured in pieces, euros or minutes. It stays finite on series containing zeros, since the actuals never appear alone in a denominator. A MASE of 0.7 means the model's average absolute error is 70% of the benchmark's; a MASE of 1.3 means it is 30% worse, which is a strong signal that a tuned model is not earning its keep.
go deeper
Be ready to say that MASE compares your error to a simple copy-forward benchmark's error, and that under 1 is good while over 1 means the benchmark won.
Explain the denominator precisely: the in-sample, one-step, seasonal-naive mean absolute error at lag m, and why sharing units makes the ratio comparable across series.
Raise the mismatch yourself — an in-sample one-step denominator against an out-of-sample multi-step numerator — and say when you would report a same-window skill score instead.
Decide what the portfolio scorecard shows: mean MASE hides the tail, so the share of series above 1 is usually the number that drives investment decisions.
## The problem MASE is built for Two demands pull against each other when you score forecasts across a catalogue of series. You want a number in units so it means something operationally, and you want a number that is comparable between a SKU selling four units a week and one selling forty thousand. Absolute error is interpretable but not comparable. Percentage error is comparable but undefined near zero and unbounded. Mean absolute scaled error resolves this by comparing an error against another error rather than against the data. ## The definition With actuals `y_t` and forecasts `f_t` over a held-out window of h periods, and a training sample of n observations: ``` numerator = (1/h) * sum over the test window of |y_t - f_t| denominator = (1/(n - m)) * sum over t = m+1..n of |y_t - y_{t-m}| MASE = numerator / denominator ``` The denominator is the in-sample mean absolute error of the seasonal-naive rule, which forecasts each period as the value m periods before it. For monthly data with yearly seasonality m is 12; for daily data with a weekly cycle m is 7; for a series with no seasonality m is 1, which makes the rule the plain random-walk naive forecast. Three properties follow directly. The units cancel, so the number is dimensionless. It is finite for any series that is not perfectly periodic, because the denominator is zero only if the naive rule was exactly right at every training point. And it is symmetric in the sense that over- and under-forecasting of the same magnitude cost the same, unlike percentage-based measures. ## Reading the number MASE below 1 means the model's average absolute error on the test window is smaller than the naive rule's average absolute error on the training data. Below 1 is the bar; how far below tells you how much the model bought you. MASE of 0.6 is a meaningful gain. MASE of 0.95 on a model that costs a nightly retraining job is a conversation about whether to ship the naive rule instead. MASE above 1 means the opposite: the model averaged larger absolute errors than a rule that copies the value from one season ago. On a portfolio, the share of series with MASE above 1 is often more informative than the mean MASE, because it counts the series where you are actively losing. ## The subtlety worth raising The denominator is measured in-sample and one step ahead, while the numerator is measured out-of-sample and may cover many horizons. Those are not the same task. A test window that happens to be more volatile than the training period inflates the numerator without touching the denominator, and a multi-step forecast is intrinsically harder than a one-step one. So a MASE of 1.1 at horizon 12 does not literally prove that a seasonal-naive forecast would have beaten your model on that window — it says your model's twelve-step errors exceeded the naive rule's one-step errors during training. If you want the strict head-to-head, compute the benchmark's forecasts on the same held-out window at the same horizons and report a skill score, `1 - error_model / error_benchmark`, where positive means better. Some teams compute MASE with an out-of-sample denominator for exactly this reason; that is a defensible variant, but it is no longer the textbook definition, so say which one you used. Mixing the two across a report makes the numbers incomparable. ## Where it does and does not apply MASE is a point-forecast metric for a series with enough history to estimate the scaling constant. It needs more than m training observations, and it is unstable when the training sample is very short, because the denominator is then an average over a handful of differences. For a brand-new SKU with three weeks of history the scaling constant is noise, and a units-based error plus a stated benchmark is more honest. It also says nothing about uncertainty. A model can have an excellent MASE and prediction intervals that cover far less than their nominal rate, because MASE only ever looks at the point forecast. Distributional accuracy needs a separate score. Finally, because it is built on absolute error, MASE is minimised by forecasting the median of the predictive distribution. If the business cost of being short differs from the cost of being long, a metric aligned with the median is scoring the wrong target no matter how clean its scaling is. ## What a strong answer sounds like State the formula, name what the denominator actually is — in-sample, one-step, seasonal-naive — say that 1 is the break-even line, and then volunteer the caveat that the numerator and denominator are measured on different tasks. That last move is what separates a candidate who has read the definition from one who has reported the metric to a stakeholder.
- Why is the MASE denominator computed on the training data rather than the test window?So the scaling constant is a fixed property of the series, not something that moves with the evaluation window. That makes the same series comparable across models and across reporting periods. The cost is that the denominator is a one-step in-sample error while the numerator may be multi-step out-of-sample, so the two sides measure different tasks and a MASE near 1 needs interpreting rather than reading literally.
- When can MASE be undefined or unstable?The denominator is zero only if the seasonal-naive rule is exactly right at every training point — a perfectly periodic or perfectly flat series — which makes MASE undefined. More common in practice is instability: with only a little more history than the seasonal period, the denominator averages a handful of differences and is mostly noise, so small changes in the training window swing the reported MASE.
- What does MASE not tell you about a forecast?Anything about the predictive distribution. MASE scores the point forecast only, so a model can post a strong MASE while its prediction intervals are far too narrow. It is also built on absolute error, so it is minimised by the median — if being short costs more than being long, MASE is measuring the wrong target and a quantile-aware score is needed alongside it.
saying these in an interview costs you the question
- Says the MASE denominator is the test-set naive error by definition
- Reads MASE as a percentage of the actual values
- Claims MASE below 1 proves the model is production-ready
- Forgets the seasonal lag and always scales by lag 1
- Thinks MASE says something about interval coverage