Program Closure: Gate Sheet, Benefit Handover and a ₹ Example

A program is ready for closure when five tests pass: every component is accepted in writing, the people who use the output are using it, each benefit has a business owner who has accepted it, each benefit has a baseline, a target and a dated first measurement, and the business case still holds. If tests 1 to 4 fail, delay. If the business case fails, stop early. A component is a project or other work package inside the program. The business case is the approved document that justifies the program's spend by the benefits it expects.

The outcome follows from the tests:

• Close: all five pass and the benefits are at or above target.
• Close with residual: all five pass, but a benefit is below target and trending up. Record the gap and its owner.
• Delay: any of tests 1 to 4 fails, or a delivered benefit shows no movement.
• Terminate early: test 5 fails.

The five tests and these four outcomes are our recommended gate sheet, built from the Standard for Program Management and the UK government's benefits workbook. They are not an official PMI requirement.

In our view, program closure so often stops at delivery because delivery is the part the program team controls and can sign off, while the benefit depends on the business changing how it works after the team leaves. Closing on delivery alone leaves the benefit with nobody. This is our reasoning, not a measured failure rate.

The closure guidance we reviewed commonly stops at handover to operations and does not name a benefit owner. It covers acceptance, documentation and lessons learned, which matter, but a handover to "operations" is not a handover to a person who can be asked in six months what happened to the benefit.

The Standard for Program Management, Fifth Edition from PMI (Project Management Institute) treats closure as the last phase of the program life cycle. Our program management life cycle page shows where the closure gate sits among the other gates.

In our recommended model, the business owns each benefit after closure and the program manager owns the plan that hands it over. Before closure, a benefit owner is accountable for realising and reporting the benefit. At closure that accountability moves to a receiving owner, a named operating role such as a head of operations, who accepts it in writing.

This settles a disagreement that recurs in PgMP® (Program Management Professional) preparation. A practice scenario that candidates often discuss sets an operations manager, who fears the information needed to manage the benefit will be gone after closure, against a program manager who calls post-closure benefits out of scope. In our view both are half right. The benefit is outside the program's scope once the program ends, but the handover is inside it. The program manager therefore prepares the transition and sustainability plan before closure, and the receiving owner accepts it.

The UK government's benefits practitioner workbook advises agreeing a clear process and defined responsibilities for closing benefits after handover to operations. Our guide to benefits realisation management covers how to build the benefits register that feeds the record below.

A benefit handover record has one row per benefit and nine fields, each with a pass test. It is the document that makes ownership real.

The workbook gives these examples of when a benefit can be closed: it has been fully realised and further monitoring is unlikely to add value; it has been partly realised over a set period and is unlikely to increase further; or it is being realised on an ongoing basis and will be monitored through operational performance reporting. When you close a benefit, record the actual benefit realised, the reason for closure, the date and who made the decision.

For a ₹42 crore loan-origination digitisation program, closure becomes "close with residual", with two benefits still short of target and each under a named owner. The figures below are illustrative, invented to show the working. They are not real program data.

Assumptions: 1,20,000 applications a year; 82% of applications are on the new process against a 75% threshold in the benefits plan; every component is accepted; both receiving owners have accepted their benefits in writing; the handover record is complete; cost per application has fallen in each of the last three months; the business case still holds. Tests 1 to 5 therefore pass.

Our working:

• Target saving per application: ₹1,850 − ₹1,100 = ₹750. Over 1,20,000 applications that is ₹9,00,00,000, or ₹9 crore a year.
• Saving at closure: ₹1,850 − ₹1,300 = ₹550. Over 1,20,000 applications that is ₹6,60,00,000, or ₹6.6 crore a year.
• Cost-per-application residual: ₹9 crore − ₹6.6 crore = ₹2.4 crore a year. This residual covers cost per application only, and it is owned by the Head of Operations.
• Turnaround is a second residual: 3.1 days against a 2-day target is 1.1 days short. The target cut is 4 days and 2.9 days are achieved, which is 72.5% of the target cut (2.9 ÷ 4). We have put no rupee value on it. The Head of Retail Lending owns it.

The outcome is close with residual. Neither gap vanishes from view: both sit in the handover record, each with an owner and a re-measure date.

When a program is stopped early, run the full closure anyway: close every contract, lock cost codes (the accounting codes that program spending is booked against), release people, log lessons, and record the reason, date and decision-maker. Stopping is a legitimate outcome when the business case no longer holds, which is test 5 of the readiness test.

A stopped program leaves the most debris. Suppliers are still contracted, and benefits that were partly delivered have no owner. Treat each delivered component as a benefit in its own right and give it a receiving owner, or record that it is being abandoned and why. The decision rights belong in your program governance framework. For the portfolio-level version of this call, see when a portfolio should kill a project.

A close-out list covers six items, each with a test you can run.

We teach closure as a benefit handover, not an archive exercise, and more than 6,000 professionals have been mentored or trained by Augment Consultancy. Program Management Essentials is a 12-week foundation course of 10 modules and more than 15 hours. Its benefits module covers benefit transition and benefit sustainment, the skills behind the handover record above. It is not a PgMP® exam-preparation course; for that route, see the last answer in the FAQ below.

As of October 2026, Program Management Essentials costs US$99 and the PgMP® Self-Paced Mentorship Program US$549 per enrolment; pricing varies by market. Digital courses are non-refundable, so ask for our free eligibility consultation before enrolling.