Forecast Accuracy Rate
Definition
Forecast Accuracy Rate
Forecast accuracy rate measures how closely predicted demand matched actual demand across a defined period, expressed as a percentage. It is the foundation every roster is built on, because a schedule can only be as good as the forecast beneath it.
Daily accuracy is the easy version. Getting the day right while getting every half-hour wrong still leaves queues unstaffed at the times that matter.
Direction matters too. Over-forecasting costs money in idle seats, while under-forecasting costs service level, and the two are rarely equally expensive.
Key takeaways
- Forecast accuracy rate compares forecast volume against actual volume for the same period.
- Interval-level accuracy matters far more than daily or weekly accuracy.
- Over-forecasting and under-forecasting carry different costs and should be reported separately.
- Accuracy above 95% at interval level is exceptional, not a starting expectation.
How it works
Forecast accuracy rate is calculated by comparing forecast volume with actual volume for the same period, expressing the difference as a percentage of actual, then subtracting that error from 100 to give an accuracy figure.
The formula is: 100 − (|forecast − actual| ÷ actual × 100).
Accuracy has to be measured at the level decisions are made, and that level is almost always the interval.
| Level | Typical accuracy | What it drives |
|---|---|---|
| Monthly | 95–98% | Recruitment and budget |
| Weekly | 92–96% | Shift patterns |
| Daily | 88–94% | Roster confirmation |
| 30-minute interval | 75–85% | Intraday staffing |
The interval row is the honest one — monthly accuracy of 97% means very little if the intraday curve is wrong on the days that count.
Structure inside the data is what makes forecasting possible at all. The NIST/SEMATECH e-Handbook explains that time series analysis accounts for internal structure such as autocorrelation, trend, or seasonal variation in data taken over time.
Seasonal shifts in demand are measurable and public. The U.S. Census Bureau reported e-commerce sales of $340.2 billion in Quarter 2, 2026, representing 17.1% of total retail sales, in a release dated 18 August 2026.
Known events should be modelled, never averaged — marketing campaigns, billing runs, and product launches produce spikes that historical smoothing will always miss.
The work belongs to call center forecasting and feeds directly into workforce management (WFM), which converts volume into required staffing.
Judgement still has a place beside the model. Judgmental forecasting covers the events no historical series contains, and it should be documented rather than applied quietly.
Never report accuracy without reporting bias. A forecast that is 93% accurate but consistently low will understaff every single week.
Examples
Forecast accuracy depends on how stable demand is, how much of it is driven by known events, and how granular the planning needs to be. Five cases show the practical range.
Retail contact centres forecast against promotional calendars. Because the marketing schedule is known, campaign spikes are modelled rather than smoothed into the baseline.
Utilities forecast against weather and billing cycles. A cold snap and a bill run landing in the same week produce a spike neither variable predicts alone.
Healthcare lines forecast against seasonal illness patterns. Historical curves work well until a novel pattern appears, at which point judgemental overlay carries the load.
Financial services forecast around regulatory deadlines. Tax and reporting dates create predictable peaks that reward interval-level modelling.
Outsourced providers report accuracy per client and per interval. Buyers should ask for interval accuracy specifically — since daily figures always look considerably better.
Related terms
Forecast accuracy rate sits at the front of the workforce planning chain. The terms below cover the forecasting disciplines, the mathematical models, and the planning functions that consume the output.
- Call Center Forecasting: the discipline that produces the forecast being scored.
- Judgmental Forecasting: the human overlay used where history offers no guide.
- Erlang: the traffic unit underpinning most staffing calculations.
- Erlang Models: the formulas that convert forecast volume into agent requirements.
- Workforce Management (WFM): the function that turns forecasts into published rosters.
- Call Center Interval: the planning unit accuracy should be measured against.
- Staffing Model: the structure that translates requirement into contracted headcount.
FAQ
How is forecast accuracy rate calculated?
Take the absolute difference between forecast and actual, divide by actual, express it as a percentage, then subtract that from 100.
What accuracy should we expect?
Roughly 95–98% monthly and 75–85% at 30-minute intervals. Interval accuracy is the figure that actually affects service level.
Why does interval accuracy matter most?
Because staffing decisions are made per interval, and a correct daily total can still leave the morning peak unstaffed.
What is forecast bias?
A consistent direction of error. A forecast that is accurate but always low will understaff every period.
How should known events be handled?
Model them explicitly. Historical smoothing removes exactly the spikes that campaigns and billing runs create.
Who should own forecast accuracy?
Workforce management, reporting it alongside schedule adherence and service level.
Source partners planning capacity against contracted service levels can compare models across Outsource Accelerator hubs.
Independent
