Your organization should treat the transition from proposal to implementation as a formal management handover. The team that wrote the application may not be the same people who will manage the award, and important assumptions can remain buried in draft files, email threads, or the writer’s memory. A structured handover helps your NGO or CBO convert donor-facing commitments into operational responsibilities before delivery begins.
Transfer the authoritative award package
Your implementation team should receive the exact submitted proposal, approved budget, final results framework, donor clarifications, signed agreement, partner commitments, and any negotiated changes. Earlier drafts should be clearly separated so staff do not accidentally work from assumptions that were later revised. This is especially important where the donor reduced the award amount or changed targets during negotiation.
Use a proposal-to-implementation handover table
| Handover area | What your organization should transfer | Leadership question | Risk if missed |
|---|---|---|---|
| Scope | Final activities, geography, beneficiaries | What exactly did the donor approve? | Project team delivers an outdated design |
| Budget | Approved lines, assumptions, restrictions | Which costs are flexible and which are not? | Early compliance or cash-flow problems |
| Results | Targets, indicators, baseline commitments | Can the team measure what was promised? | Reporting gaps later |
| Partners | Roles, budgets, letters, due-diligence status | What is the lead organization accountable for? | Partner obligations are misunderstood |
Explain the assumptions behind the proposal
Your organization should hand over more than the final documents. The implementation team also needs to understand staffing assumptions, procurement lead times, exchange-rate exposure, partner dependencies, and the reasoning behind major targets. These assumptions should be highlighted because they are often the first things to change after award.
Detailed example: when the implementation team inherits the wrong version
Imagine your NGO wins a USD 500,000 education grant. The original proposal planned 12 schools, but during award negotiation the donor reduces the budget and approves work in 8 schools. The program team, however, begins startup from the earlier concept note and starts contacting all 12 schools.
A formal handover would have flagged the approved change and linked the final budget, targets, and workplan. The executive director can then ensure that procurement, staffing, partner agreements, and MEL all align with the 8-school model. Without this step, the project can create commitments it no longer has funding to honor.
Transfer open risks into live management tools
Any unresolved staffing, procurement, co-financing, safeguarding, partner, or evidence risk should move from proposal notes into a live risk register. The same applies to donor conditions that require early action, such as registration, insurance, baseline work, or partner due diligence. A risk that disappears during handover often reappears later as a delivery problem.
Handover checklist
- The final donor-approved package is clearly identified.
- Negotiated changes are documented.
- Budget assumptions and restrictions are explained.
- Targets and indicators are handed over to MEL staff.
- Partner commitments and open due-diligence items are transferred.
- Key donor communications are stored centrally.
- Open risks are moved into the live project risk register.
- A cross-functional handover meeting is completed before full startup.
What boards and institutional donors are likely to expect
Boards should expect management to know exactly what the organization agreed to deliver before implementation begins. Institutional donors are also likely to assume that approved commitments have been translated into internal controls, reporting systems, and partner expectations. A strong handover reduces the risk that the project spends its first months rediscovering what was promised.
What to do next
Use the Grant Management File Index to organize the award package and implementation evidence from the start. For practical funding intelligence, subscribe to Africads Grant News.
Frequently asked questions
What should be included in a grant handover?
Transfer the final approved proposal, budget, results framework, signed agreement, donor clarifications, partner commitments, negotiated changes, key assumptions, and open risks. Earlier drafts should be clearly separated from the authoritative award package.
Who should attend the handover meeting?
Include the proposal lead plus the people who will manage program delivery, finance, MEL, procurement, safeguarding, partnerships, and leadership oversight. The goal is to transfer accountability, not simply files.
What if the donor changed the award during negotiation?
Document every material change in amount, scope, targets, timing, or partner responsibilities and make sure the implementation team uses the negotiated version rather than the original proposal.
Should proposal assumptions be transferred too?
Yes. Staffing, procurement, exchange-rate, partner, and target assumptions often explain why the proposal was designed a certain way and should be monitored after award.
When should the handover happen?
As soon as the award terms are final enough to support startup, ideally before implementation begins. Delaying the handover increases the risk that teams act on outdated drafts or incomplete information.
Conclusion
A strong handover converts donor-facing promises into operational responsibilities. Your organization should transfer the final award package, explain the assumptions and changes behind it, and move open risks into live management systems before delivery starts.
Put this guide into practice
Free resource: The Funding Checklist. Use this funding checklist when preparing your organization for its next donor conversation or funding cycle.
