PMI-SP Domain 4: Schedule Closeout

Domain 4 is 6% of the PMI-SP exam: the five official closeout tasks, from final acceptance to archiving, with as-built, EVM at completion and a self-test.

Domain 3 runs until the last activity is statused. Domain 4 covers what the scheduler does after that: getting the contractual schedule items accepted, judging how the schedule performed, turning that judgement into something the organisation can reuse, issuing the final reports and archiving the files.

Domain overview

The PMI-SP Examination Content Outline describes Domain 4 as "activities related to finalizing all schedule activities, evaluating schedule performance against the original baseline, documenting lessons learned, and distributing final schedule information." At 6% it is the smallest of the five domains.

The PMI-SP Handbook gives 170 multiple-choice questions, 150 scored and 20 unscored pretest items, in three and a half hours. At 6%, Domain 4 is about 9 scored questions. The content outline PMI publishes for this credential is dated 2012, so check the PMI-SP page for a newer version before you book.

The outline lists five tasks and six knowledge and skill areas: contractual schedule components, schedule close-out procedures, feedback techniques, schedule review techniques, schedule issue management and transition planning. The figure pairs each task with the record it should leave behind. The task numbers are PMI's; the "leaves behind" column is ours.

The rules for storing and controlling schedule versions come from Domain 1, the baseline from Domain 2 and the versioned updates from Domain 3. The PMI-SP exam content overview maps all five.

Where the schedule ends on a newbuild

Before any closeout task, the team has to agree where the schedule finishes. The GAO Schedule Assessment Guide says everyone affected by the schedule should agree on the final actions that make up completion; if the scope includes financial closeout, contract disputes or final payments, those belong before the finish milestone.

On a ship the question is real. Delivery takes place when the protocol of delivery and acceptance is signed, and title and risk pass to the buyer at that point. The builder's responsibility continues: shipbuilding contracts commonly carry a guarantee period of twelve months from delivery for defects in design, material or workmanship, as in the Norwegian SHIP25 standard form. Our article on how a shipbuilding contract works covers delivery and the guarantee period, and sea trials and delivery follows the final phase from the project team's side.

The PMBOK Guide, sixth edition (2017), describes Close Project or Phase as the process of finalizing all activities for the project, phase or contract, performed once or at predefined points. Illustrative example: the construction schedule closes at delivery, while guarantee claims, retention release and the final account run in a small post-delivery schedule that closes when the guarantee period ends. Whatever the split, write it down, so nobody argues later about which date "completion" meant.

Task 1: Obtain final acceptance of the contractual schedule components

In the outline: obtain final acceptance of the contractual schedule components, working with the sponsor or customer, to support project closeout.

The contract decides what these components are. Depending on the contract and specification, they may include the delivery date and other dated milestones, schedule submittals such as a final or as-built schedule, the record of actual milestone dates and the time effect of approved changes. The PMBOK Guide lists the milestone list, with the final dates on which milestones were accomplished, and the accepted deliverables as inputs to closing, and notes that the project charter records who signs off.

Accepting these items is not the same as accepting the ship. A vessel can be delivered while the parties still disagree on how many days of delay the owner's changes justified, and that number decides whether delay liquidated damages apply. Illustrative example: the yard claims 20 days of extension for owner variations; the final acceptance states how many were agreed, cites the variation orders and closes the item. If there is no agreement, the item is logged as open and handed to whoever manages the dispute. That is the "schedule issue management" skill in the outline; the PMBOK Guide also uses the issue log at closing to confirm no issue is left open. Closeout is much faster when time effects were agreed as each change happened, as described in the change and variation order article.

Task 2: Evaluate final schedule performance

In the outline: evaluate final schedule performance against the baseline schedule, the scheduling approach and its implementation, using standard tools and techniques and asking stakeholders for feedback, to identify lessons learned and develop best practices.

Three things are evaluated: the results against the baseline, the scheduling approach that was chosen, and how well it was carried out.

Against the baseline. GAO calls the final version of the current schedule the as-built schedule, the plan as executed to completion, and recommends archiving it and comparing it with the original plan for lessons learned. PMI's Practice Standard for Scheduling (second edition, 2011) makes the same point: once the project is complete, the schedule model forms the basis for lessons learned and for similar future projects. The PMBOK Guide lists document, regression, trend and variance analysis among the data analysis techniques for closing.

Note the word "original" in the domain description. GAO warns that a rebaseline normally wipes out historical variances. If the project was rebaselined, show performance against the original baseline and against the last approved one, with the change log explaining the difference.

Useful questions for the comparison:

• Which activity types ran long or short: block fabrication, zone outfitting, commissioning, trials?
• Where did the critical path actually run, compared with the baseline prediction?
• How did the forecast delivery date move from update to update? A forecast that held for months and then slipped every period says something about the status process, not only about production.
• Did the approach fit the job: level of detail, update frequency, integration of subcontractor schedules?

Feedback. The outline asks for stakeholder feedback, not only numbers. Structured interviews or short workshops with production, design, procurement and the owner's site team can explain what the numbers alone do not.

Task 3: Update the organizational process assets

In the outline: update the organizational process assets by documenting the lessons learned and best practices identified, to improve business processes.

The PMI Lexicon defines organizational process assets as the plans, processes, policies, procedures and knowledge bases used by the performing organization. The PMBOK Guide lists the updates at closing: project documents, operational and support documents, closure documents and the lessons learned repository, which receives the finalized lessons learned register.

GAO names the most practical use of the as-built schedule: its actual durations, sequences, resources and productivity become basis-of-estimate input for analogous projects, and a source for building and checking fragnets, standard sub-networks for repeated work such as a systems test.

Illustrative OPA updates after a newbuild:

• revised man-hour norms per tonne for a block type, used in estimating man-hours and loading resources;
• a standard dock and sea trials fragnet with durations from the as-built record, used with the sea trial checklist;
• a default risk in the shipyard risk register template, such as late approval of a long-lead item.

In our view, a lesson that changes no norm, template, checklist or procedure has been recorded rather than learned. The outline points the same way: the purpose of Task 3 is to improve business processes.

Task 4: Distribute final schedule reports

In the outline: distribute final schedule reports, including earned value management (EVM) calculations and variance analysis, to stakeholders, to support project closeout.

The PMBOK Guide describes the final report as a summary of project performance, including schedule objectives with actual milestone dates and reasons for variances, and cost objectives with actual costs and reasons for variances. It is not the last weekly report with a new title.

EVM at completion has a trap. When all scope is done, earned value equals the budget at completion (EV = BAC) and the estimate at completion equals actual cost. Planned value equals BAC too, so SPI ends at 1.0 however late the project finished. Walt Lipke, who introduced earned schedule, put it bluntly: SPI fails for late performing projects. Report schedule performance in time units instead: planned against actual finish, and SPI(t), which at completion is planned duration divided by actual duration.

Illustrative example: a newbuild with a BAC of $42.0 million, a 30-month original baseline and one approved owner change that added a month.

The variance analysis is what readers need most: which part of the two months was the owner change, backed by the approved variation order, and which part was the yard's, traced to activities in the as-built schedule. The shipyard EVM lesson, the article on EVM in shipbuilding and the EVM tracker template cover the measures during execution. Who receives the report, and how, belongs to Domain 5: Stakeholder Communications Management.

Task 5: Archive schedule files

In the outline: archive schedule files, for example the final schedule model, the schedule management plan, periodic status reports and the schedule change log, according to defined procedures, to satisfy contractual requirements and prepare for potential forensic schedule analysis.

The defined procedures trace back to Domain 1, whose first task sets configuration management policies for storage, retrieval, change control and baseline control; the outline's cross-cutting skills also include scheduling data management procedures such as archiving. The Practice Standard for Scheduling (2011) notes that a unique version identifier for each instance of the schedule model is essential for proper archiving and audit, and that records explaining each change in durations or logic help if it becomes necessary to reconstruct what happened and why.

Why keep every update and not only the final file? AACE International's Recommended Practice 29R-03, Forensic Schedule Analysis, includes methods built on the contemporaneous project updates, and a separate section on validating updates and reconstructing them when they are missing. Reconstruction after the event is extra work and rests on assumptions. On a ship, a dispute can surface after delivery, when the planning team has moved to the next hull.

A practical archive set for a newbuild:

• the original baseline and every approved rebaseline, with approval records;
• every periodic update, identified by version and data date, with its narrative;
• the progress records and status reports behind the updates;
• the schedule change log and the variation orders behind baseline changes;
• the schedule management plan in force;
• the as-built schedule, the final report, the lessons learned and the Task 1 acceptance record.

Software changes during a long program, so one safeguard is to store an exchange format and PDFs of key views alongside the native files. The MPP file handbook covers reviewing archived Microsoft Project files without the original tool, and getting started with MS Project for shipbuilding schedules shows how baselines and actuals are recorded.

Transition planning

The last knowledge area in the outline is easy to overlook. The PMBOK Guide includes the transition of the final product, service or result to the group that will operate and support it. For the schedule, decide who receives what: the estimating group gets the as-built data and norms, the guarantee team gets the open items and the post-delivery schedule, and a claims team gets access to the archive if a dispute is expected. For a yacht build, the yacht master schedule lesson shows the critical path that ends at the delivery this handover follows.

Typical exam traps

• Physical completion vs acceptance: a delivered ship does not mean the contractual schedule components are accepted.
• SPI at completion: always 1.0; report time variance or SPI(t).
• Original vs current baseline: the domain description says original; show both after a rebaseline.
• Final file vs full archive: forensic analysis needs the periodic updates, not only the as-built schedule.
• Domain 3 vs Domain 4: controlling change during execution is Domain 3; evaluating and archiving after the last update is Domain 4.

Test yourself

These questions are written for this lesson, not taken from any PMI question bank.

1. The ship has been delivered, but owner and yard still disagree on 12 days of claimed extension. Which Domain 4 task is not complete? A) Task 1. B) Task 3. C) Task 4. D) Task 5.

2. A project finished four months late with all scope delivered. What is the final SPI? A) Below 0.90. B) 1.00. C) It cannot be calculated. D) Equal to the CPI.

3. Planned duration was 24 months and actual duration 27 months. What is SPI(t) at completion? A) 0.89. B) 1.00. C) 1.13. D) 0.75.

4. A delay claim is raised a year after delivery. The archive holds only the as-built schedule. What is the main weakness? A) No lessons learned. B) The periodic updates with data dates and narratives are missing. C) No final EVM report. D) The schedule management plan was not signed.

5. The project was rebaselined once after an approved owner change. What should the final evaluation show? A) Only the last baseline. B) Only the original baseline. C) Both, with the change log explaining the difference. D) Neither; use CPI only.

Answers: 1 A, the time effect is a contractual schedule component still open. 2 B, EV equals PV equals BAC at completion. 3 A, 24 / 27 ≈ 0.89. 4 B, forensic methods rely on the contemporaneous updates. 5 C, a rebaseline wipes historical variance.

Where this leads

Closeout turns the schedule from a control tool into a record. The next lesson, Domain 5, covers stakeholder communication. Study this domain with the PMI-SP Examination Content Outline and PMI's Practice Standard for Scheduling, now in its third edition (2019).