Operations KPI

Forecast Accuracy Formula

Learn what Forecast Accuracy means, how to calculate it in Excel, and how to recreate the same KPI as a Power BI DAX measure.

💡 Ideas for You

Resources related to this KPI and spreadsheet reporting.

4 useful links
📚 Step-by-step booksStart with beginner-friendly step-by-step books and learning resources from Create & Learn.📊 KPI dashboard resourcesBooks and templates for building operations KPI dashboards in spreadsheets.📈 Business metrics booksReferences for understanding operations metrics, definitions, and reporting habits.📘 Excel reporting guidesGuides for turning spreadsheet calculations into clear reports and dashboards.

Quick answer

Forecast Accuracy is calculated as:

1 - ABS(Actual - Forecast) / Actual

Use this Excel version when your inputs are on row 2:

=IFERROR(1 - ABS(B2 - C2) / B2,0)
Example result96.2%
FormatPercentage
Typical chartLine chart for trends; bar chart for comparing teams, channels, products, or locations.

What is Forecast Accuracy?

Forecast Accuracy is a Operations KPI used to turn business activity into a clear number. It helps an operations manager reviewing weekly performance decide where delays, defects, or capacity bottlenecks are hurting results.

Operations KPIs measure how reliably work moves through production, fulfillment, inventory, quality, and suppliers.

Beginner tip: A KPI is not just a formula. It is a number used to make a decision. Before adding it to a dashboard, write down the definition, time period, owner, target, and data source.

Real-life example

Imagine an operations manager reviewing weekly performance. The team adds the inputs for Forecast Accuracy to an operations performance dashboard, calculates the KPI for the current month, and compares it with the previous month and target. In the sample below, the result is 96.2%. That number becomes useful when everyone uses the same formula each month.

Excel cellInputWhat it meansSample value
B2Actualthe input value used by the KPI formula104,000
C2Forecastthe input value used by the KPI formula100,000
ResultForecast AccuracyOutput of the KPI formula96.2%

How to calculate Forecast Accuracy in Excel

  1. Create one row per reporting period, team, product, campaign, location, or customer segment.
  2. Add one input per column. Do not combine inputs in the same cell.
  3. Paste the Excel formula in the KPI result column.
  4. Format the result as Percentage.
  5. Copy the formula down the table and compare the result against target, previous period, and trend.
Quality check before publishing:
  • Use the same date range for every input.
  • Confirm that the denominator is not blank or zero.
  • Document whether the KPI is calculated before or after discounts, refunds, taxes, returns, or cancellations.
  • Keep the definition stable so reports remain comparable over time.

Power BI DAX measure

If you also report this KPI in Power BI, create a measure instead of hard-coding the calculation in a visual. Replace the measure names below with the names used in your model.

Forecast Accuracy = 1 - DIVIDE(ABS([Actual] - [Forecast]), [Actual], 0)

For best results, build base measures first, such as revenue, cost, customers, orders, or tickets, and then build the KPI measure from those base measures.

How to read the result

Context matters. Compare it with your target, previous period, and industry norm instead of assuming bigger is always better.

Do not read the KPI alone. A single value can be misleading without a target, trend, segment, and business context. For example, the same result may be good for one product line but poor for another.

Useful comparisons

  • Current month versus previous month.
  • Actual result versus target or budget.
  • By channel, product, customer segment, team, or location.
  • Rolling average over several periods to smooth one-off spikes.

Common mistakes

  • Mixing time periods, such as monthly cost with quarterly revenue.
  • Using a total when the KPI should be segmented.
  • Changing the formula definition after the dashboard is already in use.
  • Comparing two teams that collect the inputs differently.
  • Ignoring blanks, zeros, refunds, cancellations, or duplicate records.