EVP — AACE Earned Value Professional Quick Review
Quick review for AACE International's AACE Earned Value Professional (EVP) candidates covering earned value formulas, baselines, forecasting, controls, and common traps.
Quick Review purpose
This independent Quick Review is for candidates preparing for AACE International’s AACE Earned Value Professional (EVP), exam code EVP. Use it to refresh the high-yield earned value management ideas before moving into topic drills, mock exams, and detailed explanations.
The exam-prep challenge is not just memorizing formulas. You need to recognize what the numbers mean, choose the right forecast method, identify weak baseline discipline, and separate schedule, cost, scope, and accounting issues.
Core earned value logic
Earned value management links three questions:
| Question | EVM answer | What it tells you |
|---|---|---|
| What work was planned? | PV | Budgeted value of work scheduled by the status date |
| What work was actually accomplished? | EV | Budgeted value of work performed |
| What did the accomplished work cost? | AC | Actual cost incurred for work performed |
The basic comparison is simple:
| Comparison | Metric | Interpretation |
|---|---|---|
| EV vs. PV | Schedule variance/performance | Are we earning value as fast as planned? |
| EV vs. AC | Cost variance/performance | Are we earning value efficiently? |
| BAC vs. EAC | Forecast variance | What is the likely final outcome? |
High-yield trap: EV is not money spent. EV is the budgeted value of completed work. AC is money or cost incurred.
The EVM building blocks
| Term | Quick meaning | Candidate trap |
|---|---|---|
| WBS | Product/scope decomposition | Do not confuse with organization chart |
| OBS | Organizational responsibility structure | Shows who owns the work |
| Control account | Management control point where scope, schedule, budget, actuals, and performance are integrated | Often owned by a control account manager |
| Work package | Near-term, detailed, measurable work | Should have a clear earned value method |
| Planning package | Future work not yet fully detailed | Must still be budgeted and controlled |
| CAM | Control Account Manager | Responsible for performance explanation and corrective action |
| PMB | Performance Measurement Baseline | Excludes management reserve in normal EVM usage |
| MR | Management reserve | Not budget for known, distributed work; not earned as EV |
| BAC | Budget at completion | Usually excludes management reserve |
| EAC | Estimate at completion | Forecasted final cost |
| ETC | Estimate to complete | Forecast cost for remaining work |
| VAC | Variance at completion | Expected underrun or overrun against BAC |
Baseline hierarchy to remember
A reliable EVM system starts with an integrated baseline:
- Define authorized scope.
- Decompose scope through the WBS.
- Assign responsibility through the OBS.
- Create control accounts.
- Break control accounts into work packages and planning packages.
- Time-phase budgets into the schedule.
- Measure progress objectively.
- Collect actual costs in the same structure.
- Analyze variances and forecast outcomes.
- Control changes to preserve baseline integrity.
| Baseline element | What good looks like | What weak control looks like |
|---|---|---|
| Scope | Authorized, traceable, decomposed | Uncontrolled scope growth |
| Schedule | Logic-based, statused, integrated with budget | Excessive constraints, missing logic, stale dates |
| Budget | Time-phased and tied to work | Level-loaded without work basis |
| Actual costs | Collected consistently with control accounts | Cost accounts do not align with EV structure |
| Progress | Objective, documented measurement | Subjective percent complete with no basis |
| Forecast | Based on performance and remaining work | Optimistic reset after every reporting period |
| Changes | Authorized, documented, traceable | Retroactive baseline changes to hide variance |
Key formulas
Memorize the formulas, but also know when each one is meaningful.
\[ \begin{aligned} CV &= EV - AC \\ SV &= EV - PV \\ CPI &= \frac{EV}{AC} \\ SPI &= \frac{EV}{PV} \end{aligned} \]\[ \begin{aligned} VAC &= BAC - EAC \\ ETC &= EAC - AC \\ TCPI_{BAC} &= \frac{BAC - EV}{BAC - AC} \\ TCPI_{EAC} &= \frac{BAC - EV}{EAC - AC} \end{aligned} \]Formula interpretation table
| Metric | Formula | Favorable result | Unfavorable result | Review note |
|---|---|---|---|---|
| CV | EV - AC | Positive | Negative | Cost efficiency in currency units |
| SV | EV - PV | Positive | Negative | Schedule performance in budget units |
| CPI | EV / AC | Greater than 1.0 | Less than 1.0 | Cost efficiency index |
| SPI | EV / PV | Greater than 1.0 | Less than 1.0 | Schedule efficiency index |
| VAC | BAC - EAC | Positive | Negative | Forecast underrun or overrun |
| ETC | EAC - AC | Lower but realistic | Unrealistically low | Remaining cost forecast |
| TCPI | Work remaining / budget remaining | Achievable if close to historical performance | Risky if much higher than CPI | Required future efficiency |
High-yield trap: A negative SV does not directly mean “late by X days.” Traditional SV is expressed in budgeted cost units, not time.
Forecasting EAC: choose the assumption first
EAC is not one formula. It is a forecast based on an assumption about remaining work.
| Situation | Common EAC approach | Logic |
|---|---|---|
| Past variance is atypical and will not continue | EAC = AC + BAC - EV | Remaining work is expected to follow the original budget |
| Current cost efficiency is expected to continue | EAC = AC + (BAC - EV) / CPI | Remaining work will perform like work completed so far |
| Cost and schedule efficiency both affect remaining work | EAC = AC + (BAC - EV) / (CPI x SPI) | Schedule pressure may drive additional cost impact |
| Original estimate is no longer valid | EAC = AC + bottom-up ETC | Re-estimate remaining work from current knowledge |
| Management-provided forecast is being evaluated | Compare EAC to CPI, TCPI, and remaining scope | Check realism, not just arithmetic |
flowchart TD
A[Performance data received] --> B{Is the variance isolated?}
B -- Yes --> C[Use AC + BAC - EV]
B -- No --> D{Will current cost efficiency continue?}
D -- Yes --> E[Use AC + remaining work / CPI]
D -- No --> F{Are cost and schedule pressure linked?}
F -- Yes --> G[Consider CPI x SPI method]
F -- No --> H[Use bottom-up ETC]
H --> I[Check TCPI realism]
E --> I
G --> I
C --> I
TCPI decision rule
TCPI tells you the cost efficiency needed on the remaining work to meet a target.
| If target is… | Use | Meaning |
|---|---|---|
| Original budget | TCPI based on BAC | Required efficiency to finish at BAC |
| Revised forecast | TCPI based on EAC | Required efficiency to finish at the forecast EAC |
Exam-style interpretation:
- If CPI is 0.85 and TCPI to BAC is 1.20, finishing at BAC is probably unrealistic without major corrective action.
- If TCPI to EAC is close to recent CPI, the EAC may be plausible.
- If TCPI is dramatically better than historical performance, question the forecast.
Progress measurement methods
Know which earned value technique fits the type of work.
| Technique | Best for | How value is earned | Common trap |
|---|---|---|---|
| 0/100 | Short tasks with clear completion | 0% until complete, then 100% | Can delay EV recognition |
| 50/50 | Short tasks started and completed within limited periods | 50% at start, 50% at finish | Can overstate progress if tasks linger |
| Weighted milestone | Discrete work with measurable interim points | EV earned at predefined milestones | Milestones must represent real progress |
| Percent complete | Work where physical progress can be estimated reliably | EV based on assessed completion | Subjective if no objective basis |
| Units complete | Repetitive measurable output | EV based on completed units | Unit weighting must reflect actual budget |
| Physical measurement | Engineering, construction, fabrication, installation | EV based on measurable installed/verified quantities | Quantity progress may not equal total effort |
| Level of effort | Support or sustaining work | EV usually follows passage of time | Does not reveal true performance efficiency |
| Apportioned effort | Work tied to another discrete effort | EV derived from base activity progress | Bad if the relationship is weak |
High-yield trap: LOE can hide performance problems. Because EV often tracks time, LOE may show little or no schedule variance even if support effectiveness is poor.
Discrete effort vs. LOE vs. apportioned effort
| Work type | Use when | EVM consequence |
|---|---|---|
| Discrete effort | Work has measurable output | Best for performance analysis |
| Level of effort | Work is time-based support with no discrete output | Limited variance insight |
| Apportioned effort | Work is proportional to another measurable task | Depends on quality of base measure |
A common exam decision point is whether a task should be measured objectively. If the work produces a definable deliverable, prefer a discrete method over LOE.
Schedule concepts that matter for EVP review
Earned value candidates must understand schedule quality, not just SPI.
| Concept | Quick review | Exam trap |
|---|---|---|
| Critical path | Longest path controlling project finish | A task with low float may be more urgent than one with high budget variance |
| Total float | Time an activity can slip without delaying project completion | Float is schedule flexibility, not budget |
| Free float | Time an activity can slip without delaying successor start | Not the same as total float |
| Data date | Status point for progress measurement | Actuals and EV should be cut off consistently |
| Baseline schedule | Approved plan for comparison | Do not keep rebasing to erase delay |
| Forecast schedule | Current projection | Should reflect actual progress and remaining logic |
| Logic ties | Dependencies between activities | Missing logic weakens critical path credibility |
| Constraints | Date restrictions | Excessive constraints can distort float |
| Negative float | Forecast completion later than required date | Indicates schedule pressure, not automatically cost overrun |
Traditional SV vs. earned schedule
Traditional earned value schedule variance is useful but limited because it is expressed in budget units. Near project completion, SV can trend toward zero as all work is eventually earned, even if the project finishes late.
Earned schedule concepts translate EV performance into time-based indicators:
| Concept | Meaning |
|---|---|
| ES | Earned Schedule: the time at which the current EV should have been earned according to the baseline PV curve |
| AT | Actual Time: time elapsed to the status date |
| SV(t) | ES - AT |
| SPI(t) | ES / AT |
Use earned schedule thinking when the question emphasizes time-based schedule performance rather than budget-valued schedule variance.
Cost collection and actual cost traps
EVP candidates should expect questions where the arithmetic is easy but the data interpretation is subtle.
| Issue | Why it matters |
|---|---|
| Accounting lag | AC may be understated if invoices or labor charges are late |
| Accruals | Needed to match cost to work performed |
| Commitments | Purchase commitments are not always the same as actual cost incurred |
| Indirect costs | Must be applied consistently with the cost system |
| Rate changes | Labor or overhead rate shifts can affect cost variance |
| Material timing | Buying material early may increase AC before EV is earned |
| Cost account mismatch | Actuals must align with the control account structure |
| Rework | Adds AC and may or may not earn additional EV |
| Scrap/waste | Raises AC without increasing EV |
| Subcontractor reporting | Must be integrated into the same status cycle |
High-yield trap: A project can look cost-unfavorable because material was purchased early, or falsely cost-favorable because actual costs have not yet been booked.
Variance analysis: what a strong answer includes
A variance explanation should go beyond “CPI is below 1.0.”
| Component | Good variance analysis answers |
|---|---|
| Variance identification | Which control account, work package, or activity is affected? |
| Cause | What specific event or condition caused the variance? |
| Impact | What is the effect on cost, schedule, technical scope, or forecast completion? |
| Corrective action | What will be done, by whom, and by when? |
| Forecast effect | Does the EAC, ETC, or completion date change? |
| Recurrence control | How will the cause be prevented or monitored? |
Weak explanations include:
- “Behind schedule due to delays.”
- “Over budget due to higher costs.”
- “Will recover next month” with no basis.
- “No impact” when CPI, SPI, or critical path evidence suggests otherwise.
Change control and baseline maintenance
AACE Earned Value Professional (EVP) exam candidates should be comfortable distinguishing legitimate baseline maintenance from improper variance masking.
| Action | Usually appropriate? | Why |
|---|---|---|
| Add authorized new scope to the baseline | Yes | Scope, budget, and schedule must reflect authorized work |
| Move budget from planning package to work packages as detail matures | Yes | Normal rolling-wave planning |
| Use management reserve for authorized in-scope unknowns | Yes, with approval | MR is controlled budget, not free performance recovery |
| Correct documented baseline errors | Yes, with traceability | Accuracy matters |
| Replan future work when assumptions change | Sometimes | Must preserve visibility of prior performance |
| Retroactively change completed work budgets to remove variance | Usually no | Masks performance history |
| Earn value for work not completed | No | Breaks EV credibility |
| Treat MR as part of BAC for performance measurement | No | MR is normally outside the PMB |
EVMS guideline intent areas
If your preparation materials reference EVMS guidelines, focus on the management intent behind the requirements.
| Area | What it is trying to ensure |
|---|---|
| Organization | Work scope and responsibility are clearly assigned |
| Planning, scheduling, and budgeting | Authorized work is time-phased into measurable plans |
| Accounting considerations | Actual costs are collected consistently with planned work |
| Analysis and management reporting | Variances are analyzed, explained, and acted on |
| Revisions and data maintenance | Baseline changes are controlled and traceable |
The exam-style issue is often practical: “Which control weakness is present?” or “Which corrective step best preserves baseline integrity?”
Integrated project controls view
Earned value should not be isolated from project controls.
| Control discipline | EVM connection |
|---|---|
| Scope management | Defines what can earn value |
| Schedule management | Determines when value should be earned |
| Cost management | Determines budget and actual cost comparison |
| Risk management | Explains uncertainty and may affect forecasts |
| Change management | Protects the baseline from uncontrolled changes |
| Contract management | Affects reporting, authorization, and cost collection |
| Quality management | Poor quality can create rework and cost variance |
| Forecasting | Converts current performance into expected outcomes |
Common exam traps
Trap 1: Confusing PV and EV
If the question says work was scheduled, think PV. If the question says work was completed or accomplished, think EV. If the question says money was spent or cost incurred, think AC.
Trap 2: Treating SPI as a time-delay percentage
SPI is budget-based. A SPI of 0.90 does not automatically mean the project is 10% late in calendar time.
Trap 3: Assuming all variances continue
Before choosing an EAC formula, ask whether the variance is isolated, systemic, or tied to schedule pressure.
Trap 4: Ignoring the data date
EV, PV, and AC must be compared as of the same status date. Mixed cutoff dates produce misleading indices.
Trap 5: Counting material purchase as progress
Buying material may create AC. EV is earned when the planned progress criterion is met, not merely when cash is spent.
Trap 6: Using LOE for measurable work
LOE is not a shortcut for difficult measurement. If work has measurable deliverables, an objective EV technique is usually stronger.
Trap 7: Hiding variance through rebaseline
Authorized changes are valid. Retroactive changes that erase poor performance without traceability are not.
Trap 8: Forgetting management reserve treatment
MR is not part of the normal performance baseline and is not earned as work performance.
Trap 9: Overlooking forecast realism
An EAC may be mathematically possible but operationally unrealistic if TCPI requires performance far better than historical CPI.
Trap 10: Separating schedule logic from earned value
A favorable SPI does not guarantee the critical path is healthy. Always consider schedule logic, float, and milestone status.
Quick calculation review example
Assume:
- BAC = 1,000
- PV = 500
- EV = 400
- AC = 450
Then:
| Metric | Calculation | Result | Meaning |
|---|---|---|---|
| CV | 400 - 450 | -50 | Cost overrun for work performed |
| SV | 400 - 500 | -100 | Behind planned value |
| CPI | 400 / 450 | 0.89 | Earning less than one budget unit per cost unit |
| SPI | 400 / 500 | 0.80 | Earning value slower than planned |
| EAC using CPI | 1,000 / 0.89 | About 1,124 | Forecast overrun if cost efficiency continues |
| VAC | 1,000 - 1,124 | About -124 | Expected overrun |
Interpretation: the project is both cost-unfavorable and schedule-unfavorable. A recovery claim should be supported by corrective actions, schedule logic, and a realistic TCPI.
High-yield decision rules
| If you see… | Think… |
|---|---|
| EV less than AC | Cost overrun |
| EV greater than AC | Cost underrun |
| EV less than PV | Behind plan in earned value terms |
| EV greater than PV | Ahead of plan in earned value terms |
| CPI below 1.0 | Cost efficiency problem |
| SPI below 1.0 | Schedule performance problem |
| EAC greater than BAC | Forecast overrun |
| VAC negative | Expected overrun |
| TCPI much greater than CPI | Recovery target may be unrealistic |
| AC unusually low | Check accruals and accounting lag |
| EV unusually high | Check progress measurement validity |
| Repeated baseline changes | Check change control discipline |
What to practice next
For the AACE Earned Value Professional (EVP) exam code EVP, use this Quick Review as a final concept map, then move into PM Mastery practice:
- Drill formulas until you can identify the right metric without hesitation.
- Practice EAC selection questions where the assumption matters more than arithmetic.
- Work variance-analysis scenarios that require cause, impact, and corrective action.
- Review baseline-control questions involving MR, PMB, BAC, planning packages, and change control.
- Use original practice questions with detailed explanations to expose weak spots before attempting full mock exams.
Next step: start with targeted topic drills on earned value formulas, baseline structure, forecasting, and variance interpretation, then build up to mixed question-bank practice under exam-like timing.
Continue in PM Mastery
Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official AACE questions, copied live-exam content, or exam dumps.