Project Exit Strategy: How to Plan the Handover

When It Matters

An exit strategy sets out the reasons, content, timing and method for your organization to conclude its involvement. That covers transitioning, handing over, decommissioning infrastructure and disengaging. Some organizations put it more simply: a plan the project team carries out to pass along knowledge, resources or management when the project ends.

It belongs in program design from the start, not in the final months. Ideally the strategy exists from the beginning of a response and involves communities and local stakeholders. Planning early forces hard questions about local leadership and government budget allocation while there is still time to act on the answers.

You need one whenever a project will be handed to a community group, a local organization, a government body, or a partnership among them. Two situations should trigger it: the project reaches its stated objectives, or it fails. Some exits are not planned at all. The end of funding and reduced resources are typical causes. The point of the strategy is not to speed up departure. It is to improve the chance that results last.

How It Works

Start with four questions in early planning. Which outcomes do we want to sustain? Who is responsible for each? Do they have the knowledge, skills and resources? How are stakeholders being involved and kept informed? Then work through this sequence.

Map stakeholders at the start. This shows who could be involved and whether an exit strategy is feasible at all.
Set exit criteria. These are the conditions that would prompt you to move on. One guidance tool treats identifying them as the first step in designing the exit.
Design the strategy jointly with the people who will take over. Agree roles, responsibilities and realistic timeframes.
Build capacity during the transition. Invest in technical and management skills, and develop management and operational plans together with the receiving party.
Communicate with communities in four stages: planning the exit, community consultation, services stopping and being handed over, and monitoring after you finish.
Monitor after handover to see whether the results hold.

Exits are often described in three ways. Phasing down means gradually reducing services while keeping a minimal presence. It is often a first step before the other two. Phasing over means handing program activities to local institutions or communities. Phasing out means pulling out without transferring the program to anyone for ongoing execution.

Planning the exit with partners and stakeholders before close-out is linked to better project results and stronger commitment to sustainability.

Key Components

A written exit strategy should be detailed, with all the activities, agreed roles and responsibilities, and realistic timeframes and completion dates. Include:

Activities: every activity needed to complete the handover.
Roles and responsibilities: duties agreed with communities and other local stakeholders, not assigned to them afterward.
Timeframes: realistic timeframes and completion dates.
Exit criteria: the conditions or trigger metrics that mark the point to move on.
Capacity development: technical training, procurement, budget management and organizational development, so the taking-over entity can run services independently.
Communication plan: who tells whom, the audience, the content and the channels.
Contingency plans: extra resources for cases where complete withdrawal is not feasible.

Use the five dimensions of sustainability as a check on the whole document: technical, financial, institutional, socio-cultural and environmental. If a dimension has no owner in your plan, that is a gap.

Best Practices

Plan from the start. Develop the strategy once broad objectives are defined and before implementation begins. Exit planning takes budgeting and sometimes extra funds, so it needs a place in the proposal.
Design it jointly so local partners own it. A strategy handed to partners at the end will not be theirs. Build it with the government, community and other local partners who will support the changes.
Treat it as a living document. Contexts and partner circumstances shift, so revisit the plan regularly. Timelines need room to move.
Tell communities early and in several channels. Share exit information well in advance, with timing set by context and program length. Use as many channels as you can, such as posters, community mobilizers, SMS and radio. Say when services will stop, what has been achieved, and how people can ask questions and raise concerns at each stage. For specific changes, one guidance tool says to give at least 1 week of warning. Consider a softer word such as transition, because exit can sound negative.
Set a defined endpoint or trigger. A compulsory endpoint makes the team deal with the sustainability questions first, including local ownership, government budget allocation and local leadership.
Share the plan openly with partners. Giving people a chance to take part makes the handover smoother and cuts problems after you go. In one account, openly sharing the exit plan changed how partners thought about their respective roles.

Common Mistakes

A plan on paper with nobody to hand over to. Exit strategies often never happen or fail because no one was identified as the successor, or because too little transition time was allowed. Map actors at the start and build the transition period into the timeline.
No defined endpoint. Without one, the NGO is quietly locked into an open-ended role and partners drift into a dependency mindset. Set the endpoint or trigger metric at the outset.
Reading absence of need as readiness. Needs going away does not show that local capacity can carry on. Test capacity directly, using the sustainability dimensions.
Forgetting that the people you serve expect the benefits to continue. They link your team to the benefits, which makes leaving hard. Start communication early and explain what has been achieved and how to voice concerns.
Planning the exit after budgets are fixed. Exit work needs money, sometimes extra. Plan it while objectives are still broad, before implementation.

Example

In one water-trucking exit, communities affected by the end of the service were told about the new processes. People felt well informed and said they appreciated the information. The planned end date for the service was pushed back because of a cholera outbreak and the response to it. That delay is one reason exit timelines need flexibility.

A separate case shows the value of openness. An international NGO working with local partners shared its exit plan directly. Once the partners took in that the NGO really would leave, their view of their respective roles changed at once.

For a proposal you are writing now, the lesson is practical. Put the endpoint, the receiving parties, the communication stages and contingency plans for extra resources in the design, and budget for them.