EVP — AACE Earned Value Professional Scenario Practice Guide

Scenario questions on the AACE Earned Value Professional (EVP) exam are rarely just calculation exercises. They often describe a project controls situation, give partial earned value data, mention a stakeholder concern, and ask for the best interpretation or next step.

Use this guide to slow down, separate relevant facts from background detail, and choose the answer that is most defensible under earned value management principles. This is an independent exam-preparation guide and is not affiliated with AACE International.

The EVP scenario mindset

An EVP scenario usually asks you to make a professional judgment using earned value, cost engineering, project controls, and baseline management concepts. Your job is not to pick the most dramatic answer or the answer that sounds the most senior. Your job is to identify what the facts support.

A strong scenario answer is usually:

• Consistent with the performance measurement baseline.
• Traceable to approved scope, schedule, and budget.
• Based on reliable data before major conclusions are made.
• Within the role and authority described in the question.
• Focused on analysis, communication, corrective action, or change control in the proper order.
• Careful not to hide variances by changing the baseline without authorization.

Before reading the answer choices in detail, ask: What decision is the scenario really asking me to make?

First identify your role in the scenario

The right next step depends heavily on who you are in the situation. An EVP-style scenario may place you in the role of a project controls analyst, cost engineer, control account manager, project manager, scheduler, contractor representative, owner representative, or independent reviewer.

If you are the project controls or earned value analyst

You are usually expected to:

• Verify data integrity.
• Calculate and interpret EV metrics.
• Identify variance drivers.
• Support the control account manager or project manager with analysis.
• Prepare reports, forecasts, and recommendations.
• Avoid making unauthorized scope or baseline decisions.

A good answer often starts with confirming the data, performing variance analysis, or presenting objective performance information to the responsible manager.

If you are the control account manager

You are closer to the work. You may be responsible for:

• Explaining schedule and cost variances.
• Identifying root causes.
• Developing corrective action plans.
• Reviewing estimates to complete.
• Ensuring reported progress reflects actual accomplishment.

For this role, the best answer may involve analyzing the control account, coordinating with the project team, and documenting corrective action.

If you are the project manager

You may have broader authority, but you still operate within governance. You may:

• Review project-level performance trends.
• Decide whether corrective action is adequate.
• Communicate with management, customer, or sponsor.
• Initiate formal change control when scope, budget, or schedule baselines are affected.
• Escalate issues that exceed authority or tolerance.

Even as project manager, do not assume you can simply rebaseline, absorb new scope, or change reporting methods without proper approval.

If you are an independent reviewer or surveillance team member

The question may be testing whether the EVMS process is reliable. Focus on:

• Whether performance is measured objectively.
• Whether the baseline is traceable and controlled.
• Whether actual costs, earned value, and schedule status are aligned.
• Whether changes are authorized before inclusion in the baseline.
• Whether variance explanations and forecasts are credible.

In this role, the answer is often about identifying a process weakness, requesting supporting evidence, or recommending corrective action to restore control system integrity.

Determine the project delivery and control context

EVP scenarios often assume a formal earned value environment, typically with defined scope, a time-phased budget, a schedule, control accounts, work packages, and reporting periods. Still, read the context carefully.

Ask:

• Is the project using a predictive, agile, or hybrid approach?
• Is work planned in detail now, or is rolling-wave planning being used?
• Is the question about baseline planning, execution reporting, variance analysis, forecasting, change control, or system validation?
• Is the work authorized, not yet authorized, or pending change approval?
• Are the reported values current, preliminary, disputed, or missing?

For earned value, the key point is not the label of the delivery approach. The key point is whether there is an approved basis for measuring progress and comparing planned value, earned value, and actual cost.

In a hybrid environment, for example, some work may be measured through agile increments or completed features, but the scenario still requires disciplined measurement rules, authorized budgets, reliable actual costs, and controlled baseline changes.

Build a quick fact map before choosing

Scenario questions often include more information than you need. Create a quick mental map.

Look for these facts:

• Scope: What work is being discussed? Is it part of the approved baseline?
• Time: What reporting period or status date is being referenced?
• Budget: What is the budgeted value of the work? Is BAC or control account budget provided?
• Performance: What has actually been accomplished?
• Cost: What actual costs have been recorded?
• Schedule: Is progress early, late, out of sequence, or based on invalid logic?
• Authority: Who can approve the decision?
• Trigger: Is there a variance, risk, change request, data issue, or stakeholder concern?
• Required response: Does the question ask for interpretation, calculation, analysis, communication, or action?

A useful habit is to restate the scenario in one sentence:

“The project has an approved baseline, the control account is underrunning cost but behind schedule, and the question asks what the project controls analyst should do before recommending corrective action.”

That sentence is often enough to eliminate answer choices that react to the wrong problem.

Find the actual decision point

Many EVP scenarios contain several facts, but only one decision point. The question stem usually reveals it.

If the question asks “What does this indicate?”

You are interpreting data. Focus on the EV metrics and the meaning of the variance.

Useful checks:

• Cost variance: \(CV = EV - AC\)
• Schedule variance: \(SV = EV - PV\)
• Cost performance index: \(CPI = EV / AC\)
• Schedule performance index: \(SPI = EV / PV\)

Then translate the result into project language:

• Positive CV means earned value exceeds actual cost for the work performed.
• Negative CV means the work performed cost more than its earned value.
• Positive SV means more value has been earned than planned by the status date.
• Negative SV means less value has been earned than planned by the status date.

Do not stop at the arithmetic if the scenario asks for management meaning. Decide whether the result calls for variance analysis, forecast review, schedule analysis, or corrective action.

If the question asks “What should be done next?”

You are choosing a sequence. The best answer is usually not the most extreme action. Use this order:

1. Verify the facts if data quality is uncertain.
2. Determine whether there is an approved baseline or authorized change.
3. Calculate or analyze the relevant performance information.
4. Identify cause and impact.
5. Communicate with the responsible party.
6. Recommend or implement corrective action within authority.
7. Escalate only when required by governance, threshold, or risk severity.

If the question asks “Which forecast is most appropriate?”

Look for the assumption about future performance.

For example:

• If current cost efficiency is expected to continue, an answer using CPI may be defensible.
• If past variance was a one-time event and future work is expected to perform as planned, a different estimate-to-complete logic may be better.
• If the scenario gives a required formula or assumption, follow that information rather than applying a preferred formula automatically.
• If the forecast is based on unreliable progress or missing actuals, the first issue may be data quality.

Forecasting questions test judgment, not just formula memory.

If the question asks “How should the baseline be handled?”

Focus on authorization and traceability.

A defensible answer usually respects these principles:

• The performance measurement baseline should reflect approved scope, schedule, and budget.
• Potential changes should not be treated as approved work until authorized through the applicable process.
• Baseline changes should not be used simply to erase unfavorable performance.
• Management reserve, undistributed budget, and control account budgets should be handled according to the project’s approved control process.
• Replanning and reprogramming require discipline, documentation, and approval.

Separate facts from distractors

EVP scenarios often include background details that sound important but do not change the earned value decision. Do not ignore them, but classify them.

Facts that usually matter

Pay close attention to:

• Approved versus proposed scope.
• Status date and reporting period.
• EV, PV, AC, BAC, EAC, ETC, CV, SV, CPI, and SPI.
• Whether actual costs are complete and recorded in the correct period.
• Whether progress measurement is objective.
• Whether the schedule is integrated and reflects the real sequence of work.
• Whether a variance threshold is provided in the scenario.
• Whether a customer, sponsor, or management action is authorized or only requested.
• Whether the issue affects a control account, the total project, or the EVMS process.

Details that may be secondary

These details may matter only if tied to the decision:

• The seniority of the stakeholder raising the concern.
• Emotional wording such as “urgent,” “critical,” or “high visibility.”
• A contractor or customer preference that is not formally approved.
• Historical performance from a different project.
• A contract type detail that does not affect the question being asked.
• A proposed recovery plan with no supporting schedule or cost analysis.

A senior stakeholder’s request does not replace formal change control. A high-visibility variance still needs analysis. A favorable CPI does not automatically solve a schedule problem.

Read EV data as a story, not just numbers

Earned value metrics describe relationships among planned work, accomplished work, and actual cost. In scenario questions, translate the numbers into a project story.

When EV is less than PV

The project has earned less value than planned by the status date. Ask:

• Is the work actually behind, or is progress being measured incorrectly?
• Is the schedule logic realistic?
• Are activities out of sequence?
• Is the delay isolated to one control account or affecting the critical path?
• Does the scenario ask for schedule variance in EV terms or true schedule impact?

Remember that EV schedule variance is not always the same as critical path delay. If the question gives network schedule facts, use them.

When AC is greater than EV

The work performed has cost more than its earned value. Ask:

• Is this due to labor inefficiency, material price variance, rework, subcontractor cost, or accounting timing?
• Are actual costs complete and mapped to the correct work?
• Is the variance expected to continue?
• Does the estimate to complete need revision?
• Is a corrective action plan needed?

A negative cost variance is not fixed by moving budget unless there is an authorized scope or baseline reason.

When CPI and SPI point in different directions

Mixed signals are common.

Examples:

• CPI favorable, SPI unfavorable: work performed is costing less than expected, but less work has been completed than planned.
• CPI unfavorable, SPI favorable: more work has been completed than planned, but at higher cost.
• CPI near 1.0, SPI unfavorable: cost efficiency may look acceptable, but schedule progress is lagging.
• SPI near 1.0, CPI unfavorable: schedule progress may be acceptable, but cost performance needs attention.

Do not let one favorable indicator cancel the other. Interpret each metric in relation to the decision being asked.

Decide whether analysis, communication, or action comes first

Many scenario answer choices are plausible but out of sequence. Use the situation to decide what comes first.

Start with data validation when the facts are unreliable

Choose validation before management action when the scenario indicates:

• Actual costs are missing, late, duplicated, or posted to the wrong account.
• Progress was estimated informally instead of measured by the approved method.
• EV was claimed before objective completion criteria were met.
• The status date is inconsistent across cost and schedule data.
• The baseline appears to include unauthorized work.

In these cases, a strong answer may be to reconcile the data, review source records, or correct the reporting process before drawing conclusions.

Start with variance analysis when the data are reliable

If the scenario provides reliable EV data and asks about performance, analyze the variance.

Good next steps include:

• Compare actual results to the baseline.
• Determine the root cause of cost or schedule variance.
• Assess whether the variance is isolated or systemic.
• Evaluate impact on EAC, completion date, or key milestones.
• Request a control account manager explanation if appropriate.

Do not jump straight to rebaselining, contract escalation, or executive reporting unless the scenario gives a reason.

Start with communication when the responsible party must be engaged

Communication comes first when another role owns the information or action.

Examples:

• A control account manager must explain a variance and propose corrective action.
• A scheduler must evaluate whether an EV schedule variance affects the critical path.
• Finance must correct actual cost timing before the report is finalized.
• A customer request must be clarified before it is treated as scope.

The best answer may be collaborative and evidence-based: meet with the responsible owner, review the data, and document the result.

Start with formal change control when scope changes

If the scenario introduces new, deleted, or modified scope, ask whether it is approved.

For proposed or directed changes:

• Confirm whether the change is authorized.
• Evaluate cost, schedule, and performance baseline impact.
• Process the change through the applicable approval path.
• Update the baseline only after approval.
• Keep current performance reporting separate from unapproved change assumptions.

If a customer asks for added work, the best EVP answer is usually not “begin work and adjust the baseline later.” It is to follow the authorization and change control process.

Avoid premature escalation

Escalation may be correct, but it is rarely the first professional action unless the scenario gives a clear trigger.

Escalation is more defensible when:

• The issue exceeds the role’s authority.
• A required threshold is exceeded and the scenario says escalation is required.
• A material risk or compliance issue cannot be resolved at the project level.
• The team refuses to correct invalid reporting.
• The customer or management must approve a baseline or contractual change.

Before escalating, ask:

• Have the facts been verified?
• Has the responsible manager been consulted?
• Is the impact understood?
• Is the escalation required by governance or necessary for a decision?
• Can the issue be handled through normal variance, forecast, or change control processes?

A calm, controlled response is usually stronger than an immediate executive escalation.

Use thresholds only when they are given

Some scenarios provide variance thresholds, reporting thresholds, or management tolerances. If the question gives them, use them directly.

If no threshold is provided, do not invent one. Instead, use the qualitative facts:

• Is the variance significant in context?
• Is the trend worsening?
• Does it affect completion forecast?
• Does it affect a key milestone or control account?
• Does it require a variance explanation or corrective action under the stated project process?

If an answer depends on an unstated rule, be careful. The best answer should be supported by the scenario facts.

Interpret baseline and change facts carefully

Baseline discipline is central to earned value reasoning. When a scenario mentions changes, budgets, or replanning, slow down.

Approved change

If the change is approved, the question may ask how to incorporate it.

Look for answers that:

• Update scope, schedule, and budget consistently.
• Maintain traceability to authorization.
• Adjust the performance measurement baseline through the approved process.
• Avoid mixing pre-change variance with post-change performance.

Proposed change

If the change is only proposed, pending, or requested, the current baseline generally remains the basis for performance measurement until authorization occurs.

The best answer may be to:

• Analyze the potential impact.
• Prepare a change request or proposal.
• Communicate assumptions clearly.
• Keep the existing baseline intact until approval.

Internal replanning

If the team wants to move budget or revise work plans, ask:

• Is the scope unchanged?
• Is the change within authorized control account planning rules?
• Does it preserve historical performance visibility?
• Is it properly documented?
• Does it require approval?

Replanning can be legitimate, but it should not be used to make unfavorable variance disappear.

Recognize EVMS process-quality scenarios

Not every scenario asks, “What is the CPI?” Some ask whether the earned value system is producing reliable management information.

Process-quality concerns include:

• Work is earning value without objective completion evidence.
• Actual costs are not aligned with the work performed.
• Schedule activities are not traceable to control accounts.
• Budgets are assigned without authorized scope.
• Control account plans are inconsistent with the integrated master schedule.
• Variance explanations repeat symptoms but do not identify root cause.
• EAC updates are mechanical and ignore current performance trends.
• Baseline changes are made after the fact to match actual results.

When the issue is system quality, the best answer often addresses process correction, documentation, reconciliation, or surveillance findings rather than a narrow calculation.

Choose the best next step

When answer choices are close, compare them using a defensibility test.

Ask which answer:

• Uses the approved baseline as the reference point.
• Relies on verified performance data.
• Addresses the stated problem rather than a side issue.
• Fits the role’s authority.
• Preserves transparency of cost and schedule performance.
• Follows analysis before action when facts are incomplete.
• Follows change control before baseline updates.
• Communicates with the right stakeholder at the right time.
• Produces useful management information.

The best answer may not be perfect. It only needs to be the most defensible among the options.

Short scenario examples

Example 1: Negative cost variance with reliable data

A control account has EV lower than AC. The actual costs have been reconciled, and the progress measurement method was applied correctly. The project manager asks what should happen next.

A defensible sequence is:

1. Confirm the cost variance and CPI.
2. Determine the root cause with the control account manager.
3. Assess whether the variance affects ETC and EAC.
4. Develop or review corrective action.
5. Report the variance according to the project process.

A less defensible response would be to immediately change the baseline to remove the variance.

Example 2: Customer requests added work

A customer asks the team to add reporting features not included in the approved scope. The team believes the work is small and wants to include it in the next reporting period.

A defensible response is:

1. Determine whether the work is authorized.
2. Analyze cost and schedule impact.
3. Process the change through the applicable approval path.
4. Update the baseline only after approval.
5. Measure performance against the approved baseline.

The important decision point is not whether the team can technically perform the work. It is whether the scope is authorized for baseline and EV reporting.

Example 3: Favorable CPI but schedule concern

A project shows a favorable CPI but an unfavorable SPI. Management asks if the project is healthy because it is under budget.

A defensible interpretation is:

• Cost efficiency appears favorable for the work accomplished.
• The project has earned less value than planned by the status date.
• Schedule analysis is needed to determine milestone or critical path impact.
• Forecasts should consider both cost and schedule information.

The favorable CPI does not eliminate the schedule issue.

Example 4: Incomplete actual cost data

The monthly report shows a favorable cost variance, but the scenario states that major subcontractor invoices have not yet been recorded.

A defensible next step is to reconcile or accrue actual costs according to the project’s cost collection process before relying on the variance.

The issue is data completeness. A favorable CPI based on incomplete actuals is not reliable management information.

Final review checklist for EVP scenarios

Before selecting an answer, pause and check:

• What role am I playing?
• Is the question asking for interpretation, calculation, communication, corrective action, or change control?
• Is the work approved baseline scope?
• Are EV, PV, and AC reliable and aligned to the same status date?
• Is this a cost problem, schedule problem, scope change, forecast issue, or system-quality issue?
• Do I need to calculate, analyze, validate, communicate, or escalate?
• Does the answer preserve baseline integrity?
• Does the answer fit the authority in the scenario?
• Am I choosing the next best step, not the final desired outcome?

Practical next step

For final review, practice EVP scenarios in sets. After each question, write one sentence identifying the role, the actual decision point, and the fact that made the correct answer defensible. Then use topic drills for weak areas such as variance analysis, forecasting, baseline control, progress measurement, and EVMS data integrity before moving into full mock exams.