Forecast the Next Year
and See How Far to Trust It
Upload a history of sales, demand, or revenue. Get a forecast with a likely range, a repeating seasonal pattern when your history is long enough, and a backtest that shows how the method did on recent months it was not shown.
Worked example: a year of airline passengers
Public dataset (Box-Jenkins AirPassengers, 1949 to 1960), not customer data. Shown to illustrate the output.
| Question | Where will monthly passenger numbers be a year from now? |
| Data | 144 monthly rows, one value per month |
| Method | Holt-Winters exponential smoothing with level, trend, and additive seasonality |
| Backtest | Last 12 months withheld, model refit on the rest, then asked to predict them |
| Result | Average miss of 2.5% (MAPE) and 11.56 passengers (thousands) per month (MAE) on the withheld year |
| Caveat in the report | A residual check showed strain, so the report tells you to treat the width of the range as approximate |
MAPE is the average size of the miss as a percentage of the actual value. MAE is the average miss in the units of your data. Both come from the withheld months only, not from the data the model was fit on.
You can re-run the backtest yourself in R (base R, no packages). Last checked 2 November 2026; it printed MAPE 2.52 MAE 11.56, matching the report:
v <- as.numeric(AirPassengers)
tr <- v[1:132]; te <- v[133:144]
hw <- HoltWinters(ts(tr, frequency = 12), seasonal = "additive")
p <- as.numeric(predict(hw, 12))
cat("MAPE", round(mean(abs((te - p) / te)) * 100, 2),
"MAE", round(mean(abs(te - p)), 2), "\n")
What a forecast report contains
Each part below appears in the sample report linked above
Point Forecasts
A projected value for each future period, such as the next 12 months. Use it as a planning input for inventory, staffing, and budgets, together with the range.
Confidence Intervals
Know the range of likely outcomes. Each period gets an 80% and a 95% band, so you can plan for a better and a worse case. The bands widen further out.
Seasonal Pattern
Shows which parts of the cycle run above or below the usual level. A seasonal pattern needs at least two full cycles of history, such as two years of monthly data.
Trend Analysis
See the underlying direction of your data: rising, falling, or flat, apart from the seasonal ups and downs.
Tested Against the Past
The last periods are held back, the model predicts them, and the report shows how close it came. If a check is shaky, the report says so.
Plain-English Notes
Each chart has a short written note, drafted by AI from the numbers. Read it next to the chart, and treat it as a draft you check.
What is Time Series Forecasting?
Time series forecasting is a technique for predicting future values based on historical data points collected over time. Unlike traditional regression that assumes independent observations, time series analysis recognizes that data points are temporally dependent: what happened yesterday influences today, and today influences tomorrow.
Time series forecasting goes beyond a simple moving average. It separates:
- Trends: Long-term directional movements (growth, decline, or stability)
- Seasonality: Recurring patterns at fixed intervals (daily, weekly, monthly, yearly)
- Cycles: Longer swings not tied to the calendar
- Noise: Random variation and one-time events
Why Time Series Matters for Business
A forecast turns past patterns into a planning number with a range around it. Whether it beats your current method is something you can test: the backtest compares the forecast with what actually happened on recent periods.
Key Applications of Time Series Forecasting
Time series forecasting powers critical business decisions across industries:
- Demand forecasting: Predict product demand to optimize inventory and prevent stockouts
- Sales forecasting: Project revenue for budgeting, hiring, and investor reporting
- Capacity planning: Forecast customer volume for staffing and resource allocation
- Financial planning: Model cash flow, expenses, and financial KPIs
- Supply chain optimization: Anticipate supply needs and lead times
- Energy forecasting: Predict consumption patterns for grid management
Understanding Forecast Accuracy Metrics
Evaluating forecast quality is essential for continuous improvement. Key metrics include:
- MAE (average miss): The typical size of the error, in the same units as your data
- MAPE (average miss, in percent): The same idea as a percentage, useful for comparing series on different scales
- Bias: Whether forecasts lean too high or too low
The standard forecast report gives MAE and MAPE from the backtest, plus a check on whether the leftover errors still show a pattern (a sign the model missed something).
How the method is chosen
The standard forecast report follows a fixed order, with no guessing. It uses the first method your data supports and names it in the report.
1. Holt-Winters (seasonal)
Smooths recent history into a level, a trend, and a repeating seasonal pattern, weighting recent months more. Used when the history holds at least two full cycles.
2. Holt (trend only)
The same smoothing without a seasonal part. Used when there is not enough history for a seasonal pattern.
3. ARIMA(1,1,1)
A classic statistical model that predicts each value from the recent ones. Used if the smoothing fits fail.
4. Straight-line drift
A simple trend line with ranges from the leftover errors, as a last resort. A flat history gives a flat forecast.
Need something else, such as Prophet, holiday effects, or several related series at once? That is a different kind of build. Read how ARIMA and Prophet compare.
How this compares with a spreadsheet or code
What each route gives you out of the box, as we understand them
| Feature | MCP Analytics | Excel / Sheets | Prophet (Python) | R forecast package |
|---|---|---|---|---|
| No coding required | Yes | Yes | No (Python) | No (R) |
| Methods | Holt-Winters, Holt, ARIMA fallback | Exponential smoothing and linear trend functions | Prophet | Many (ETS, ARIMA, others) |
| Choosing the method | Fixed rules, named in the report | You choose | You choose | Automatic selection available |
| Prediction ranges | 80% and 95% | 95% in the forecast sheet feature | Yes | Yes |
| Backtest on recent periods | Built in | You build it | Available, you write it | Available, you write it |
| Shareable report | Link to an interactive report | Share the file | Your own output | Your own output |
Other columns reflect common default behavior as of November 2026. All three alternatives are good tools, and the R package covers more methods than we do.
Forecasting Use Cases
Where time series forecasting is typically used
Demand Forecasting
Project product demand to guide inventory levels, with a range so you can decide how much buffer to hold.
Revenue Forecasting
Project future revenue for budgeting and hiring plans. The range supports a better case and a worse case.
Capacity Planning
Forecast customer volume and workload as an input to staffing plans.
Supply Chain Planning
Project material needs ahead of supplier lead times.
Energy Forecasting
Project consumption patterns for a facility or utility from its meter history.
Financial Planning
Model cash flow, expenses, and key financial metrics. Support budgeting cycles with a projection and its range.
What you can check
Things you can verify in a report
Your data
Encrypted in transit. See the privacy policy for how uploads are handled.
Named methods
Every report names its method, shows the backtest, and flags checks that did not pass.
Repeatable
Same data, same method, same numbers. The R code is shown in the report.
Frequently Asked Questions
Get answers to common questions about time series forecasting
ARIMA (AutoRegressive Integrated Moving Average) is a classical statistical method that excels at capturing linear patterns, autocorrelations, and trends in stationary data. It requires parameter tuning (p, d, q) and works best with clean, regularly-spaced data.
Prophet, developed by Facebook/Meta, is designed for business time series with strong seasonal effects and holiday patterns. Prophet handles missing data better, requires less manual tuning, and provides intuitive decomposition of trends and seasonality.
Which is better depends on your data, and the honest way to decide is a backtest on your own history. The standard forecast report here uses Holt-Winters first and ARIMA(1,1,1) as a fallback; it does not run Prophet. See the ARIMA and Prophet comparison.
Seasonality is a recurring pattern at fixed intervals (daily, weekly, monthly, or yearly) that significantly impacts forecast accuracy. Modeling seasonality when it is really there usually helps, and the backtest shows by how much on your data.
Common seasonal patterns include: weekly retail sales peaks on weekends, monthly billing cycles, quarterly business reporting, and yearly holiday shopping spikes.
Seasonal Holt-Winters, used here when there are at least two full cycles of history, models one repeating pattern and separates it from the underlying trend.
The amount of historical data needed depends on your forecasting horizon and seasonality:
- Daily forecasts: At least 2-3 weeks of data
- Weekly forecasts: 3-6 months of weekly data
- Monthly forecasts with yearly seasonality: 2-3 years (24-36 months) to capture seasonal patterns
- Quarterly business forecasting: 3-5 years for robust results
The key is having at least 2-3 complete cycles of your dominant seasonal pattern. More data generally improves accuracy, but data older than 5 years may not reflect current market conditions.
Confidence intervals represent the range of likely outcomes for a forecast, quantifying uncertainty. A 95% range is built so that, if the model's assumptions hold, about 95 of 100 future values land inside it. If the checks in the report are strained, the real coverage may be lower.
They matter because:
- They enable risk-aware planning by showing best and worst-case scenarios
- They widen as forecasts extend further into the future, reflecting increasing uncertainty
- They help set appropriate inventory buffers and safety stock levels
- They inform scenario planning for budgets and resource allocation
Narrow intervals indicate high confidence, while wide intervals suggest more volatility or uncertainty in the data.
Simple Exponential Smoothing: Use for data with no clear trend or seasonality, when you need fast, reactive forecasts.
Holt-Winters (Triple Exponential Smoothing): Use for data with both trend AND seasonality, like monthly sales with yearly patterns. It is fast and works well on regular monthly or weekly data.
ARIMA: Use when you need statistical rigor, your data has complex autocorrelation patterns, or you want to incorporate external variables (ARIMAX). Requires more expertise but captures subtle patterns.
For seasonal business data, Holt-Winters is a sound starting point. Compare against ARIMA when the leftover errors still show a pattern.
Anomaly detection in time series involves identifying data points that deviate significantly from expected patterns. Detection methods include:
- Statistical approaches using z-scores or IQR to flag points beyond 2-3 standard deviations
- Decomposition methods that separate trend and seasonality to identify unusual residuals
- Machine learning approaches like Isolation Forest or autoencoders
Once detected, handle anomalies by: investigating if they represent real events (promotions, outages) or data errors; deciding whether to correct, remove, or adjust them; using robust forecasting methods less sensitive to outliers.
Check your history for these before you upload, since one-off spikes can pull a forecast off course.
Traditional time series forecasting cannot predict unprecedented events (black swans) because models learn from historical patterns. However, you can improve resilience by:
- Using confidence intervals to plan for uncertainty
- Implementing scenario analysis with multiple forecast paths
- Monitoring forecast errors in real-time to detect regime changes quickly
- Combining quantitative forecasts with qualitative business intelligence
- Building adaptive models that quickly incorporate new data
After a disruption, refit models with recent data and consider structural breaks. The report's ranges show uncertainty, and the backtest shows whether recent months are drifting away from the forecast.
Related Resources
Deep dive into time series forecasting methods and best practices
Whitepapers
Tutorials
Start Forecasting Today
Upload your historical data and get a forecast. See pricing for plan details.
Where to start
One email with your data and your question. We take it from there.
MCP Analytics
Data science by email
Send us your data and your question, and we will reply.
Try it on your own data
30 days free.
Answers, analytics and custom analytics. No card, no call, nothing to install.
30 days free. →