Try 10 focused PMI-SP questions on Schedule Closeout, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PMI-SP |
| Topic area | Schedule Closeout |
| Blueprint weight | 6% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Schedule Closeout for PMI-SP. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 6% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Schedule Closeout
At project closeout, a system rollout that used rolling-wave planning finished on November 6. The approved schedule baseline finish was October 30, the last forecast before completion was November 8, and no rebaseline was approved. Which conclusion best belongs in the final schedule performance evaluation?
Best answer: C
What this tests: Schedule Closeout
Explanation: Final schedule performance at closeout is evaluated against the approved schedule baseline, not the last forecast. Here, the project finished 7 days late to baseline, while the November 8 forecast simply shows the planning approach produced a forecast that was 2 days later than actual.
In schedule closeout, the primary performance comparison is actual results versus the approved schedule baseline because the baseline is the formal control reference. In this scenario, an actual finish of November 6 against a baseline finish of October 30 means the project completed 7 calendar days late.
The scheduling approach should still be evaluated, but separately. The final forecast of November 8 shows that rolling-wave planning produced a reasonably close forecast, finishing 2 days earlier than expected. That is useful evidence about forecast quality and approach effectiveness, but it does not change the final schedule variance. Because no rebaseline was approved, the baseline remains the correct reference for final performance reporting.
Beating the last forecast is helpful context, not the main closeout performance result.
Closeout performance is measured against the approved baseline, while forecast accuracy and the scheduling approach are evaluated separately.
Topic: Schedule Closeout
During schedule closeout for a facilities project, the scheduler is updating organizational process assets for future projects. Midway through the project, forecast accuracy improved only after the team stopped reporting percent complete alone and began submitting remaining duration with logic validation at each status date. Which information should be retained as process-improvement information for future scheduling work?
Best answer: B
What this tests: Schedule Closeout
Explanation: Process-improvement information for future scheduling work should capture a reusable lesson about how scheduling was performed better. In this case, the valuable closeout update is the practice change that improved forecast credibility, not a project-specific date, baseline, or status report.
In Schedule Closeout, organizational process asset updates should preserve lessons that can improve how future schedules are developed, updated, or controlled. The key distinction here is between a project record and a reusable process improvement. A final forecast date, a reapproved baseline, and a status report are important historical artifacts, but they mainly describe this project’s results.
The reusable improvement is the finding that forecast quality improved when the team collected remaining duration and validated logic at each status date instead of relying on percent complete alone. That helps future projects improve status methods, forecast credibility, and schedule-model integrity.
The closest distractors are useful archives, but they do not directly tell future teams how to schedule better.
This captures a reusable scheduling practice improvement, not just a project-specific schedule record.
Topic: Schedule Closeout
A healthcare system rollout had one schedule rebaseline approved through change control after new regulatory testing was added. At closeout, the project actually finished on November 12, 2025. The original baseline finish was October 20, 2025, the approved revised baseline finish was November 5, 2025, and the final forecast before completion was November 12, 2025. For the final schedule performance evaluation, which comparison should the scheduler use?
Best answer: C
What this tests: Schedule Closeout
Explanation: At closeout, final schedule variance is assessed by comparing actual results with the approved schedule baseline that governed the work after authorized changes. A forecast is only a prediction, and the original baseline is no longer the formal performance reference once a rebaseline is approved.
The key distinction is baseline versus forecast. Final schedule performance evaluation uses actual dates against the current approved schedule baseline, because that baseline is the control reference after formal change approval. In this scenario, the correct closeout comparison is the actual finish of November 12, 2025, against the approved revised baseline finish of November 5, 2025, showing the project finished 7 days late against the approved baseline.
The final forecast is useful for judging how accurate the team’s prediction was, but it does not measure schedule variance. The original baseline may still help with lessons learned and change-impact analysis, but once the schedule was officially rebaselined, it is no longer the primary reference for final performance reporting.
At closeout, measure execution performance against the approved baseline, not against what the team last expected to happen.
Final schedule performance at closeout is measured against the approved baseline in effect, not against a forecast or a superseded baseline.
Topic: Schedule Closeout
At closeout of a plant expansion project, the contract requires a schedule archive that is “forensically ready” and compliant with the schedule management plan. The final accepted update has a data date of October 31, 2026, uses both a Monday-Friday project calendar and a Saturday vendor calendar, includes finish-to-start links from vendor delivery to installation, and has two approved finish-no-later-than regulatory milestones.
Archive procedure:
- Keep native schedule files for the original baseline, any approved rebaseline, and the final accepted update
- Preserve calendars, logic, constraints, actual dates, remaining durations, and resource settings
- Include approved schedule change records and update history
Which action best satisfies the contractual requirement?
Best answer: B
What this tests: Schedule Closeout
Explanation: The archive must preserve the native schedule model and its history, not just a readable summary. Keeping data dates, calendars, dependencies, constraints, actuals, resources, and approved changes satisfies the stated procedure and supports contractual traceability.
In schedule closeout, archiving means preserving a complete, auditable record of how the schedule was built, updated, and approved. Because the contract and procedure explicitly require native files, update history, calendars, logic, constraints, actual dates, remaining durations, resource settings, and approved change records, the best action is to archive those items intact. That preserves model integrity for any later claim review, delay analysis, or contract audit.
Deleting completed activities, collapsing the file into summaries, replacing dependencies with constraints, or overwriting baseline dates may make the schedule look cleaner, but those actions destroy traceability. They can prevent reviewers from reconstructing the driving path, checking approved changes, or validating status as of the final data date.
At closeout, readability is secondary to preserving an unchanged, defensible schedule record.
This preserves the full schedule model and audit trail exactly as required for contractual compliance and later forensic analysis.
Topic: Schedule Closeout
During closeout of a facility automation project, the team reviews a past forecasting problem.
Exhibit:
Status date: June 10
Calendar: Monday-Friday
Activity: System test
Constraint in update: Mandatory Finish June 28
True driver later confirmed: FS from vendor approval milestone
Actual finish: July 2
After correction: forecast matched the driving path
Which closeout entry is most appropriate as a schedule lesson learned, rather than a final status report item or an unresolved issue?
Best answer: B
What this tests: Schedule Closeout
Explanation: The correct choice turns the experience into reusable scheduling guidance: represent external approvals with logical dependencies instead of hard constraints. That is a lesson learned because it improves future schedule model integrity and forecast credibility, not just this project’s record of results or open follow-up.
A schedule lesson learned captures a reusable insight from the project’s scheduling experience. Here, the key insight is that the vendor approval should have been modeled as a predecessor milestone with finish-to-start logic on the Monday-Friday calendar, not hidden behind a mandatory finish constraint on system testing. Using the real dependency preserves traceability to the driving path and produces a more credible forecast.
By contrast:
Closeout may archive all of these artifacts, but only the process-improvement insight belongs in lessons learned.
This is reusable process-improvement guidance that strengthens schedule logic, traceability, and forecast credibility.
Topic: Schedule Closeout
During schedule closeout of a 14-month facility project, the team reviews this evidence:
SPI for months 6-12: average 1.03 (appeared ahead of plan)
Final commissioning milestone: 15 workdays late
Milestone trend: slipped in 4 consecutive updates
Status practice: percent complete often changed,
remaining duration rarely changed
Which lessons-learned entry is most useful to retain in organizational process assets for future scheduling work?
Best answer: C
What this tests: Schedule Closeout
Explanation: The best retained information is a process improvement, not just a historical result. Here, SPI looked favorable, but milestone trend slippage and unchanged remaining duration showed that forecast quality was weak, so future updates should explicitly validate both.
In schedule closeout, process-improvement information should tell future teams what to do differently. The evidence shows that SPI averaged above 1.0, yet the final commissioning milestone still finished late. That means an aggregate performance indicator did not provide a reliable finish forecast for this project. The more useful lesson is that update cycles should include milestone trend analysis and a disciplined review of remaining duration, especially when key milestones keep moving.
Archiving the final SPI and lateness is useful historical data, but it does not improve future scheduling practice by itself. Likewise, adding a blanket buffer treats the symptom rather than the root cause, and relying mainly on SPI repeats the same forecasting weakness. The strongest closeout lesson is the one that improves future schedule analysis and status quality.
It captures the reusable scheduling improvement: SPI alone masked the problem, while milestone trends and stale remaining-duration data revealed weak forecasting.
Topic: Schedule Closeout
A construction project has reached final acceptance. The approved schedule baseline completion date was October 15, but the actual completion date was October 27, and the scheduler has final EVM results and variance analysis ready for the customer and governance board. The sponsor asks the scheduler to change the baseline to October 27 before issuing the closeout package so the project appears on time. What should the scheduler do?
Best answer: A
What this tests: Schedule Closeout
Explanation: At closeout, performance must be reported against the approved schedule baseline, not rewritten to match the actual finish. Stakeholders need the final schedule report, EVM results, and variance analysis to understand true performance and complete closeout properly.
The core concept is baseline integrity during closeout. Once the schedule baseline has been formally approved, it remains the reference for measuring final performance unless a new baseline is approved through change control. An actual finish date does not become the baseline just because the variance is unfavorable.
For closeout, the scheduler should distribute the final schedule report to stakeholders using the approved baseline, actual completion date, final EVM results, variance analysis, and the history of approved changes. That gives the customer and governance board a truthful record for acceptance, lessons learned, and archives. Compressing remaining administrative work or omitting the analysis does not fix the already measured completion variance.
The key takeaway is to report final schedule performance transparently, not to hide it.
The approved baseline remains the control reference, so closeout reporting should transparently show final performance and variance.
Topic: Schedule Closeout
During closeout of a hospital commissioning project, turnover finished 12 working days late. At the October 31, 2025 status date, the archived schedule used a Monday-Friday calendar, linked training to testing with SS+15d, and applied a Must Finish On constraint to the turnover milestone. The scheduler now needs stakeholder feedback to identify schedule lessons learned and best practices. What should the scheduler do?
Best answer: A
What this tests: Schedule Closeout
Explanation: Closeout lessons learned should come from structured stakeholder review of the final schedule model, not from a cleaned-up summary or altered record. Reviewing actual logic, constraints, lags, and calendars helps identify which modeling practices supported or weakened forecast credibility.
In final schedule performance evaluation, the goal is to capture reusable lessons from how the project was actually planned, updated, and delivered. Because the delay may have been influenced by the SS+15d lag, the Must Finish On milestone constraint, and the calendar setup, stakeholder feedback should be gathered through a focused review of those specific model elements against actual execution results. That approach preserves traceability between the approved baseline, status history, and final outcomes while producing concrete best practices for future schedules.
A milestone-only summary, a rewritten baseline, or a vague opinion survey may look cleaner, but each removes evidence or detail needed to understand model quality. The key takeaway is to solicit evidence-based stakeholder feedback without changing the historical schedule record.
This uses stakeholder feedback to evaluate the actual schedule model choices that affected performance while preserving traceable closeout evidence.
Topic: Schedule Closeout
At closeout of a facilities upgrade, the scheduler reviews the model used through the final status date of October 31, 2025.
Calendar: Monday-Friday
Dependency used: Installation complete -> Commissioning (10-day lag)
Constraint used: Mandatory finish on Contract Handover milestone
Reality found: Commissioning could start only after utility inspection on a separate calendar
Which lesson learned should be retained for future scheduling work?
Best answer: C
What this tests: Schedule Closeout
Explanation: The reusable improvement is to model third-party inspection work explicitly instead of hiding it in lags or constraints. That strengthens schedule logic, preserves traceability, and produces more credible forecasts in future projects.
Lessons learned for schedule closeout should capture practices that improve future schedule model quality. Here, the real driver was a utility inspection on a different calendar, but the model used a 10-day lag and a mandatory finish constraint instead. A better process for future schedules is to add the inspection as its own activity, apply the correct calendar, and link it logically to commissioning and handover. That allows status, float, and driving-path analysis to reflect reality and makes forecast dates more trustworthy. Longer lags and hard constraints may make the file look cleaner, but they hide accountable work and weaken analysis. Preserving baseline history is also essential, so archived schedules should not overwrite baseline dates with final dates. The key takeaway is to model real driving work explicitly.
Explicit activities preserve traceable logic, support correct calendar behavior, and show the true driving path.
Topic: Schedule Closeout
During final schedule review on a facilities project, the owner will accept schedule closeout only when contractual completion dates are achieved or any date impacts are formally resolved. Which situation should prevent schedule closeout acceptance?
Best answer: A
What this tests: Schedule Closeout
Explanation: Schedule closeout acceptance requires the final contractual schedule position to be settled, not just reported. A late contractual milestone with an unresolved time-extension request is an actual schedule issue that must be formally dispositioned before acceptance.
In schedule closeout, the key test is whether contractual schedule components are complete and any actual date impacts have been formally resolved. A late substantial-completion milestone is not a future risk or a simple status variance; it is a current schedule issue because the delay has already occurred. If the related time-extension request is still pending, the project does not yet have a finalized contractual schedule outcome for that milestone. Closeout acceptance should wait until the delay is resolved through the required approval, denial, or settlement process. By contrast, an approved revised milestone, a possible future delay outside contractual completion, or lateness on noncritical work that does not affect contractual milestones does not by itself block closeout acceptance.
A missed contractual milestone with a still-pending time-extension decision is an open schedule issue, so the contractual impact is not resolved for closeout.
Use the PMI-SP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PMI-SP guide on PMExams.com, then return to PM Mastery for timed practice.