Prepare for PMI Scheduling Professional (PMI-SP) with free sample questions, a 170-question full-length diagnostic, scheduling domain drills, timed mock exams, baseline, variance, recovery, communication, and schedule-control scenarios, and detailed explanations in PM Mastery.
Start a practice session for PMI Scheduling Professional (PMI-SP) below, or open the full app in a new tab. For the best experience, open the full app in a new tab and navigate with swipes/gestures or the mouse wheel—just like on your phone or tablet.
Open Full App in a New TabA small set of questions is available for free preview. Subscribers can unlock full access by signing in with the same app-family account they use on web and mobile.
Use on iPhone or Android too: PM Mastery on the App Store or PM Mastery on Google Play using the same PM Mastery account you use on web. The same PM Mastery subscription works across web and mobile.
Free diagnostic: Try the 170-question PMI-SP full-length practice exam before subscribing. Use it as one schedule-control baseline, then return to PM Mastery for timed mocks, topic drills, explanations, and the full PMI-SP question bank.
PMI-SP is PMI’s scheduling certification for practitioners who build logical schedule models, baseline them, analyze variance, optimize recovery options, and communicate date impacts clearly.
Official source check: Last checked May 5, 2026 against PMI's public PMI-SP certification page.
PMI's public page lists 170 multiple-choice questions, 210 minutes, 150 scored questions plus 20 unscored pretest questions, and the five weighted scheduling domains used below. Confirm current appointment rules and eligibility directly with PMI before booking.
For the latest official exam details and requirements, see: https://www.pmi.org/certifications/scheduling-sp
Source: PMI Scheduling Professional (PMI-SP) Exam Content Outline, 2012.
PMI-SP questions usually reward the option that protects schedule logic, reveals the true driver of the date, and communicates a defensible recovery or control decision instead of just manipulating software output.
| Domain | Weight |
|---|---|
| Schedule Strategy | 14% |
| Schedule Planning and Development | 31% |
| Schedule Monitoring and Controlling | 35% |
| Schedule Closeout | 6% |
| Stakeholder Communications Management | 14% |
Use these filters when two answers both sound plausible. PMI-SP questions often reward the answer that protects schedule credibility, not the answer that makes the date look better temporarily.
| Scenario signal | First check | Strong answer usually… | Weak answer usually… |
|---|---|---|---|
| The finish date moved | What changed on the critical or near-critical path? | Identifies the driver, validates progress data, and communicates forecast impact before choosing recovery. | Compresses work without proving the date driver. |
| A stakeholder wants a faster date | What trade-off is being accepted? | Evaluates crashing, fast tracking, scope, resource, risk, quality, contract, and cost effects before recommending. | Promises a date by adding resources or overlaps without impact analysis. |
| The baseline is questioned | Was the baseline approved and is the change controlled? | Uses formal change control and variance analysis before rebaselining. | Moves the baseline to hide performance variance. |
| Logic looks suspicious | Are dependencies, constraints, calendars, and leads/lags defensible? | Fixes schedule quality issues before trusting float, critical path, or forecast output. | Treats software output as reliable even when the model is weak. |
| Progress data conflicts | Which source is reliable enough for forecasting? | Reconciles actuals, remaining duration, percent complete, and owner input before reporting. | Reports optimistic progress because it reduces variance. |
| Recovery is required | Which option preserves the project objective with acceptable risk? | Selects a recovery option with clear assumptions, owners, risks, and stakeholder communication. | Chooses the fastest option without checking feasibility or side effects. |
| If you are deciding between… | Main distinction |
|---|---|
| PMI-SP vs PMP | PMI-SP is specialist scheduling depth; PMP is PMI’s broad project-leadership route. |
| PMI-SP vs PMI-RMP | PMI-SP is schedule focused; PMI-RMP is risk focused. |
| PMI-SP vs CAPM | PMI-SP is advanced schedule logic and control; CAPM is an entry-level PM route. |
| PMI-SP vs AACE PSP or CST | PMI-SP is PMI’s scheduling credential; AACE PSP is AACE’s professional planning-and-scheduling route and AACE CST is the technician-level scheduling route. |
Use this map when reviewing missed questions. Most PMI-SP misses are not about remembering a scheduling term; they are about using the term to make a defensible schedule-control decision.
| Domain | What the exam is really testing | What PM Mastery practice should force you to decide | Common wrong-answer trap |
|---|---|---|---|
| Schedule Strategy | Whether the schedule approach supports the project objective and governance environment | Which scheduling method, level of detail, calendar logic, reporting cadence, and control rules fit the work | Building a schedule model before agreeing how it will be governed |
| Schedule Planning and Development | Whether the model is logically sound enough to forecast | How to sequence activities, estimate durations, assign resources, validate constraints, and protect traceability | Accepting weak dependencies, missing calendars, or hard constraints because the software still calculates a date |
| Schedule Monitoring and Controlling | Whether progress and variance are interpreted correctly | When to update actuals, analyze critical path movement, forecast completion, escalate, or recommend recovery | Reacting to variance without finding the real driver |
| Schedule Closeout | Whether schedule data is closed, archived, and converted into useful lessons | What should be reconciled, documented, and transferred before the schedule is considered closed | Treating closeout as administrative cleanup only |
| Stakeholder Communications Management | Whether schedule information is understandable and decision-ready | What each stakeholder needs: forecast, variance, assumptions, impact, options, or decision request | Sending raw schedule data without interpretation or recommendation |
Use this once you understand the schedule domains and need to convert practice into exam readiness.
| Window | What to do | What not to do |
|---|---|---|
| Days 7-5 | Take one mixed timed set or the full-length diagnostic, then classify every miss by strategy, planning, monitoring/control, closeout, communication, or timing. | Do not only reread explanations; write the schedule-control rule you missed. |
| Days 4-3 | Drill planning and monitoring/control because they carry the most weight and create the most scenario traps. | Do not spend most of the final week on low-weight closeout if your variance and recovery misses are unresolved. |
| Days 2-1 | Review recurring traps: weak logic, informal rebaselining, misleading percent complete, critical path changes, and recovery options with hidden risks. | Do not start a large new run if fatigue will distort your readiness signal. |
| Exam day | Read for the required decision, identify the schedule driver, and eliminate answers that hide variance or bypass control. | Do not choose an answer just because it makes the date look better. |
The goal is not to memorize every schedule scenario. The goal is to build transferable schedule-control judgment so you can interpret a new prompt under time pressure.
If you can complete several varied timed attempts at 75% or higher, explain the schedule driver behind your missed questions, and consistently choose responses that protect baseline discipline, forecast credibility, and stakeholder decision quality, it is usually time to sit the exam rather than repeating recognized questions. More practice still helps when it targets a weak domain, but repeating sets you already remember can make readiness look stronger than it is.
Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.
Try these 24 public sample questions for PMI-SP. They are original PM Mastery practice items aligned to schedule strategy, planning, development, monitoring, control, closeout, and communication decisions. They are not PMI exam questions and are not copied from any exam sponsor.
Topic: Stakeholder Communications Management
On a hybrid system implementation, the baseline customer go-live milestone is July 30. As of the July 10 status date, a vendor defect has delayed interface testing on the driving path, and the current forecast shows go-live slipping 7 working days. A joint sponsor/customer status report is due today, and the schedule management plan requires threatened commitments to be reported with impact, assumptions, and next steps; the baseline can change only through approved change control. What is the best action?
Best answer: A
Explanation: When a commitment is threatened, stakeholders need more than an “at risk” label. The best communication states the forecast impact, the assumptions behind that forecast, and the next corrective steps, while keeping the baseline separate until a formal change is approved.
Effective schedule communication should help stakeholders understand both the likely outcome and what will happen next. Here, the delay is already affecting the driving path, the go-live commitment is threatened, the report is due now, and the plan explicitly requires impact, assumptions, and next steps. The scheduler should therefore communicate the current forecast slip, the key assumptions that make that forecast credible, and the immediate recovery or decision actions underway, while keeping the approved baseline unchanged until change control approves any revision.
A vague warning or a hidden baseline change weakens both schedule control and stakeholder trust.
This meets the reporting requirement by giving stakeholders a decision-ready forecast while preserving the approved baseline.
Topic: Schedule Monitoring and Controlling
At the June 1 data date, float analysis shows the contractual commissioning milestone is forecast 8 working days late. A what-if analysis shows that adding a second crew to the current critical-path activity would recover all 8 days but add $40,000. The schedule management plan requires formal change approval for any recovery action adding more than $25,000, and any contractual milestone slip over 5 days must be escalated to the sponsor in the current reporting cycle. What should be done before implementing the recovery?
Best answer: C
Explanation: The analysis shows a workable recovery on the critical path, but governance rules still apply. Because the action adds more than $25,000 and addresses a contractual milestone slip greater than 5 days, the impact must be escalated and formally approved before the team changes execution.
The key concept is schedule recovery control: a technically valid recovery option is not automatically authorized for implementation. Here, the what-if analysis shows that adding a second crew to the critical-path activity can recover the full 8-day delay, so the option is schedule-effective. But the schedule management plan sets two mandatory triggers: the contractual milestone variance exceeds the 5-day escalation threshold, and the proposed recovery adds more than $25,000. That means the project team must communicate the variance and proposed recovery impact to the sponsor and route the action through formal change approval before changing execution. After approval, the team can update the forecast and, if authorized, any controlled baseline information. A favorable analysis result supports the request; it does not replace approval.
The recovery is supported by analysis, but the cost and milestone-slip thresholds require escalation and formal approval before execution.
Topic: Schedule Monitoring and Controlling
On a hospital fit-out project, the status date is June 14. Interior signage fabrication is forecast to finish 5 working days later than baseline. That path still has 7 days of total float, the driving path remains testing -> regulatory inspection -> handover, and the committed handover milestone is still forecast for July 30. What is the best control action?
Best answer: D
Explanation: Because the delayed activity is on a non-driving path with 7 days of total float, its 5-day slip does not currently threaten the July 30 handover. The right response is to keep the approved baseline, show the real forecast variance, and monitor whether float continues to erode.
Schedule control should focus on whether variance affects the driving path or a committed milestone. Here, the delayed signage activity is 5 days late, but its path still has 7 days of total float and the handover milestone forecast remains July 30, so there is no immediate milestone threat to recover. The scheduler should enter truthful status, preserve the approved baseline, and communicate the variance as a monitored condition. If later updates consume the remaining float or shift the driving path, then corrective action may be needed. Until then, this is a non-driving variance, not a reason to compress work or replace the baseline. A visible variance is better than a cosmetically on-time schedule.
The delayed work is non-driving with enough remaining float, so the correct action is to show the variance and continue monitoring rather than recover or rebaseline.
Topic: Schedule Planning and Development
A scheduler is reviewing a draft baseline for a facilities upgrade. Control account CA-07 represents 28% of the project budget. The WBS dictionary lists four deliverables and two external handoffs under CA-07, but the schedule model shows only two activities: Install equipment (55 working days) and Commission system (20 working days). The project finish milestone currently has 10 working days of total float. Before approving the baseline, which schedule analysis approach would best test whether CA-07 is insufficiently decomposed and could make the baseline unreliable?
CA-07 decomposed furtherBest answer: D
Explanation: A coarse control account can make a schedule look stable even when important work and handoffs are not defined as activities. The best analysis is to decompose that area further and run what-if scenarios, because this tests whether missing detail changes the path, dates, or float enough to undermine the baseline.
The core issue is not current float or current path length; it is that the schedule model may be structurally incomplete. When a large control account contains multiple deliverables and handoffs but is represented by only two long activities, the activity definition is too weak to support a credible baseline. A what-if analysis using a finer decomposition is the best choice because it tests whether added internal activities, logic, and handoffs materially change dates, float, or the driving path.
By contrast, analyzing the existing coarse model more deeply can still leave hidden scope gaps undetected.
Testing alternate logic and durations after finer decomposition is the best way to reveal whether the coarse control account is hiding schedule drivers and weakening baseline credibility.
Topic: Schedule Planning and Development
In a data center cutover, the scheduler wants to link Begin monitoring on replacement platform as the predecessor to End monitoring on legacy platform as the successor. The successor can occur only after the predecessor starts. Which relationship type should be used?
Best answer: C
Explanation: The key clue is that the successor activity is allowed to finish only after the predecessor starts. That pattern is a start-to-finish relationship, often used for cutovers or handoffs where old work continues until replacement work begins.
Logic relationships define which event in a predecessor controls which event in a successor. Here, the successor is End monitoring on legacy platform, and it may finish only after the predecessor, Begin monitoring on replacement platform, has started. That is a start-to-finish dependency.
FS: successor starts after predecessor finishesSS: successor starts after predecessor startsFF: successor finishes after predecessor finishesSF: successor finishes after predecessor startsSF is less common than the other three, but it is the right choice for relief, cutover, and handoff situations. The closest trap is FS, which reverses the intended logic and models the opposite sequence.
Start-to-finish is correct because the successor may finish only after the predecessor has started.
Topic: Schedule Monitoring and Controlling
A predictive project uses a 5-day workweek calendar. The status date is September 30, 2026. Regulatory Filing Complete has a contractual Finish No Later Than date of December 4, 2026. The current forecast finishes December 1, 2026, and overall SPI is 1.00. The driving path is Integration Test -> Defect Fixes -> Validation Package -> Regulatory Filing Complete.
| Update | Total float on driving path |
|---|---|
| July 31 | 12 days |
| August 31 | 7 days |
| September 30 | 3 days |
What is the best scheduling judgment?
Must Finish On December 4, 2026.Best answer: C
Explanation: The schedule still looks acceptable in a single snapshot, but the trend is deteriorating. Losing float across consecutive updates on the same driving path is an early warning that the forecast is becoming less credible, even while SPI remains 1.00 and the milestone is still early.
In schedule control, a single metric can hide emerging problems. Here, the milestone is still forecast to meet its contractual date and SPI is neutral, but the same driving path has lost float from 12 days to 3 days over three updates. That trend shows the project is steadily consuming schedule flexibility. The right response is to validate status quality, remaining durations, and logic on that path, then decide whether corrective action is needed.
A stronger date constraint would only mask slippage in the model, and rebaselining would replace the control reference without approved change control. Path-level trend analysis is more useful because it warns of likely future variance before a single summary metric turns negative.
Repeated float erosion on the driving path is a stronger early warning than one favorable SPI snapshot or a still-on-time milestone forecast.
Topic: Schedule Strategy
On a hybrid product rollout using a Monday-Friday calendar, the data date is July 12, 2026. System test is finish-to-start after build completion, and the regulatory go-live milestone on August 31 has zero total float. Several team leads are typing forecast finish dates and adding Must Finish On constraints so the weekly report still shows August 31. The schedule management plan requires status as of the data date and formal change control for committed date changes. What should the scheduler communicate to improve compliance and preserve schedule-model integrity?
Must Finish On constraints if leads explain them in status comments.Best answer: B
Explanation: The best communication is a clear update protocol: report actual dates and remaining duration as of the data date, then use formal change control for any committed milestone move. That preserves a logic-driven forecast and keeps the baseline as the control reference.
This tests schedule strategy communication tied to model quality. The scheduler should tell team members how to provide status without damaging the schedule model: enter actual start/finish information and remaining duration as of July 12, let the existing finish-to-start logic and calendar calculate the forecast, and submit any requested change to the August 31 commitment through formal change control. Because the milestone has zero float, hiding slippage with typed finish dates or Must Finish On constraints would make the report look cleaner but reduce traceability, distort float, and weaken forecast credibility. Replacing the baseline with the forecast is also wrong because the baseline must remain the approved reference for variance measurement. The closest trap is allowing constraints with comments; comments do not fix broken logic transparency.
It enforces status-by-data-date reporting while keeping forecasts logic-driven and commitment changes under approved control.
Topic: Schedule Planning and Development
A data center project has a contractual energization milestone on August 15. The schedule management plan says an external milestone may be reported as achievable only when schedule risk analysis shows at least 80% confidence of meeting it. After a supplier delay, the latest results are:
| Measure | Date |
|---|---|
| Contract milestone | August 15 |
| Deterministic forecast | August 15 |
P50 date | August 14 |
P80 date | August 26 |
What should the scheduler recommend?
Best answer: D
Explanation: The stated tolerance requires at least 80% confidence, so the milestone must be checked against the P80 date, not the deterministic forecast. Because P80 is August 26, the August 15 commitment is not achievable within tolerance and should trigger recovery analysis and, if needed, formal change control.
This question tests whether a milestone is achievable within a defined schedule risk tolerance. When the rule says an external commitment needs 80% confidence, the scheduler should compare the required date to the P80 result from schedule risk analysis. Here, the deterministic forecast happens to equal August 15, but that does not satisfy the stated tolerance. The risk-adjusted date that meets the confidence requirement is August 26, so the contractual milestone is outside tolerance.
The right control decision is to:
A deterministic date that looks acceptable is not enough when the agreed decision rule is probabilistic confidence.
The 80% confidence rule makes the P80 date the test of achievability, and P80 is later than August 15.
Topic: Stakeholder Communications Management
During the weekly update for a hospital equipment installation project, the scheduler validates the status data and confirms that a late vendor delivery will move the contractual handover milestone 7 working days beyond its baseline date. The schedule management plan sets a 3-day tolerance on contractual milestones and requires escalation to the sponsor and contract manager within 24 hours; only they may approve customer-facing commitments or recovery spending above $25,000. What should the scheduler do next?
Best answer: A
Explanation: Because the contractual milestone breach was already validated and exceeds the stated tolerance, the next step is formal escalation, not routine reporting. The scheduler should communicate the forecast impact and response options to the sponsor and contract manager, who have the authority for external commitments and major recovery decisions.
When a verified schedule issue exceeds a defined tolerance on a contractual milestone, it is no longer just routine status information. It must be escalated through the approved communication path to the stakeholders with authority to decide on commitments, corrective action, or contract-facing communication. In this case, the sponsor and contract manager are the named decision-makers, so the scheduler should provide the confirmed forecast impact and feasible response options to them promptly.
The closest trap is treating the delay as a normal status item, but a tolerance breach on a contractual milestone requires escalation now.
It follows the required escalation path after a validated contractual milestone variance exceeded tolerance.
Topic: Schedule Strategy
A PMO is tailoring minimum schedule requirements for four upcoming projects. It wants to make a resource-loaded schedule, explicit resource calendars, and weekly capacity reviews mandatory on only one project. Which project most strongly justifies that requirement?
Best answer: C
Explanation: Shared scarce resources are the strongest reason to require resource loading, resource calendars, and routine capacity review. Those requirements verify that planned dates are executable with available people, not just logically sequenced.
Schedule requirements should be tailored to the characteristic that most threatens schedule realism. When a specialist crew is shared and can support only one site at a time, the schedule needs explicit resource assignments, accurate resource calendars, and regular capacity checks. Otherwise, the network logic may look valid while the dates are still impossible to achieve with actual availability.
Contract commitments usually drive milestone control and commitment reporting requirements. Geographic dispersion usually drives calendar, handoff, and time-zone rules. Technical complexity usually drives stronger dependency definition and interface milestones. The best choice is the project where resource scarcity is the dominant driver, because the requested requirement is specifically about resource feasibility.
Severe shared-resource limits make resource loading, calendars, and capacity reviews essential for a credible schedule.
Topic: Schedule Monitoring and Controlling
On a refinery upgrade, mechanical completion is a contractual milestone due September 30. The baseline schedule includes a 10-working-day contingency buffer before that milestone. As of August 15, a supplier delay on a critical-path installation activity is forecast to consume 6 days, and two open risks on the same path still carry 5 more days of potential impact. The schedule management plan requires change control if the commitment cannot be met within approved reserve. What is the BEST scheduling action?
Best answer: D
Explanation: Reserve analysis is used to test whether approved schedule contingency still protects the committed date. Here, the current and remaining critical-path exposure exceeds the available reserve, so the scheduler should escalate through change control and evaluate recovery options rather than quietly absorb the variance.
Reserve analysis supports schedule risk and control decisions by comparing remaining approved contingency with the total exposure still threatening the driving milestone. In this scenario, the milestone has 10 working days of reserve, but the path already shows 6 days of forecast delay plus 5 more days of open risk exposure. That means the reserve is no longer sufficient to protect the contractual commitment.
A sound control response is to:
This preserves baseline discipline and gives stakeholders an accurate view of whether the approved reserve can still absorb schedule risk.
Reserve analysis shows the likely 11-day exposure exceeds the 10-day approved buffer, so formal schedule control action is needed.
Topic: Schedule Monitoring and Controlling
On a data-center upgrade, a key equipment supplier missed an interim milestone, triggering a known delivery risk. The current forecast shows final cutover 9 working days late, and the project manager wants to add expediting and temporary test-bench activities to the schedule baseline immediately. What should the scheduler require before baselining that mitigation work?
Best answer: C
Explanation: Before adding mitigation work to the baseline, the scheduler needs evidence that the triggered risk threatens a driving path and that the proposed response materially improves the forecast. Only then should the schedule baseline or PMB be updated through formal change control.
Adding mitigation work to the baseline is a control decision, not just a schedule edit. The scheduler first needs schedule risk assessment evidence showing that the supplier risk affects the project finish or another driving milestone, and that the proposed expediting and test-bench work has a quantified, credible benefit. That means understanding the likely date impact without the response and the expected forecast improvement with it.
A recovery idea may be reasonable, but without quantified evidence and approval it should not replace the approved baseline.
Mitigation should enter the baseline only after analysis shows it credibly improves the driving forecast and the change is formally approved.
Topic: Schedule Monitoring and Controlling
On the June 30 status date, a data-center migration milestone is forecast 10 days late after a supplier delay triggered a known schedule risk. The scheduler finds that activity names in the schedule do not match the resource plan, cost accounts, or risk register, so the team cannot reliably tell which delayed work is driving, funded, or already covered by the response plan. What is the best control action?
Best answer: B
Explanation: The best action is to organize the schedule data so each activity can be traced to its status, responsible resources, cost accounts, and related risks. That creates a credible reforecast and supports corrective action or change control without hiding variance or acting blindly.
The core issue is data traceability, not immediate compression. When schedule activities are logically organized with common IDs or codes, the scheduler can connect current status to resource assignments, cost accounts, and risk responses. That makes it possible to identify which delayed activities are actually driving the milestone, whether recovery resources or funding exist, and whether a triggered risk response already applies.
This protects schedule model integrity; acting before the data are connected leads to weak recovery decisions and poor reporting.
Common coding links the delayed activities to their status, resources, costs, and risks so the forecast and any control action are based on the true driving work.
Topic: Schedule Monitoring and Controlling
A hospital system upgrade has an approved schedule baseline and a contractual go-live milestone on November 15. Weekly status is collected by work package, finance reports labor by control account, and the risk register tracks mitigation by risk ID, but the schedule activities have inconsistent names and no common coding. The sponsor needs one variance report tomorrow showing which delayed work is driving the milestone and the related resource, cost, and risk impacts. Baseline dates cannot be changed without approved change control. What is the BEST action?
Best answer: C
Explanation: The scheduler needs an integrated data structure, not a cosmetic report. Consistent activity coding lets status, resource, cost, and risk information roll up to the driving milestone while preserving the approved baseline for variance analysis.
Logical data organization means the schedule model uses consistent identifiers and coding so each activity can be traced to its work package, responsible resource group, control account, and relevant risk item. In this scenario, that is the only reliable way to produce the sponsor’s integrated variance report: delayed activities can be statused once, then rolled up to the contractual milestone with linked resource, cost, and risk impacts. Replacing baseline dates would destroy the control reference, and a milestone-only or one-time manual report would not provide repeatable, trustworthy schedule control. The best action is to strengthen the schedule model’s data relationships so reporting reflects real schedule logic and supports ongoing monitoring and communication.
Common activity codes create traceable rollups across schedule, status, resource, cost, and risk data without altering the approved baseline.
Topic: Stakeholder Communications Management
A project’s communication plan says to elevate a schedule matter to the sponsor and customer when an issue has occurred and the current forecast shows a contractual milestone will be missed, or when recovery needs approval beyond the project manager’s authority. Which situation should be elevated now?
A noncritical activity is 4 days late, but it still has 6 days of total float.
A supplier may slip a future delivery, but no delay has occurred and the milestone forecast is unchanged.
A critical-path integration defect has already delayed testing, and the forecast now shows the contractual go-live milestone 5 days late unless scope trade-offs are approved.
A work package owner reports only 50% complete, but the remaining duration was reduced and the forecast finish date is still on baseline.
A. Late noncritical activity with remaining float
B. Possible future supplier delay with no forecast impact yet
C. Lower percent complete but forecast still on baseline
D. Occurred critical-path delay pushing a contractual milestone late
Best answer: D
Explanation: The item should be escalated when it is no longer just status noise or an untriggered risk. Here, an actual critical-path delay has already occurred, the forecast misses a contractual milestone, and recovery requires stakeholder approval.
Escalation should be driven by schedule impact and governance thresholds, not by any variance report by itself. The communication plan in the stem sets two triggers: an issue has already occurred and the forecast misses a contractual milestone, or recovery needs approval beyond the project manager’s authority. The integration defect scenario meets both conditions: it is an active issue, it affects the critical path, the forecast slips the contractual go-live date, and recovery depends on approved scope trade-offs.
The other situations stay within normal schedule control. A late noncritical activity with enough float does not yet threaten a key date. A possible supplier slip is still a risk because no delay has occurred and the forecast is unchanged. Lower reported percent complete is only status data if the forecast finish remains on baseline. The key takeaway is to elevate confirmed schedule impact that crosses agreed stakeholder thresholds, not every update.
This is an actual schedule issue with forecasted contractual slippage and recovery needing approval beyond normal authority, so it meets the escalation rule.
Topic: Stakeholder Communications Management
At the data date, the scheduler has already validated status, logic, and remaining durations. The forecast now shows the critical-path cutover milestone finishing five days late. The sponsor wants a recovery plan, but only the operations director can approve the weekend outage window and production acceptance. What should the scheduler do next?
Best answer: A
Explanation: The forecast is already credible, so the next step is not more validation, reporting alone, or rebaselining. Because the operations director controls the outage window and production acceptance, the scheduler should confirm that stakeholder’s recovery constraints before choosing a compression action.
The key concept is stakeholder influence on schedule recovery and acceptance. In this case, the delay has already been validated, so the issue is no longer status quality; it is whether any recovery option will be acceptable and executable. Because the operations director is the approval authority for the weekend outage window and production acceptance, that stakeholder’s expectations and constraints directly affect which recovery scenarios are viable. The scheduler should engage that decision-maker before selecting fast tracking, crashing, or another corrective action. Sending reports improves visibility, but visibility alone does not resolve the recovery decision. Rebaselining is also inappropriate until an approved change justifies replacing the control reference. The best next step is to involve the stakeholder who can actually accept or reject the recovery window.
That stakeholder controls both the recovery window and schedule acceptance, so their constraints must be confirmed before selecting a recovery action.
Topic: Schedule Monitoring and Controlling
On a predictive project, the monthly update shows the completion forecast is 12 working days later than the approved baseline. Internal audit asks the scheduler to show when the slip first appeared, which approved changes affected it, and which file version supported each month’s analysis. Schedule files have been saved in different folders with inconsistent names, and some prior versions were overwritten. What is the best corrective action?
Best answer: C
Explanation: The key problem is not only the late forecast but the missing audit trail behind it. Standard electronic storage and retrieval rules preserve prior schedule versions, status dates, and approved-change references so ongoing audit analysis can verify when variance emerged and why.
Electronic file storage and retrieval standards support schedule control by preserving traceable evidence across updates. In this scenario, the team cannot reliably analyze the delay trend because prior schedule versions were overwritten and scattered across folders. The strongest corrective action is to enforce a controlled repository that retains each update, uses consistent names tied to the status date, and links schedule files to approved changes.
That improves audit readiness and schedule analysis without changing the baseline or forcing dates.
This creates a reliable audit trail so analysts can reconstruct prior forecasts and trace approved changes over time.
Topic: Schedule Planning and Development
On a plant-upgrade project, the startup milestone is forecast 12 working days late. The entire driving path before startup is a single 30-day summary task labeled Commissioning, and the electrical SME and vendor say calibration, regulator witness testing, and punch-list closeout were never defined separately; operator training has 8 days total float. The schedule management plan requires external approvals and handoffs to be modeled as distinct milestones. What is the best corrective action?
Commissioning remaining duration to recover 12 days.Commissioning with SMEs, add approval milestones, relink, then reforecast.Best answer: C
Explanation: The main issue is poor activity and milestone definition on the driving path, not yet a validated need for compression or rebaselining. The best action is to decompose the work with SME input, add the required milestones, and then produce a credible forecast from the corrected schedule model.
A recovery decision is only credible if the schedule model reflects the real work. Here, Commissioning is still a lumped summary task on the driving path, while SMEs already know it contains separate steps such as calibration, witness testing, and punch-list closeout. Because scheduling policy requires external approvals and handoffs to appear as distinct milestones, the first control action is to decompose that work, define the missing activities and milestones, and update the logic and durations with SME input. Then the scheduler should reforecast from the corrected model and decide whether further recovery or formal change control is needed. Shortening durations by decree, compressing non-driving work, or replacing the baseline with the forecast weakens schedule control instead of improving it.
This corrects the schedule model by defining missing activities and milestones with SME input before any recovery or change-control decision is made.
Topic: Schedule Planning and Development
A project in a program must deliver an interface package to another project by July 15, as committed in the integrated master plan. After the latest status update, the project forecast moves that handoff to July 29 because a supplier approval activity on the driving path slipped by 10 working days. The baseline has not changed, and no recovery action has been approved. What is the best alignment action?
Best answer: B
Explanation: When a project date no longer matches an integrated master plan commitment, the scheduler should keep the baseline unchanged, update the forecast, and evaluate the impact on dependent work. Then the variance should go through the program’s change-control or governance path so any recovery, resequencing, or rebaseline decision is approved.
The key concept is alignment between the project schedule and the program-level commitment without damaging schedule control. Here, the slip is on the driving path and affects an interface milestone that another project depends on, so the first step is to reflect the new forecast honestly and analyze the cross-project impact. Because the baseline is still the approved reference, it should remain in place until an authorized decision changes it.
A sound response is to:
The closest trap is trying to make reports look aligned by changing baseline dates before approval.
This preserves baseline integrity while aligning the new forecast and its cross-project impact through the proper program decision path.
Topic: Schedule Monitoring and Controlling
At the status date, a critical-path vendor delivery is forecast 10 workdays late. The delay exceeded a risk trigger, so the team activated a preapproved mitigation: add a prefabrication crew and resequence two successor activities. After updating logic and resources in the schedule model, project completion is now forecast 3 workdays late. No change request to move the contractual finish milestone has been approved. What should the scheduler do?
Best answer: D
Explanation: The mitigation should be reflected in the schedule model and forecast because it changes the expected finish date. The baseline should remain unchanged until formal change control approves a new contractual milestone, so the remaining 3-day variance must still be visible.
When a triggered mitigation is already authorized, the scheduler should incorporate it into the schedule model and publish the resulting forecast. That forecast reflects the current logic, resources, and expected dates after the recovery action. It does not automatically replace the schedule baseline or performance measurement baseline. The baseline remains the approved reference for measuring variance until a formal change request authorizes a revised milestone. Here, the mitigation improves the forecast from 10 workdays late to 3 workdays late, so the project should report that smaller but still real variance and route any needed milestone move through change control. Rebaselining early, forcing dates, or acting on non-driving work weakens schedule control rather than improving it.
Mitigation changes the current forecast, but the baseline stays as the approved control reference until a milestone change is formally approved.
Topic: Schedule Monitoring and Controlling
On a predictive project, the status date is September 9, 2026, and all activities use a 5-day workweek calendar. The contract milestone Ready for Inspection has a Finish No Later Than September 30, 2026 constraint.
Driving path:
Install Piping (4d remaining) -> Pressure Test (3d)
-> Punch-list Fixes (2d)
-> Schedule Reserve (2d remaining of 5d)
-> Ready for Inspection
Near-critical path:
Vendor Documents -> Training, 8d total float
The current forecast milestone date is September 29, but residual testing risk is estimated at up to 4 more working days. What should the scheduler do next?
Best answer: A
Explanation: Reserve analysis is used to compare remaining schedule contingency with current residual risk. Here, only 2 reserve days remain against up to 4 days of exposure, so the scheduler should keep the reserve visible in the model and use that shortfall to support recovery or formal control action.
The key concept is that reserve analysis supports schedule control by showing whether the remaining contingency is still adequate for the unresolved risk. In this schedule, the milestone still forecasts one day before the contractual date, but that forecast depends on only 2 remaining reserve days while the residual testing risk could consume 4 days. That means the schedule has a 2-day exposure even though the current forecast still appears acceptable.
The closest trap is relying on the current forecast date alone; reserve analysis is valuable precisely because it reveals weak schedule protection before the milestone is actually missed.
Reserve analysis compares remaining schedule contingency with residual risk, and the explicit reserve activity shows a 2-day shortfall without distorting logic.
Topic: Schedule Planning and Development
A scheduler is building the baseline for a software cutover on a Monday-Friday calendar. Configure interface and Validate data mapping are parallel 5-day activities, both finish-to-start from Design approved and both finish-to-start into the Cutover ready milestone. Each activity requires 1 integration architect and currently has zero total float. The architect’s approved calendar shows only 4 hours per day available that week because of production support, and there are no date constraints. Which action best preserves schedule model integrity?
Best answer: B
Explanation: The schedule should show the resource’s real availability and each activity’s actual resource requirement before trying to protect dates. That reveals the true capacity problem, and leveling is the appropriate allocation technique to resolve it in the model.
Resource requirements are the resources each activity needs; here, each parallel activity needs 1 integration architect for 5 days. Resource availability comes from the approved resource calendar; here, that architect is only 50% available during the week. Capacity requirements are the combined demand over that period, and the overlapping activities create demand that exceeds available capacity.
The best modeling action is to keep the activity requirements explicit, apply the architect’s actual availability calendar, and then use resource leveling to resolve the conflict. That may push dates, but it preserves schedule logic, traceability, and forecast credibility. By contrast, forcing dates with constraints, hiding the specific resource, or insisting dates stay fixed makes the schedule look cleaner while masking an invalid resource-loaded plan.
This keeps activity demand separate from actual availability, exposes the true capacity shortfall, and uses a valid allocation technique to produce a credible forecast.
Topic: Schedule Monitoring and Controlling
On the June 14 data date, activity Install Sensors shows a baseline finish of June 12 and no actual dates. The field lead says, “We started June 10, we are 60% complete, and we should finish June 18.” What is the best next step for the scheduler?
Best answer: C
Explanation: The update contains both actual status and forecast information. The scheduler should first capture validated actual progress data—especially the actual start and remaining work—then let the schedule model calculate the forecast finish. That keeps actuals, forecast, and baseline dates distinct.
In schedule monitoring and controlling, actual progress data are facts as of the data date, such as actual start, actual finish, and credible remaining duration or physical progress. A finish like June 18 is a forecast, not an actual date, and the June 12 baseline finish remains the approved reference for variance measurement.
Here, the best next step is to validate and enter the actual start of June 10 and confirm the remaining work before recalculating the schedule. That allows the model logic to produce a credible forecast finish. Reporting the forecast before validation, leaving planned dates in place as if they were status, or changing the baseline would all reduce schedule-control quality.
The key takeaway is to collect and verify actual status first, then derive the forecast and compare it to the baseline.
June 10 is actual progress data, while June 18 is only a forecast until validated through remaining work and schedule logic.
Topic: Schedule Monitoring and Controlling
On the April 15 status date, critical path analysis shows a critical activity finished 5 working days late. The project completion milestone has a baseline date of June 30 and now recalculates to a forecast date of July 7. No scope change or change request has been approved. What is the most appropriate schedule update?
Best answer: A
Explanation: A routine status update should reflect current reality, so the forecast can move when critical-path work finishes late. The baseline remains the approved control reference and should stay at June 30 unless formal change control approves a rebaseline.
In schedule monitoring and controlling, a status update changes the live schedule model by entering actual dates and remaining work, which recalculates forecast dates. The baseline is different: it is the approved reference used to measure variance. Here, critical path analysis shows a real slip from the June 30 baseline milestone to a July 7 forecast milestone, and no change has been approved. The correct action is to show the new forecast while preserving the original baseline so the variance remains visible for reporting, recovery planning, and auditability. Changing the baseline now would hide performance variance, while forcing the old date would misstate the forecast.
Status updates should change the forecast based on current critical-path performance, while baseline dates stay fixed until approved change control authorizes rebaselining.
Use this flow when a question asks how to build, validate, or recover a schedule. PMI-SP scenarios usually reward logic quality, baseline discipline, forecast realism, and transparent control decisions.
flowchart LR
A["Scope and deliverables"] --> B["Activities and dependencies"]
B --> C["Durations, resources, and constraints"]
C --> D["Schedule quality review"]
D --> E["Approved baseline"]
E --> F["Progress update and critical path"]
F --> G["Forecast, variance, and recovery action"]
| Concept | Exam-facing use |
|---|---|
| Logic network | Dependencies must reflect real work relationships for the schedule to forecast correctly. |
| Critical path | Current longest path through the schedule; delays here usually affect completion. |
| Float | Time an activity can slip before affecting the project finish or constrained milestone. |
| Baseline | The approved reference for schedule variance; do not move it informally. |
| Recovery action | Evaluate schedule, cost, risk, quality, contract, and resource effects before choosing. |
| Schedule quality | Check open ends, hard constraints, unrealistic durations, missing owners, and weak calendars. |
Use this live PMI-SP page for web and app access, public sample questions, timed mocks, topic drills, plans, and related PM Mastery exam links.
If you want concept-first reading before heavier simulator work, use the companion guide at PMExams.com .
Use the live PM Mastery route above if PMI-SP is the exam you actually need.