AACE EVP common mistakes
AACE EVP · Understand the traps and how to avoid them.
Treating EV as money spent or money received rather than as the budgeted value of work physically accomplished, so budgeted cost of work performed is confused with actual cost.
Everyday finance intuition equates value with cash, and the three-letter acronyms PV/EV/AC look interchangeable under time pressure.
What to do instead
Before every calculation, label each figure aloud as budgeted (PV), earned (EV), or actual (AC), and derive EV only from percent complete times the work package budget or from a milestone/weighted-milestone credit, never from invoices.
Mixing up cost variance and schedule variance sign conventions, reporting a negative SV as good or a positive CV as overrun.
The formulas CV = EV - AC and SV = EV - PV differ only in the second term, and candidates memorize them as strings rather than as 'earned minus what it cost' and 'earned minus what was planned'.
What to do instead
Anchor on the semantic reading: EV minus AC positive means under budget; EV minus PV positive means ahead of schedule. Re-derive each formula from that sentence during the exam instead of recalling symbols.
Computing percent complete by dividing EV by AC or by elapsed calendar time instead of by the budgeted value of completed scope.
Percent complete feels like a progress ratio, and actual cost or time elapsed is readily available, so it becomes the default denominator.
What to do instead
Always divide earned value by budget at completion (or by the work package budget for a component) and check that the result is expressed against planned scope, not against spend or duration.
Applying earned value to work packages that cannot be objectively measured, such as level-of-effort or apportioned work, and then interpreting the resulting variances as real performance signal.
Candidates treat EV as universally applicable and forget that some work is measured by its support relationship to discrete work rather than by its own output.
What to do instead
Identify the measurement technique for each work package first; for level of effort, expect EV to track PV and AC proportionally, and analyze variance only on discrete, objectively measurable packages.
Building a baseline whose control accounts combine incompatible units or omit undistributed budget and management reserve, so later variance analysis is meaningless.
The pressure to finish the schedule and budget quickly leads to lumping scope and skipping the reconciliation of the sum of control accounts to the total budget.
What to do instead
Reconcile bottom-up: work package budgets sum to control accounts, control accounts plus undistributed budget and management reserve equal the total allocated budget, and each control account has a single responsible manager and consistent unit of measure.
Treating management reserve as available for work package execution and folding it into the performance measurement baseline.
Management reserve and contingency sound synonymous, and including reserve inflates the baseline in a way that looks prudent.
What to do instead
Keep management reserve outside the PMB and outside BAC used for earned value; only undistributed budget sits inside the baseline awaiting distribution to control accounts, and reserve is released only through formal change control.
Forecasting estimate at completion by simply extrapolating actual cost to date without selecting an appropriate performance factor or considering remaining work conditions.
Candidates latch onto one formula, often the budgeted-rate or the cumulative CPI method, and apply it mechanically regardless of whether the variance is expected to persist.
What to do instead
Choose the EAC method deliberately: budgeted rate when variances are atypical and expected to reverse, cumulative CPI when they will persist, and a blended or manager-adjusted factor when remaining work differs materially from work to date. State the rationale.
Reporting TCPI against the original budget when the question asks about performance needed to meet a revised or management target.
The two TCPI forms differ only in the denominator, and candidates default to BAC without reading which target the scenario specifies.
What to do instead
Read the target first: use (BAC - EV)/(BAC - AC) for the original budget and (BAC - EV)/(EAC - AC) for a revised estimate, and sanity-check that TCPI rises as the target tightens.
Approving scope changes informally or after the fact without revising the baseline, then analyzing variances against a stale plan.
Change control is perceived as administrative overhead, and the schedule pressure favors starting work before paperwork is complete.
What to do instead
Require every scope change to flow through the change control board with documented impact on scope, schedule, and cost, and rebaseline only through approved, versioned baseline revisions so variance analysis always compares against the current authorized baseline.
Treating an integrated baseline review as a financial audit or a document check rather than an assessment of whether the baseline is realistic, complete, and achievable.
The word review suggests compliance checking, and candidates focus on whether plans exist rather than whether the logic, resources, and risks support them.
What to do instead
Frame IBR answers around baseline realism: verify the work breakdown structure captures all scope, the schedule logic and critical path are sound, resources support the plan, risks and reserves are addressed, and managers can defend their control account plans.