Earned Value Management (EVM) Template: Free Examples, Download and How to Use It

What does an EVM template measure?

earned value management (EVM) template is a key topic in modern project management and teamwork. An EVM template integrates scope, schedule, and cost. It does not equate money spent with progress. Instead, it assigns budget to defined work packages, schedules that budget over time, measures completed work using agreed rules, and compares earned budgeted value with actual cost at the same status date.

The three core values are:

• Planned value (PV): the authorized budget for work that should have been completed by the status date. In older terminology, PV is BCWS (budgeted cost of work scheduled).
• Earned value (EV): the authorized budget value of work actually completed by that date. EV is not revenue, cash received, or amount spent. Older terminology calls it BCWP (budgeted cost of work performed).
• Actual cost (AC): the cost incurred for the work performed by that same date, using the project’s agreed accounting basis. Older terminology calls it ACWP.

Budget at completion (BAC) is the total budget assigned to the scope in the performance measurement baseline. At completion, PV and EV will normally reach BAC if all baseline scope is completed. Management reserve or other funds outside the measurement baseline should not be silently mixed into BAC; follow the organization’s control rules.

What should an EVM template include?

A practical template needs a summary, a work-package data table, a formula area, and a short narrative/action log. The work-package level is important: a single project total can hide one troubled package behind several healthy ones.

For a spreadsheet, put one row per work package and keep cumulative and current-period values distinguishable. A compact column layout is: `WBS | Owner | BAC | PV | EV | AC | CV | SV | CPI | SPI | ETC | EAC | VAC | Progress evidence | Variance note | Action owner/date`. Add reporting-period columns or a separate trend tab so that current-period changes are not confused with cumulative-to-date figures.

How do you calculate the core EVM formulas?

Use the same currency, scope, and data date for PV, EV, and AC. Calculate these measures from the cumulative values at that cut-off:

CV and SV are currency amounts, not days. Traditional SV is a schedule indicator expressed in budget units; at the end, when EV and PV both reach BAC, SV returns to zero even if the project finished late. If the decision requires an actual time forecast, use the schedule network/critical-path analysis or an earned-schedule method rather than calling SV “days behind.” CPI and SPI are ratios, not percentages: CPI of 0.80 means $0.80 of budgeted work value was earned per $1.00 of actual cost.

Guard against division by zero at the beginning of a project. If AC is zero, CPI is undefined; if PV is zero, SPI is undefined. Show “N/A” rather than inventing a result. Confirm your chosen convention for negative or credit costs as well.

How do you set up the template before reporting?

Start with authorized scope, not a list of loosely related activities. Create a work breakdown structure (WBS) that divides deliverables into manageable work packages, assign each package an owner, and define acceptance or completion evidence. Estimate the budget and schedule for each package, then spread the budget over the periods when the work is planned. The time-phased sum becomes the performance measurement baseline against which performance is assessed.

Choose an earning method that fits the work and document it before execution. Short, discrete tasks can use a 0/100 rule: earn value only when accepted. For a short task with clear start and finish, a 50/50 rule may be appropriate if policy permits. Repetitive measurable work can earn value by quantity—for example, 40 of 100 verified units installed means 40% of the package budget, if units are comparable. Longer work may use weighted milestones with objective evidence. Avoid unsubstantiated “percent complete” estimates; 90% complete can remain 90% for weeks and produce misleading EV.

Set the status date and reporting cadence. Collect progress evidence, reconcile AC to the same period and scope, calculate measures, review material variances with package owners, and record decisions. Monthly is common for larger projects; faster delivery teams may review more frequently. Whatever cadence you choose, use it consistently and allow for accounting lag to be visible rather than silently mixing dates.

What does a fully worked EVM example show?

Suppose a software implementation has a BAC of $500,000, scheduled over ten months. At the end of month five, the approved plan says 55% of the budgeted work should be complete. Objective acceptance records show 45% complete. The accounting system shows $260,000 in actual cost for the same work and cut-off date.

First calculate the values:

• PV = 55% × $500,000 = $275,000
• EV = 45% × $500,000 = $225,000
• AC = $260,000

Then calculate status:

• CV = EV − AC = $225,000 − $260,000 = −$35,000 (unfavorable cost variance)
• SV = EV − PV = $225,000 − $275,000 = −$50,000 (less work value earned than planned)
• CPI = EV ÷ AC = $225,000 ÷ $260,000 = 0.865 (about 86.5 cents of budgeted value for each dollar spent)
• SPI = EV ÷ PV = $225,000 ÷ $275,000 = 0.818 (about 81.8% of planned value earned)

This is not simply “35,000 over budget.” The project has also earned $50,000 less value than planned. The two indices signal different problems: CPI describes cost efficiency, while SPI describes progress against the time-phased plan. The project manager should inspect the largest package-level variances, verify that acceptance rules were applied consistently, and determine whether the schedule variance affects the critical path.

Now show forecast alternatives, rather than presenting one number as certainty. If cumulative cost efficiency continues, EAC = BAC ÷ CPI = $500,000 ÷ 0.865 ≈ $578,035. The implied remaining cost is ETC = EAC − AC ≈ $318,035, and VAC = BAC − EAC ≈ −$78,035. This is a mathematical extrapolation, not a guaranteed outcome.

If the variance to date is genuinely atypical and the remaining work is expected to meet its original budget, use EAC = AC + (BAC − EV) = $260,000 + $275,000 = $535,000. That assumption needs evidence, such as a one-time mobilization cost that will not recur. A bottom-up ETC is often better when the remaining work has been re-estimated: document resource rates, quantities, risks, and schedule assumptions, then calculate EAC = AC + bottom-up ETC.

A composite forecast sometimes uses EAC = AC + (BAC − EV) ÷ (CPI × SPI) when both cost and schedule performance are expected to affect future cost. Here it is approximately $260,000 + $275,000 ÷ (0.865 × 0.818) = $648,900. Use this only when there is a defensible mechanism—such as schedule delay creating extended staffing or escalation costs—not just because multiplying two ratios looks conservative. Compare a formula-based estimate with the team’s risk-adjusted, bottom-up forecast and state which one management is using.

Finally, test the recovery challenge. TCPI to meet BAC = (BAC − EV) ÷ (BAC − AC) = $275,000 ÷ $240,000 = 1.146. Remaining work would need a CPI of about 1.15 to finish within the original budget. Ask the delivery leads whether that improvement is plausible. If not, escalating effort alone will not make the budget achievable; management may need to approve a revised forecast, scope decision, or recovery plan.

How should you interpret thresholds and trends?

Do not copy a universal CPI threshold into every project. Set control limits with the sponsor and delivery leads based on uncertainty, contract, project scale, historical performance, and the cost of delayed intervention. A team might investigate a 5% variance in a stable repeatable rollout, while a novel prototype could need a wider tolerance. These are local management thresholds, not universal definitions of success.

A useful trigger could require the owner to explain any package outside an agreed band for two consecutive periods, immediately escalate a critical-path milestone miss, or reforecast when EAC exceeds the approved budget or available contingency. Define who reviews the signal, what evidence is required, and by when an action is due. Look at cumulative results and period-to-period movement: a strong cumulative CPI can conceal a sharp recent decline, while one poor period may reflect a timing issue.

Trend charts for PV, EV, and AC can make divergence visible. Label the date, currency, baseline version, and whether values are cumulative. Pair them with a short narrative: cause, consequence, corrective action, owner, and expected check-in. A number without a response path is reporting overhead, not control.

How do you protect baseline integrity?

The baseline is the reference plan, not a target to edit until the variance disappears. Maintain version history and a formal change log. When authorized scope, schedule, or budget changes, record the approval, effective date, affected work packages, and impact on BAC and time-phased PV. Show historical performance against the baseline that was in force; do not rewrite past PV or EV to make old reports appear favorable.

Separate scope changes from corrective actions. A corrective action changes how the team will perform remaining work; it does not automatically justify changing the baseline. An approved scope change may require a baseline update, but preserve the original version and explain the reconciliation. If the project is rebaselined, label before-and-after measures so stakeholders do not mistake a new starting point for recovered performance.

Data discipline matters just as much. Match AC to the same scope and cut-off as EV, account for accruals consistently, avoid double-counting commitments and invoices, and identify late cost postings. Keep evidence for progress claims. If actual cost data arrive after the reporting date, note the lag and revise transparently when reconciled.

What are EVM’s benefits, limitations, and common mistakes?

EVM gives leaders a common language for progress and cost, surfaces unfavorable trends earlier than a final budget report, and makes assumptions behind forecasts explicit. It can improve accountability because each work package has an owner and measurable earning rule. Its cost is setup and maintenance: teams must build a credible baseline, keep schedules and actuals aligned, and validate progress. For a small, rapidly changing effort, this overhead may exceed the decision value.

Common pitfalls include:

• Treating spend as earned value. Paying an invoice does not prove that planned work is complete.
• Using subjective completion percentages. Define observable earning rules and retain evidence.
• Mixing dates or scope. PV, EV, and AC must share a status date and comparable work boundary.
• Changing the baseline without a trail. This erases the signal the template is meant to preserve.
• Reading SPI as calendar time. SV is in budget units and traditional SPI can return to 1.0 at project completion despite lateness.
• Treating EAC as a promise. Each formula encodes an assumption; identify it and compare with a realistic bottom-up estimate.
• Rewarding high CPI blindly. It can result from understated scope, delayed cost recognition, or quality cuts that create rework.
• Rolling everything into one total. Inspect the work packages driving the result and consider quality, risk, customer acceptance, and critical-path impact.

For agile or discovery-heavy work, stable scope may not exist at a detailed level. A team can apply EVM to a release or bounded phase if it defines the budget, acceptance criteria, and baseline for that interval. Do not convert story points into currency and imply precision unless the mapping is consistent and useful. For an exploratory initiative, a rolling forecast, burn rate, throughput, and outcome measures may be more honest than a rigid baseline.

When can Doitify support EVM work?

An EVM worksheet is only as dependable as the underlying work and ownership data. Teams that already plan work in a project workspace can keep tasks, subtasks, owners, schedules, dependencies, milestones, and progress reporting together, then export or reconcile the approved values with their finance and controls process. Doitify supports project and team management in one workspace, including Gantt charts, calendars, WBS dependencies, workload, and work reports. It can help organize execution inputs; this does not make it a certified EVM system or replace formal cost accounting, baseline governance, or contract reporting. Disclosure: Doitify is our product, and this mention describes its project-management role rather than an independent EVM-system certification.

Conclusion

An earned value management template becomes useful when it links budgeted scope, a time-phased plan, objective evidence of completion, and actual cost at a common status date. The core measures—CV, SV, CPI, and SPI—describe current performance; EAC, ETC, VAC, and TCPI help test what may happen next. None of them explains causes by itself.

Build the worksheet around owned work packages, write down earning rules and thresholds before reporting, preserve baseline history, and compare formula-based forecasts with a reasoned estimate of remaining work. Then turn material variances into named actions. That is what makes EVM a management tool rather than a spreadsheet full of precise-looking numbers.

If this post on earned value management (EVM) template was helpful, you might also enjoy Gantt Chart vs Project Plan: What’s the Difference? and Project Management Software With CRM and Time Tracking: Best Options.