PMI-SP · Domain 4 of 5

PMI-SP Domain 4: Schedule Closeout

Schedule Closeout is the smallest PMI-SP domain, but it decides whether the project's schedule record is accepted, explained, reusable and retrievable after the team disbands.

Exam weight
6%
Official tasks
5
Estimated questions estimate
~10
Suggested study time estimate
5–10 hrs

About 12 min read Reviewed October 2026

Overview

Schedule Closeout covers five tasks at the end of a project or phase: obtaining final acceptance of the contractual schedule components from the sponsor or customer, evaluating final schedule performance against the baseline and the chosen scheduling approach, updating organizational process assets with lessons learned and best practices, distributing final schedule reports with earned value results and variance analysis, and archiving schedule files under defined procedures and contract terms.

Candidates need to know the order of these steps, what an as-built schedule is, how final earned value figures are read, and why lessons learned must be specific enough to change future estimates. The domain closes the loop on Domain 1's archiving and configuration rules and uses the variance history kept in Domain 3.

How it's tested

Questions are short situational items about sequence and completeness: what to do FIRST when work ends, which document belongs in the archive, or what a useful lesson learned looks like. Occasionally a final earned value figure must be interpreted. The reasoning pattern is to secure acceptance, evaluate, capture, report, then archive.

  • Closeout sequence

    Several closeout actions are listed and you pick the one that must happen first, usually acceptance of contractual schedule components.

  • Useful lessons

    You choose the lesson learned or OPA update that is specific, evidence-based and reusable for future estimates.

  • Final numbers

    Final EV, PV, AC or dates are given and you interpret the final variance correctly, including the limits of cost-based SPI at completion.

Reasoning it through

The last deliverable is accepted and the PM wants to release the scheduler immediately. The contract requires an as-built schedule. Reasoning: the contractual schedule component is still outstanding. Produce the as-built schedule and obtain the customer's acceptance before release, then complete the performance evaluation, lessons learned and archive. Releasing staff first risks losing the knowledge needed to explain variances.

Tasks 5

Official tasks from the PMI outline, in outline order.

4.1 Obtain final acceptance of the contractual schedule componentsGet sponsor or customer sign-off on schedule deliverables.
What it means
You confirm that schedule-related contract deliverables, such as the as-built schedule, final schedule narrative or required reports, are complete and formally accepted by the sponsor or customer.
What to understand
Acceptance of the product does not automatically mean acceptance of the schedule deliverables; contracts can list them separately and tie them to payment or claims.
How it shows up
The product is accepted but the as-built schedule is outstanding; the correct next step is to complete and obtain acceptance of it.
Common confusion
Assuming project closure or product acceptance covers every contractual schedule obligation.
4.2 Evaluate final schedule performance against baseline schedule and scheduling approachCompare final results with the baseline and review the approach.
What it means
You compare actual dates and durations with the baseline, explain major variances, and judge how well the chosen methodology, tool and update process worked, gathering stakeholder feedback.
What to understand
The evaluation covers both the numbers and the process: an accurate finish achieved through constant re-baselining indicates a weak approach.
How it shows up
A question asks what the final review should examine; the best answer includes both variance causes and the effectiveness of the scheduling approach.
Common confusion
Limiting evaluation to whether the finish date was met.
4.3 Update the organizational process assetsRecord lessons learned and best practices for future projects.
What it means
You add specific lessons, actual durations, productivity rates, estimating accuracy and template improvements to the organization's historical data and scheduling standards.
What to understand
A useful lesson states the situation, cause, impact and recommendation with data, such as permits averaging 45 days against 30 planned.
How it shows up
Options list several lessons; the right one is specific, measurable and actionable for future estimates.
Common confusion
Treating lessons learned as a closeout meeting only, rather than an update to reusable assets.
4.4 Distribute final schedule reports, including EVM calculations and variance analysisIssue final performance reporting to stakeholders.
What it means
You prepare and distribute final reports showing final earned value metrics, schedule and cost variances, explanations of significant variances and the final dates.
What to understand
At completion EV equals BAC and cost-based SV becomes zero, so final schedule performance is better expressed in time (actual versus baseline finish, or SPI(t)).
How it shows up
A final report shows SPI of 1.0 on a project that finished two months late; you identify why and what measure to report.
Common confusion
Concluding from a final SPI of 1.0 that the project finished on time.
4.5 Archive schedule filesStore final model, plans and reports per procedure and contract.
What it means
You archive the final schedule model, schedule management plan, baselines, periodic updates, reports and change records according to retention procedures and contract requirements.
What to understand
Archives must keep the update history and baselines, not only the final file, so later audits or claims can be supported.
How it shows up
A question asks which items to archive; the best answer includes baselines and periodic updates as well as the final schedule.
Common confusion
Archiving only the final schedule and deleting intermediate versions to save space.

High-yield concepts

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

  • As-built schedule

    The final schedule showing actual start and finish dates of every activity, recording how the project was really executed.

    Remember
    It is often a contractual deliverable and is the core input for forensic analysis.
    Tested as
    Appears in acceptance and archiving questions.
    Trap
    Archiving the baseline schedule as if it showed what happened.

  • Final variance at completion

    The difference between the baseline and the actual finish date and between BAC and final actual cost.

    Remember
    Report schedule variance at completion in time units, because cost-based SV is zero when EV reaches BAC.
    Tested as
    Final report questions test this distinction.
    Trap
    Reporting a cost-based SV of zero as schedule success.

  • SPI convergence

    Cost-based SPI = EV / PV moves to 1.0 at completion because EV eventually equals BAC and PV has already reached BAC.

    Remember
    Use SPI(t) or actual versus baseline dates for final schedule performance.
    Tested as
    A classic interpretation item at closeout.
    Trap
    Believing a late project became efficient at the end.

  • Lessons learned register

    A record of what happened, why, the effect, and what to repeat or change, updated throughout and finalized at closeout.

    Remember
    Capture lessons during the project; closeout consolidates them.
    Tested as
    OPA update questions focus on quality and timing of lessons.
    Trap
    Waiting until the end, when people and details have gone.

  • Organizational process assets update

    Adding actual durations, productivity rates, templates, calendars and estimating accuracy data to organizational repositories.

    Remember
    The goal is better future estimates and schedules, not just documentation.
    Tested as
    Task 4.3 is tested through choosing the most useful update.
    Trap
    Selecting a generic statement such as 'communication could be better'.

  • Retention requirements

    Contractual, regulatory and organizational rules for how long and in what form project records are kept.

    Remember
    The archive must satisfy the strictest applicable requirement.
    Tested as
    Archiving questions refer to contract or policy terms.
    Trap
    Applying the organization's default retention when the contract specifies longer.

  • Phase closeout

    Closing a phase with the same acceptance, evaluation and archiving steps before handing over to the next phase or operations.

    Remember
    The ECO's closeout knowledge includes transition planning to the next phase or operations.
    Tested as
    Scenarios may involve a phase end rather than project end.
    Trap
    Assuming closeout tasks apply only at the end of the whole project.

  • Schedule narrative

    A written explanation accompanying the final schedule that describes the critical path history, major delays, causes and recoveries.

    Remember
    Numbers without narrative do not explain variances to future readers or auditors.
    Tested as
    Supports final reports and archives.
    Trap
    Distributing final metrics with no variance explanations.

Side by side

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

Baseline schedule vs. final updated schedule vs. as-built schedule

ConceptMeaningKey differenceCommon trap
Baseline schedule Approved plan used to measure performance Shows intended dates Treating it as the record of execution
Final updated schedule Last status update before completion May still contain forecasts for unfinished work Archiving it as the final record before all actuals are entered
As-built schedule All activities with actual dates Shows what actually happened Omitting it when the contract requires it

Cost-based SPI vs. time-based schedule measures at completion

ConceptMeaningKey differenceCommon trap
Cost-based SPI EV / PV Equals 1.0 at completion regardless of lateness Using it to judge final schedule success
SPI(t) Earned schedule / actual time Reflects lateness at completion Not knowing it exists
Finish date variance Actual finish minus baseline finish Direct time measure stakeholders understand Not adjusting for approved baseline changes

Exam traps

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

  1. Archive first

    What candidates pick
    Archive all schedule files as soon as the last activity finishes.
    Why it looks right
    Archiving feels like the defining closeout act.
    Why it's wrong
    If contractual schedule components are not yet accepted, the archived version may not be the accepted record.

    Clue to watch for The stem mentions an outstanding contractual schedule deliverable or pending customer sign-off.

  2. Product acceptance equals schedule acceptance

    What candidates pick
    Close the schedule because the customer accepted the final product.
    Why it looks right
    Acceptance of the product seems to close everything.
    Why it's wrong
    The contract may separately require an as-built schedule or final schedule report, which needs its own acceptance.

    Clue to watch for The contract lists schedule deliverables separately from product deliverables.

  3. Final SPI of 1.0

    What candidates pick
    Report that the project met its schedule because SPI equals 1.0.
    Why it looks right
    1.0 normally means on plan.
    Why it's wrong
    Cost-based SPI always converges to 1.0 at completion; the actual finish date tells the real story.

    Clue to watch for Actual finish date later than baseline finish appears elsewhere in the stem.

  4. Vague lessons

    What candidates pick
    'Better communication with suppliers is needed.'
    Why it looks right
    It is true and sounds constructive.
    Why it's wrong
    It gives future schedulers no data to adjust estimates or logic.

    Clue to watch for Another option includes a measured difference and a specific recommendation.

  5. Save space by pruning

    What candidates pick
    Keep only the final schedule file in the archive.
    Why it looks right
    Intermediate versions seem redundant once the project ends.
    Why it's wrong
    Baselines and periodic updates support audits, claims and forensic analysis, and contracts may require them.

    Clue to watch for The stem mentions possible disputes, audits or retention requirements.

Answer framework

Use this sequence when a closeout question asks which step comes first or what is missing.

  1. Confirm every contractual schedule component, such as the as-built schedule and final reports, is complete and formally accepted by the sponsor or customer.
  2. Enter all final actuals so the as-built record is complete, then compare final dates and costs with the baseline, adjusting for approved changes.
  3. Explain significant variances and evaluate how well the scheduling approach, tool and update process worked, using stakeholder feedback.
  4. Record specific, data-backed lessons learned and update organizational process assets such as historical durations, productivity rates and templates.
  5. Distribute final reports with EVM results and variance analysis, then archive all baselines, updates and records under retention rules.

Practice question

The final deliverable has been handed over and accepted. The contract also lists an as-built schedule and a final variance report as deliverables. The project manager asks the scheduler to archive the files and release the team. What should the scheduler do FIRST?

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

Checklist

0 of 10

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

Study strategy

This domain is small, so aim for efficient mastery rather than long study. Start by memorizing the closeout sequence: accept, evaluate, capture lessons, report, archive. Then rehearse why acceptance of contractual schedule components comes first and why archiving comes last.

Next, spend time on the one calculation idea that trips people here: cost-based SPI converges to 1.0 at completion. Work an example where a project finishes late, show that EV and PV both equal BAC, and compare with the finish date variance and SPI(t).

Commonly underestimated areas are the quality of lessons learned and the archive contents. Practice rewriting vague lessons into measurable ones, and list everything the archive needs, including baselines, periodic updates and change records.

Afterwards, do a short set of closeout scenarios that each ask for a FIRST step or a missing item, and explain why each wrong option is out of sequence, then return to Domain 3, since many closeout answers depend on records kept during control.

FAQ

How much is Schedule Closeout worth on the exam?

PMI weights it at 6%, the smallest domain. Applied to 170 items, that is about 10 questions as a planning estimate.

What is the first closeout step for a scheduler?

Obtain final acceptance of the contractual schedule components, such as the as-built schedule, from the sponsor or customer. Evaluation, lessons learned, reporting and archiving follow.

Why does SPI show 1.0 on a late project at completion?

SPI = EV / PV, and at completion both EV and PV equal the budget at completion. Report schedule performance in time, such as actual versus baseline finish or SPI(t).

What makes a good lesson learned for scheduling?

It states what happened, the cause, the measured impact and a recommendation, for example that permit approvals averaged 45 days against 30 planned and future schedules should plan 45.

What should be archived?

The final and as-built schedules, the schedule management plan, all baselines, periodic updates, reports and change records, kept according to contract and organizational retention rules.

Does closeout apply only at the end of the project?

No. The same steps apply at the end of a phase, together with planning the transition to the next phase or to operations.

Other Project Management certifications

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

Test your Domain 4 knowledge

You have walked through acceptance of schedule deliverables, final performance evaluation, lessons learned, final reporting and archiving. Check whether you can pick the right first step at closeout.

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

Keep going