Domain 4 covers the smallest share of the PMI-SP exam (6%) but governs how a project's schedule knowledge survives after the team disbands: obtaining final acceptance, evaluating performance against baseline, updating organizational process assets, distributing final EVM-based reports, and archiving schedule files for potential forensic review.
Domain 4 is the smallest domain on the PMI-SP exam by weight, but it is not a minor topic in practice. Schedule Closeout is where the scheduler's work either becomes a durable, reusable organizational asset or quietly disappears the moment the project team disbands. A schedule that is never properly closed out cannot support a future claim, cannot inform the next project's estimate, and cannot demonstrate that the contractual schedule obligations were actually met.
Domain Overview and Core Objectives
Per the PMI-SP Examination Content Outline, Domain 4 covers activities related to finalizing all schedule activities, evaluating schedule performance against the original baseline, documenting lessons learned, and distributing final schedule information. It carries five tasks, each with a distinct purpose in the closeout sequence.
Task 1: Obtain Final Acceptance of the Contractual Schedule Components
Task Definition: Obtain final acceptance of the contractual schedule components, by working with sponsor and/or customer, in order to facilitate project closeout.
Most contracts define specific schedule-related deliverables: the final as-built schedule, a completed milestone log, a closed change log, or a formal statement that all contractual dates were met or that variances were disclosed and accepted. Final acceptance means the customer or sponsor has formally agreed that these components are complete and correct — not simply that the physical work is finished.
This task is easy to underestimate because it is administrative rather than technical. In practice, obtaining sign-off can require walking the sponsor through the final schedule, explaining any variances against the baseline, and resolving any lingering disagreement about what the contract actually required before the acceptance can be considered final.
Task 2: Evaluate Final Schedule Performance Against the Baseline
Task Definition: Evaluate final schedule performance against baseline schedule, scheduling approach and the implementation, using standard scheduling tools and techniques, including solicitation of feedback from stakeholders, in order to identify lessons learned and develop best practices.
This is where Domain 4 connects directly back to Domain 3's monitoring and controlling techniques, applied one final time at project completion rather than as an ongoing cycle. The evaluation should cover not just whether the finish date was met, but why the schedule performed the way it did: which estimating assumptions held up, which activities consistently ran long, where the critical path actually moved during execution versus where it was predicted to move at baseline, and whether the chosen scheduling approach (rolling wave, fully detailed up front, hybrid) was appropriate for the work.
Soliciting feedback from stakeholders — not just running the numbers — is explicitly part of this task. A scheduler who only reports the final SPI and CPI without asking discipline leads what actually went wrong misses half of what this task is for.
Task 3: Update the Organizational Process Assets
Task Definition: Update the organizational process assets, through documentation of identified lessons learned and best practices, in order to improve business processes.
Lessons learned that stay in a single project's closeout report help nobody on the next project. This task requires translating what Task 2's evaluation found into something the organization can actually reuse: an updated productivity factor for a type of activity, a revised standard duration for a recurring task, a new standard WBS element that should have existed from the start, or a flagged risk that should be built into future risk registers by default.
Organizations with a mature OPA library treat this as a structured update, not a narrative document nobody reads again. If a lesson learned doesn't change a template, a standard, a productivity factor, or a checklist, it usually hasn't actually been "learned" in an organizational sense — it has just been recorded.
Task 4: Distribute Final Schedule Reports
Task Definition: Distribute final schedule reports, including earned value management (EVM) calculations and variance analysis, to stakeholders, in order to facilitate project closeout.
The final report is not simply the last weekly status report relabeled. It should present the complete performance story: final SPI and CPI, the variance at completion (VAC), a summary of major rebaselining events and why they occurred, and a reconciliation between what was baselined and what was actually delivered.
Practical Example (Shipbuilding Context)
Consider a newbuild project closing out with the following final figures:
- Budget at Completion (BAC) = $42,000,000
- Actual Cost (AC) = $44,100,000
- Earned Value (EV) at completion = BAC = $42,000,000 (all scope delivered)
Since all planned scope was ultimately completed, EV equals BAC at closeout, and CPI = EV / AC = 42,000,000 / 44,100,000 ≈ 0.95. Variance at Completion (VAC) = BAC − AC = 42,000,000 − 44,100,000 = −$2,100,000. The final report should not stop at these numbers — it should explain them: for instance, that the variance traces to a specific rebaselining event following a major equipment delivery delay in month 14, rather than to general inefficiency across the whole project. A final report that presents the index without the explanation gives stakeholders a number but not an understanding.
Task 5: Archive Schedule Files
Task Definition: Archive schedule files (for example, final schedule model, schedule management plan, periodic status reports, schedule change log), as per defined procedures, in order to satisfy contractual requirements and prepare for potential forensic schedule analysis.
This task connects directly to the Schedule Data Management practices covered in Domain 1. The difference is that Domain 1 sets up the configuration management policy at the start of the project; Domain 4 is where that policy is actually executed one final time as the project closes.
A useful archive is not just the final schedule file. It typically includes: the final schedule model, the schedule management plan, periodic status reports and their supporting progress data, the complete schedule change log, and documentation of every rebaselining event with its justification. This matters most when a contractual dispute or claim surfaces after the project team has moved on — sometimes years later, as noted in the Knowledge and Skills area below. An archive that contains only the final schedule, with no intermediate status history, cannot support a retrospective time-impact analysis if a delay claim is raised after the fact.
Knowledge and Skills for Domain 4
Per the PMI-SP Examination Content Outline, this domain draws on:
- Contractual schedule components — knowing exactly what the contract requires as schedule-related deliverables.
- Schedule close-out procedures — the organization's defined steps for finalizing a schedule model.
- Feedback techniques — structured ways to solicit lessons learned from stakeholders rather than relying on the scheduler's own impression.
- Schedule review techniques — the same analytical toolkit used in Domain 3, applied one final time at completion.
- Schedule issue management — tracking open items through to formal closure rather than letting them lapse silently.
- Transition planning — handing off archived schedule data and lessons learned to whoever needs them next, whether that's a follow-on project, a claims team, or the organization's estimating group.
Exam Tip: If a question describes a scenario where a delay claim surfaces well after project completion and asks what should have been done differently, the answer almost always points back to Task 5 — inadequate archiving of intermediate schedule versions and supporting progress data, not a failure in the original scheduling technique itself.
Why This Domain Carries Real Weight Despite Its Small Exam Percentage
At 6% of the exam, Domain 4 generates comparatively few questions. But the underlying discipline it tests — closing out a schedule so it remains useful and defensible after the project team disperses — is exactly what separates a scheduler who produces a good-looking Gantt chart from one who leaves the organization with something it can actually reuse. A well-executed Domain 5 (Stakeholder Communications) keeps people informed during the project; a well-executed Domain 4 makes sure the project's schedule knowledge survives after the project itself is over.
Final Exam Preparation Focus
When studying Domain 4, focus on distinguishing its five tasks clearly from one another: obtaining acceptance is a sponsor-facing sign-off, evaluating performance is an analytical exercise, updating OPAs is an organizational-learning step, distributing reports is a communication step built on EVM data, and archiving is a records-management step aimed specifically at satisfying contractual requirements and surviving a future forensic review. Exam scenarios often test whether you can tell these apart when a question blends elements of more than one.
