NISM Professor

Exit/Takeover Plan

Also written Takeover Plan · Exit/Takeover Protocol Fund

A concrete plan, developed towards a project's end, for using the assets, capacities and partnerships built during the project to sustain its impact after the project itself is over.

In plain language

A social project cannot run forever. At some point it ends, and the question becomes: what happens to the people, systems and relationships it built?

An Exit/Takeover Plan is the answer a project is meant to prepare in advance rather than improvise at the end. The workbook's own words: it involves "a meaningful planning exercise with stakeholders and the beneficiary community" to "utilise assets, capacities, partnerships, networks, and influence built during the project to sustain its impact" beyond the project's own timeline.

How it works

The Exit/Takeover Plan is funded through what the workbook calls the Exit/Takeover Protocol Fund, one of the cost categories a project must budget for under section 4.3.3 (Assigning Accurate Costs for Inputs Related to Project Sustainability). It sits alongside three other named cost heads:

Cost headWhat it funds
Listing CostRegistration and listing costs on the SSE, split between the enterprise and the funder
Pre-project Implementation FundThe t0 year activities — beneficiary selection, manpower, community planning — before the project formally begins
M&E and Knowledge Management FundMonitoring, evaluation, and cross-learning among stakeholders
Exit/Takeover Protocol FundThe post-mid-term planning that produces a concrete Exit/Takeover Plan

The workbook places this planning "towards the end of the project", involving stakeholders and formalising co-commitment instruments — agreements that institutionalise the processes and systems the project built, so they keep running once the project's own funding and staff are gone.

A worked example

Illustrative figures.

A 3-year water-conservation project has built 40 check dams and trained a village-level water committee in each of 25 villages, on a total budget of ₹4 crore.

In its final 6 months, the project uses its Exit/Takeover Protocol Fund of ₹12 lakh (part of the original ₹4 crore) to:

  • Formally hand over check-dam maintenance responsibility to each village water committee, with a signed co-commitment instrument.
  • Train two committee members per village as certified maintenance leads.
  • Connect each committee to the district irrigation department for future technical support.

Two years after the project's formal end, an independent check finds 34 of the 40 check dams still properly maintained by the village committees — evidence that the Exit/Takeover Plan, not the original construction alone, is what sustained the impact after the project itself wound down.

Why NISM asks about it

Chapter 4, section 4.3.3, names the Exit/Takeover Protocol Fund as one of four cost categories a project must plan for, and describes the resulting Exit/Takeover Plan. Expect a question on when this plan is developed (towards the end of the project, not at the start) and what it is meant to achieve (sustaining impact beyond the project timeline through co-commitment instruments).

Common exam traps

  • The plan is developed towards the END of the project, using assets already built — not at the start, unlike the Pre-project Implementation Fund, which covers activity before the project even begins.
  • "Co-commitment instruments" are the formal mechanism for institutionalising the handover — a question testing this term is looking for a formalised, agreed commitment, not an informal handover.
  • This is a cost category to be budgeted for in the project design, not an optional afterthought — the workbook lists it alongside listing cost and the M&E fund as a required planning item.
  • Do not confuse the Exit/Takeover Plan with the Impact Management Project's Contribution dimension — Exit/Takeover planning is about sustaining impact after project close, not about measuring how much impact to credit to the enterprise.

Where this is taught

Free preparation for NISM Series XXIII

Related terms

← All terms
Something look wrong? Report it