Quick answer
Project Cost Variance is calculated as:
Earned Value - Actual CostUse this Excel version when your inputs are on row 2:
=B2 - C2What is Project Cost Variance?
Project Cost Variance measures the cost connected to a business result. It helps show whether the result is efficient enough to justify the money spent.
Project management KPIs compare plan versus actual work, cost, schedule, risks, and resource use.
Real-life example
Imagine a project manager preparing a status report. The team adds the inputs for Project Cost Variance to a project status dashboard, calculates the KPI for the current month, and compares it with the previous month and target. In the sample below, the result is $8,000. That number becomes useful when everyone uses the same formula each month.
| Excel cell | Input | What it means | Sample value |
|---|---|---|---|
| B2 | Earned Value | the input value used by the KPI formula | $84,000 |
| C2 | Actual Cost | the cost included in the calculation for the same period as the output | $76,000 |
| Result | Project Cost Variance | Output of the KPI formula | $8,000 |
How to calculate Project Cost Variance in Excel
- Create one row per reporting period, team, product, campaign, location, or customer segment.
- Add one input per column. Do not combine inputs in the same cell.
- Paste the Excel formula in the KPI result column.
- Format the result as Currency.
- Copy the formula down the table and compare the result against target, previous period, and trend.
- 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.
Project Cost Variance = [Earned Value] - [Actual Cost]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
Lower is usually better, because this KPI often represents cost, waste, delay, risk, loss, or friction.
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.