Only used for labelling the chart. The order of the rows is what matters.
Sales, sign-ups, traffic, cost β whatever continuous metric you are trying to predict.
Your first time series tool. Look at what a series is actually made of, extend it with a rule you can say out loud, then find out whether that rule beats doing nothing at all. No parameters to guess, no Python to load, nothing to install.
Every time-series forecast is a concrete rule for extending a historical line into the futureβyet teams routinely deploy complex forecasting software that fails to beat the simplest possible baseline: "next period will equal last period" (or "this month last year"). Forecast Starter decomposes your series into level, trend, seasonality, and noise, projects six foundational forecasting rules side-by-side, and scores them on a held-out backtest window before you graduate to ARX or ARIMAX.
vs. Naive < 1.0), and is it systematically over- or under-forecasting (Bias)?m (e.g., 12 for monthly, 4 for quarterly, 7 for daily) and holdout window sizevs. Naive) is greater than 1.00, the extra complexity made your forecast worse than simply copying the most recent observation.H periods (Step 3 Holdout Backtest) and score predictions against actuals the model never saw.π¬ Read it in plain English: Naive repeats the final observation y_T, Seasonal Naive repeats the same season from m periods ago, Moving Average averages the last k periods equally, and Simple Exponential Smoothing (SES) updates level β_t by blending the latest actual y_t (weight Ξ±) with the previous level (weight 1 β Ξ±).
π¬ Read it in plain English: Trend + Seasonality extends a linear time trend Ξ²Μβ + Ξ²Μβt and adds the repeating seasonal index Ε for that month/quarter, while the Holdout Backtest scores accuracy over H hidden periods relative to the Naive benchmark.
Four series, each one teaching a different answer to "which method should I use". Start with the first β it is the one where the cleverest method loses.
A CSV with one column of dates or period labels (ordered chronologically) and one continuous numeric column (interval/ratio scale: revenue, units, subscribers, CPC), with no missing periods in the middle.
Drag & drop a CSV (.csv, .tsv, .txt)
First row = column headers. One row per period, oldest first (50+ periods recommended for seasonal cycles).
Only used for labelling the chart. The order of the rows is what matters.
Sales, sign-ups, traffic, cost β whatever continuous metric you are trying to predict.
How many periods before the pattern repeats: 12 for monthly data with a yearly cycle, 7 for daily data with a weekly one, 4 for quarterly.
Added means the December bump is the same number of units every year. Multiplied means it is the same percentage, so the bump grows as the business does.
The series with its wobble and its cycle smoothed away.
The same shape every cycle, above and below the trend.
Should look structureless. Big spikes here are usually events, not noise.
Here in Forecast Starter, we handle a moving series either by repeating the last value (Naive) or by smoothing its level and slope (Holt). When you step up to ARX Forecasting, you will meet stationarity and Differencing (d = 1): subtracting each period from the one before it (\(\Delta y_t = y_t - y_{t-1}\)) so a climbing or wandering series becomes flat period-to-period changes before fitting autoregressive lags and external predictors.
Pick a rule. Each one is a single sentence β if you cannot say it out loud, do not use it.
Every method looks accurate on the data it was fitted to. The only honest test is to hide the last few periods, forecast them, and compare against what actually happened.
These are cut from the end, never chosen at random β a method that saw next month while predicting this one is not being tested, it is being told.
Watch out: every change you make (a method, a slider, the cycle length) is re-scored on these same hidden periods. Once you pick settings by watching this table, the hidden periods are helping to choose the model, so a score you tuned your way to is optimistic. Check it at a different number of hidden periods, or press Score from many origins below the table, before you believe it.
| Method | Typical miss (MAE) | Typical miss (%) | vs. "repeat last period" | Average bias (ME) | Big-miss penalty (RMSE) |
|---|---|---|---|---|---|
| Load data to score the methods. | |||||
MAE is the average size of the miss, ignoring whether it was too high or too low. The percentage column is left blank when any hidden period sat at or near zero, because dividing by it would produce a meaningless number.
The table above scores one starting point: the forecast made at the end of the training periods. A forecast origin is the last period a forecast is allowed to see. This panel runs the same test from many earlier origins, each forecast using only the periods before it, and adds up the misses. It uses your settings exactly as they are when you press the button, so this score cannot be tuned.
Load a series to score it from many origins.