PMI-SP · Domain 3 of 5

PMI-SP Domain 3: Schedule Monitoring and Controlling

The heaviest PMI-SP domain covers what happens after the baseline: collecting honest status, auditing schedule quality, testing recovery options and controlling baseline changes.

Exam weight
35%
Official tasks
6
Estimated questions estimate
~60
Suggested study time estimate
40–55 hrs

About 15 min read Reviewed October 2026

Overview

Schedule Monitoring and Controlling is the execution loop. You collect activity status at defined intervals, gather resource actuals and availability, audit in-house and subcontractor schedules against industry practice, explore alternative execution options with what-if analysis, bring approved risk mitigation work into the schedule through change control, and update the model while documenting every baseline change so the history supports later forensic analysis.

Candidates must interpret performance data, not just record it: schedule variance and SPI, time-based measures such as earned schedule, the baseline execution index (BEI), float erosion and critical path changes. The domain uses the thresholds and change routes set in Domain 1, measures against the baseline built in Domain 2, and feeds Domain 5's status reporting and Domain 4's final performance evaluation.

How it's tested

Items are mostly scenario-based with embedded data: a status update, an earned value snapshot, an audit finding or a delay claim. You decide what the data means, what to do NEXT, or which option BEST recovers the schedule. Earned value and float calculations appear, but the reasoning usually continues past the number to an action.

  • Interpret then act

    Values such as PV, EV and AC or a float change are given; compute the index and choose the action the threshold and critical path justify.

  • Status integrity

    Reported progress conflicts with evidence (100% of duration used, 50% complete, no remaining duration); you validate status before updating the model.

  • Change versus update

    You distinguish a routine schedule update from a baseline change that needs formal approval and documentation.

Reasoning it through

SPI is 0.92, but the late activities have 30 days of total float while the critical path is on plan. The PM wants to crash. Reasoning: the aggregate index hides where the delay sits. Check float and critical path first; the finish date is not currently at risk, so monitor float erosion on that path instead of spending money on compression.

Tasks 6

Official tasks from the PMI outline, in outline order.

3.1 Collect activity status at defined intervals from activity ownersGather actual dates, remaining duration and percent complete each cycle.
What it means
At each status date you obtain actual starts and finishes, remaining duration and progress from activity owners through reports, meetings or inspections, and update the model as of that data date.
What to understand
Remaining duration drives the forecast, not percent complete. Actuals cannot be in the future and remaining work cannot be in the past relative to the data date.
How it shows up
An owner reports 80% complete but expects another four weeks on a five-week task; you validate and use the remaining-duration estimate to forecast.
Common confusion
Deriving remaining duration from percent complete, which gives an optimistic forecast when productivity is lower than planned.
3.2 Collect resource information and updatesTrack resource actuals, utilization and availability.
What it means
You gather hours worked, staffing levels and future availability from timesheets, reports, meetings and inspections, and compare them with the resource-loaded plan.
What to understand
A shortfall in planned resources on upcoming critical work is a leading indicator of delay, even when current progress looks fine.
How it shows up
Timesheets show a key crew at 60% of plan for next month; the scenario asks what to update and whom to inform before the slip appears.
Common confusion
Treating resource tracking as a cost-only activity and missing its effect on future durations.
3.3 Perform schedule analysis and audit on in-house and subcontractor schedulesTest schedule quality using industry standards and checks.
What it means
You analyze the schedule's health against recognized practices, checking missing logic, excessive lags and leads, hard constraints, high float, invalid dates and resource loading, for your own and subcontractor schedules.
What to understand
Health checks (such as the DCMA 14-point assessment, where contracts require it) reveal whether forecasts can be trusted; a subcontractor schedule must integrate with the prime schedule's logic.
How it shows up
A subcontractor submits a schedule with many hard constraints and no logic; the best response is to audit and require a logic-driven resubmission before integrating it.
Common confusion
Accepting a subcontractor's milestone dates without testing the logic that supports them.
3.4 Identify alternative project execution options using what-if analysisModel recovery and optimization scenarios before deciding.
What it means
You copy the model and test options such as re-sequencing, crashing, fast-tracking, adding shifts or changing scope order, then compare their effect on dates, cost, resources and risk.
What to understand
Only options that act on the critical or driving path shorten the finish, and each option must be re-tested because the critical path can move.
How it shows up
Several recovery options are listed with costs and affected activities; you choose the one that shortens the current critical path at the lowest cost and risk.
Common confusion
Running what-if changes directly in the baseline or the live model instead of a copy.
3.5 Incorporate approved risk mitigation activities into the scheduleAdd mitigation work via change control and establish a new PMB.
What it means
When a risk response is approved, you add its activities and logic to the schedule through the defined change process and adjust the PMB accordingly.
What to understand
Mitigation work changes scope and baseline, so it needs approval and documentation; it may draw on management reserve, which then moves into the PMB.
How it shows up
A mitigation has been approved by the risk owner but not through change control; the next step is to process it formally before baselining it.
Common confusion
Adding mitigation activities quietly to the working schedule without a baseline change, which distorts variance analysis.
3.6 Update the schedule model and document schedule baseline changesKeep the model current and maintain a traceable baseline change log.
What it means
You apply approved changes, update logic and durations, save versions, and record what changed, why, who approved it and its effect, so delays can be analyzed later.
What to understand
Documented versions and change records make forensic schedule analysis possible, such as windows or as-planned versus as-built comparisons for delay claims.
How it shows up
A delay claim arises and the team cannot show when a slip began; the scenario tests whether baseline changes and updates were documented.
Common confusion
Re-baselining to remove variances without approval, which destroys the record needed for performance and claim analysis.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Schedule variance and SPI

    SV = EV - PV and SPI = EV / PV compare work earned with work planned to date in cost units.

    Remember
    SPI below 1.0 means less work done than planned; SV negative means behind.
    Tested as
    The most common earned value calculation in control questions.
    Trap
    Dividing PV by EV, which inverts the result and makes a late project look early.

  • Cost variance and CPI

    CV = EV - AC and CPI = EV / AC show cost efficiency of the work completed.

    Remember
    CPI and SPI are independent; a project can be on schedule and over budget.
    Tested as
    Questions often give PV, EV and AC together and ask for one index.
    Trap
    Using AC in the SPI formula.

  • EAC and ETC

    Estimate at completion forecasts final cost; a common form is EAC = BAC / CPI, and ETC = EAC - AC.

    Remember
    Choose the formula by assumption: BAC / CPI if current efficiency continues; AC + (BAC - EV) if the variance was a one-off.
    Tested as
    Appears in forecast and final reporting questions.
    Trap
    Applying BAC / CPI when the stem says the cause will not recur.

  • Earned schedule

    A time-based extension of earned value: ES is the time at which the current EV should have been earned; SPI(t) = ES / actual time.

    Remember
    Cost-based SPI drifts to 1.0 at completion even for late projects; SPI(t) does not.
    Tested as
    Explains why late-stage SPI can look healthy on a late project.
    Trap
    Concluding a project near completion is on time because cost-based SPI is close to 1.0.

  • Baseline execution index (BEI)

    Completed activities divided by activities baselined to finish on or before the status date; the ECO lists it among analysis measures.

    Remember
    A BEI below about 0.95 is a common warning sign that the team is completing fewer tasks than planned.
    Tested as
    Used in schedule health and performance questions.
    Trap
    Counting activities planned for the future in the denominator.

  • Data date (status date)

    The point in time up to which progress is reported; everything left of it is actual, everything right of it is forecast.

    Remember
    Remaining work must be scheduled after the data date.
    Tested as
    Status integrity and audit questions rely on it.
    Trap
    Leaving unstarted work scheduled in the past, which makes the forecast unrealistic.

  • Float erosion

    Steady loss of total float on a path across status cycles.

    Remember
    Trend float on near-critical paths; a path losing float can overtake the critical path.
    Tested as
    Leading indicator questions about which path to watch.
    Trap
    Watching only the current critical path.

  • Schedule health check

    Structured tests of schedule quality, such as missing predecessors or successors, hard constraints, leads, lags, high float, negative float, invalid dates and resource assignment.

    Remember
    Audit before trusting a forecast, especially a subcontractor's.
    Tested as
    Core of the audit task in this domain.
    Trap
    Judging a schedule by whether its milestones look acceptable.

  • What-if analysis

    Testing alternative execution scenarios on a copy of the model to see effects on dates, cost and resources.

    Remember
    Re-run the critical path after each option; savings stop when another path becomes critical.
    Tested as
    Recovery and optimization questions.
    Trap
    Adding up savings from several compressions without checking for path shifts.

  • Re-baselining

    Replacing the baseline after an approved change so that the measurement reference reflects the new agreed plan.

    Remember
    Only through formal change control, documented, with the previous baseline kept.
    Tested as
    Frequent trap in control questions.
    Trap
    Re-baselining to make a poor variance report disappear.

  • Forensic schedule analysis

    Retrospective analysis of delays using as-planned, as-built and updated schedules, for example windows analysis or time impact analysis.

    Remember
    It depends on saved updates and documented baseline changes.
    Tested as
    Linked to the task of documenting baseline changes.
    Trap
    Assuming the current schedule alone can show when and why a delay occurred.

  • Management reserve vs. contingency reserve

    Contingency reserve covers identified risks and sits inside the baseline; management reserve covers unknown-unknowns and sits outside the PMB.

    Remember
    Using management reserve requires a change that moves it into the PMB.
    Tested as
    Applies when approved mitigation work is added.
    Trap
    Spending management reserve without a baseline change.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Schedule update vs. baseline change vs. re-plan

ConceptMeaningKey differenceCommon trap
Schedule update Recording progress, actuals and revised remaining durations each cycle Changes the forecast, not the baseline Seeking change board approval for every status update
Baseline change Approved modification of the baseline after a scope, risk or contract change Needs formal change control and documentation Making it without approval to clear variances
Internal re-plan Re-sequencing or re-detailing future work within the existing baseline totals Keeps baseline dates and budgets intact Treating it as permission to move contract milestones

SPI vs. SPI(t) vs. BEI

ConceptMeaningKey differenceCommon trap
SPI EV / PV in cost units Trends toward 1.0 at completion regardless of lateness Trusting it late in the project
SPI(t) Earned schedule / actual time in time units Stays meaningful through completion Confusing earned schedule with earned value
BEI Activities completed / activities due by status date Counts tasks, not value Ignoring that small tasks can inflate it while large critical tasks lag

Percent complete vs. remaining duration vs. physical percent complete

ConceptMeaningKey differenceCommon trap
Duration percent complete Elapsed duration as a share of total duration Measures time used, not work done Reading it as progress
Remaining duration Owner's estimate of working time still needed Drives the forecast finish Calculating it from percent complete
Physical percent complete Measured share of work accomplished Basis for earned value Using subjective guesses where objective measures exist

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Index without location

    What candidates pick
    Crash or fast-track because SPI is below 1.0.
    Why it looks right
    A low SPI signals the project is behind.
    Why it's wrong
    SPI aggregates all work; if the late work has float, the finish may not be at risk and compression wastes money.

    Clue to watch for The stem gives float values or says the critical path is on plan.

  2. Cosmetic re-baseline

    What candidates pick
    Re-baseline to the current forecast so reports show no variance.
    Why it looks right
    It makes reports cleaner and calms stakeholders.
    Why it's wrong
    Without an approved change it hides real performance and destroys the history needed for analysis and claims.

    Clue to watch for No approved change request is mentioned, only poor performance.

  3. Status at face value

    What candidates pick
    Enter the reported percent complete and let the tool compute the finish.
    Why it looks right
    The owner provided the number and the tool does the math.
    Why it's wrong
    The reported progress may conflict with elapsed time or remaining work; status must be validated first.

    Clue to watch for Numbers that do not reconcile, such as 90% complete after 50% of duration with half the deliverables outstanding.

  4. Trust the subcontractor

    What candidates pick
    Insert the subcontractor's milestone dates into the master schedule as constraints.
    Why it looks right
    The subcontractor owns that work and committed to those dates.
    Why it's wrong
    Dates without auditable logic cannot be integrated or forecast; the ECO expects audit against industry standards.

    Clue to watch for Words like 'summary bars only', 'no logic' or 'constrained dates' in the subcontractor submission.

  5. Adding savings blindly

    What candidates pick
    Total the days saved by each compression option to get the new finish.
    Why it looks right
    Simple arithmetic on the listed savings.
    Why it's wrong
    Once a parallel path becomes critical, further compression of the original path saves nothing.

    Clue to watch for A near-critical path with only a few days less duration appears in the network.

  6. Mitigation without change control

    What candidates pick
    Add the approved mitigation tasks straight into the working schedule.
    Why it looks right
    The risk owner already approved the response.
    Why it's wrong
    Mitigation work alters scope, budget and baseline, so it must pass through the defined change process to establish a new PMB.

    Clue to watch for The stem says the response was approved by the risk owner, not by the change control authority.

Answer framework

Use this sequence when a control question gives status or performance data and asks what to do next.

  1. Validate the status: actuals before the data date, remaining work after it, and reported progress consistent with evidence.
  2. Calculate the relevant measures, such as SPI, SV, float change or BEI, and compare them with the thresholds in the schedule management plan.
  3. Locate the variance on the network and determine whether it affects the critical path, near-critical paths or contract milestones, and by how much.
  4. Test recovery options on a copy of the model with what-if analysis, rechecking the critical path after each option.
  5. Route any baseline-affecting change through formal change control, update the model, and document the change and its rationale.

Practice question

At the status date, planned value is $500,000, earned value is $440,000 and actual cost is $470,000. The schedule management plan requires corrective action analysis when SPI falls below 0.90. Which statement is correct?

Want more like this? The PMI-SP practice test has questions for every domain.

Checklist

0 of 12

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Begin with the status cycle, because every other task depends on valid data. Practice updating a small schedule by hand: set a data date, enter actuals, assign remaining durations, and check that nothing unstarted remains in the past.

Next, drill earned value until the formulas are automatic: SV, SPI, CV, CPI, EAC variants and ETC. Then add earned schedule and BEI so you can explain why each index can mislead on its own. Pair each calculation with the question 'is the late work on the critical path?', because the exam rewards that second step.

Commonly underestimated areas are schedule audits and baseline change documentation. Learn the main health checks and practice spotting them in a description of a poor schedule, and be clear on when a change needs formal approval versus a routine update.

Afterwards, practice scenario sets that mix calculation and action, and time yourself, since this domain carries more items than any other. Then review Domain 5, which turns these results into stakeholder reporting.

FAQ

Why is this the most important PMI-SP domain?

It carries the largest weight at 35%, about 60 of 170 items as a planning estimate, and it combines calculation with judgment about forecasting and change control.

Which earned value formulas do I need?

SV = EV - PV, SPI = EV / PV, CV = EV - AC, CPI = EV / AC, EAC variants such as BAC / CPI and AC + (BAC - EV), and ETC = EAC - AC. Know earned schedule and SPI(t) as well.

What is the baseline execution index?

BEI divides activities completed by activities that the baseline says should be finished by the status date. It is a task-count measure, so read it alongside critical path status.

When is re-baselining appropriate?

Only after an approved change such as added scope, an approved mitigation or a contract modification, processed through formal change control and documented with the prior baseline kept.

Will I be tested on forensic delay methods?

The ECO ties baseline change documentation to supporting forensic analysis, so understand why saved updates matter and the purpose of methods such as windows and time impact analysis, rather than detailed claim procedure.

How does this domain relate to Schedule Planning and Development?

Domain 2 builds the baseline and PMB; this domain measures performance against them and controls changes. Network skills from Domain 2 are reused here on live data.

How long should I study Domain 3?

A planning estimate is 40 to 55 hours, weighted toward earned value practice and status and audit scenarios.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 3 knowledge

You have covered status validation, schedule audits, what-if recovery, earned value and baseline change control. Check whether you can move from a calculated index to the right action.

Take the PMI-SP practice test Check your PMI-SP readiness

Keep going