Skip to content
EMPOBase
en

What belongs on an NGO project closure checklist?

By the EMPOBase team · · 4 min read

Short answer

An NGO project closure checklist covers seven areas: programme results, finance, assets and stock, staff and contracts, partners and sub-grants, donor reporting and approvals, and records. Start it three to four months before the end date, give each line an owner and a due date, and close the project only when every line is done or has a written exception.

Key points

  • Start the checklist months before the end date, not in the last week.
  • Cover seven areas: programme, finance, assets, staff, partners, donors, records.
  • Every line has one owner and a due date.
  • Record exceptions in writing; do not leave lines blank.

Why close a project on purpose?

Projects rarely fail at closure. They drift. The last activity ends, staff move on, and loose ends stay open: an unpaid supplier, a vehicle nobody owns, a final report with no author. Months later, an auditor asks about them and nobody remembers.

A closure checklist makes the end of a project a managed step. It protects the team, the donor relationship and your next proposal to the same donor.

When should closure start?

Start three to four months before the end date. Many items, such as asset transfer approval or a final audit request, need weeks of lead time. If you wait until the last month, you will rush the items that matter most.

What belongs on the checklist?

Group the lines under seven headings. Adapt the lines to your donor agreement.

  1. Programme results. Final indicator data is collected and reviewed. Targets and actuals are compared and gaps explained. Final beneficiary or activity lists are complete. Evaluation, if required, is finished.
  2. Finance. All invoices and claims are received and paid. Advances and petty cash are cleared. Final expenses are posted and the budget vs actual is reconciled. Unspent funds and any refund are agreed with the donor.
  3. Assets and stock. Every asset bought with project funds is listed. Each has a decision: transfer, donate, keep for another grant, or dispose. The donor’s approval is on file where required. Remaining stock is counted and handed over.
  4. Staff and contracts. Contract end dates, final pay and leave balances are confirmed. Staff receive notice in line with their contracts and local law. Handover notes are written.
  5. Partners and sub-grants. Partner reports and final financial statements are received. Partner agreements are closed in writing. Any partner assets are dealt with.
  6. Donor reporting and approvals. The final narrative and financial reports are scheduled with owners. Required no-cost extension or closure letters are sent. Audit requests are known.
  7. Records and learning. Project files are complete and stored where they can be found. A retention end date is set. Lessons are captured, for example in an after action review.

How do you assign and track it?

A checklist only works if it has owners and dates. For each line, record:

  • one named owner,
  • a due date,
  • a status: not started, in progress, done, or exception,
  • a note or a link to the evidence.

Review the checklist in a short meeting every two weeks during the closure period. Use the project manager as chair and ask finance and logistics to attend. A line marked “exception” needs a reason, an approver and a date to review again.

What gaps appear most often?

These are the lines teams most often miss:

  • Assets with no decision. Laptops, motorbikes and generators sit in an office with no recorded owner.
  • Liabilities after the end date. Final rent, utilities or severance are not budgeted.
  • Missing partner closure. The partner agreement ends by date but is never formally closed.
  • Records scattered across inboxes. Evidence is in personal email, so it leaves with the staff member.
  • No retention date. Files are kept forever, or deleted too early.

What should happen after the checklist is complete?

Closure does not end with the last tick. Hold a short closing meeting with the team and the sponsor. Confirm that every line is done or has a written exception, and that open items have owners and dates.

Then tell the people affected. Staff need clear notice. Partners need a closing letter. Communities may need a final meeting that explains what ends and what continues. Check what your agreements and local law require for each.

Finally, protect what you learned. Store the final reports, the checklist and the lessons where the next proposal team can find them. A project that closes well becomes the evidence behind your next grant.

Where EMPOBase fits

EMPOBase has a Closure Checklist and an After Action Review in its Programs module, so closure steps sit with the project record next to the Charter and RACI. The Closure Checklist tracks what you list; it does not check your donor agreement for you, so build the lines from your own contract. Final figures can come from Grant Finance and Budget vs Actual. See the platform overview or ask us for a demo.

Questions people ask

Who should sign off a project closure?

The project manager completes the checklist. The person who sponsors the project, often a country director or head of programs, signs it. Finance should confirm its section.

How long should we keep project records after closure?

Check the donor agreement and local law. Retention periods differ by donor and country, and some run for several years. Write the end date of retention on the checklist.

What if a donor report is still due after the project ends?

List it as an open item with an owner and a date. A project can close operationally while a final report or audit is still pending. Do not release the records until it is done.