Project closeout
Closeout is where a programme proves what it did, settles what it owes and hands over what it built. It is often the least resourced phase: staff leave, records scatter and deadlines compress. Unfinished closeout surfaces later as audit qualifications, refund claims, orphaned assets and lost evidence. This page sets out how closeout risk develops, what a complete closeout contains, and what the institutions that review, receive and learn from the work need.
- 01In briefDefinition and scope
- 02The question4 mechanisms
- 03Key terms3
- 04FieldH3 field plate
- 05Indicators8
- 06PipelineRun graph
- 07Sources6
- 08Decision holders4
- 09Methods2
GCRI · Established · service level R0
The short answer.
Project closeout is the phase in which a programme proves what it did, settles what it owes and hands over what it built. It is often the least resourced phase, and unfinished closeout surfaces later as audit qualifications, refund claims, orphaned assets and lost evidence.
Jurisdictions in the Mediterranean.
The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for the Mediterranean as an example geography for this subject.
Assignment and team board, in outline.
The working screen behind this subject: its structure, terms and states. Names are placeholders and values illustrative.
Assignment and team board
Project closeout · Assignment pool · Quarter 1
Assignments
Team record
| Team lead | Disaster risk management | None declared | Confirmed |
| Hydrologist | Flood modelling | Declared, managed | Confirmed |
| Data engineer | Pipelines | None declared | Invited |
| Reviewer | Independent | None declared | Confirmed |
Scope
- Requester
- Requesting institution
- Duration
- 10 weeks
- Authority
- stays with the requester
- Fee
- R0 · no fee stated
Project closeout: how the risk develops.
Review, evidence, learning and lawful handoff. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Closeout is compressed
Final deliverables, financial reconciliation, evaluation and handover fall in the same weeks as staff leave for new assignments. Tasks that need care, such as records transfer and grievance resolution, are the first to slip.
Evidence decays
Results data, decisions and supporting documents sit in personal drives and email. Once the team disperses, claims in a completion report cannot be traced to their evidence, and evaluators rely on recollection.
Handover without ownership
Systems, equipment and data are transferred to an institution that has no budget, staff or legal acceptance for them. They fall out of use or out of compliance, and the investment is lost.
Open obligations cascade
Unreconciled accounts, unspent advances, open grievances and personal data held beyond its purpose lead to audit qualifications, ineligible expenditure, refunds and complaints. These can delay or block the next financing for the same institution.
Terms used on this page.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Completion report | The final report on a project's results, costs and lessons, often validated independently. |
| Lawful handover | Transfer of assets, records and responsibilities to a receiving institution with signed acceptance. |
| Ineligible expenditure | Spending that does not meet the financing agreement's rules and may have to be refunded. |
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Completion reports submitted within the required period | percent of operations | annual | Funding agency records | OFFICIAL |
| Final audit opinion | category: unmodified, qualified, adverse, disclaimer | per operation | External audit reports | OFFICIAL |
| Ineligible expenditure identified at closure | currency amount | per operation | Audit and funder review | OFFICIAL |
| Assets transferred with signed acceptance by the receiving institution | percent of assets | per operation | Handover records | REPORTED |
| Grievances open at closing date | count | per operation | Grievance mechanism records | REPORTED |
| Records transferred or disposed of under a retention schedule | percent of record series | per operation | Records management logs | REPORTED |
| Evaluation ratings against DAC criteria | ordinal rating by criterion | per evaluation | Independent evaluations | ESTIMATED |
| Completion report ratings confirmed by independent validation | percent of validated reports | annual | Evaluation office validations | OFFICIAL |
From sources to decisions.
The topic as a computational graph: named sources feed the methods, an evidence review gates the outputs, and the decisions stay with the authorities that hold them.
Fig. 02Nodes carry their type, two metric rows and a state; connectors show what feeds what; dashed frames name the owners; the timeline is the cadence. Design of the pipeline, not a record of a run.
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Source | What it gives | Licence class |
|---|---|---|
| World Bank Implementation Completion and Results Reports and IEG reviews | Self-assessed results and independent validation of closed operations | Public documents under the World Bank access to information policy |
| Asian Development Bank completion reports and validations | Project completion reports and validation by the independent evaluation function | Public documents under ADB access to information policy |
| OECD DAC Evaluation Resource Centre | Final and ex post evaluations from member agencies | Public reports, terms per evaluating agency |
| IATI Datastore | Activity status, end dates, final budgets, results and documents of closed activities | Open, licence declared per publisher |
| UN Board of Auditors reports | Audit findings on UN entities, including closure of projects and assets | Public documents |
| National supreme audit institution reports | Audits of closed programmes and of financial statements of implementing agencies | Public records, terms per audit office |
Who decides, and what the evidence serves.
Nexus Agency prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Implementing agency | Whether every obligation is settled before the closing date, and what remains open | Closeout checklist with open items and their holders |
| Funding agency | Whether expenditure is eligible, refunds are due and the completion report can be accepted | Audit opinion, reconciliation and evidence register |
| Receiving institution | Whether to accept assets, systems and data, and on what terms | Handover protocol, condition records and recurrent cost notes |
| Supreme audit institution or evaluation office | Whether reported results are supported by evidence | Evidence register and records retained under the retention schedule |
Outputs this topic produces
- Closeout checklists covering deliverables, finance, assets, grievances, data and records
- Evidence registers that link each reported result to its source
- Handover protocols with receiving-institution acceptance and recurrent cost notes
- Lessons records written for retrieval by later assignments
What closeout must settle.
- Were the deliverables accepted against the criteria agreed at the start?
- Where are the outputs, data and documentation, and who maintains them now?
- Which personal or confidential data must be returned, retained or deleted, and under what rules?
- What went well, what did not and what should change next time?
How value leaks at the end.
Projects often end in a rush: final reports are delivered without review, models are left without documentation, data sit on personal devices and the host has no one trained to maintain what was built. Lessons are lost because no one is asked to write them down.
A deliberate closeout prevents this by treating handover as a deliverable in its own right, with time and responsibility assigned to it.
Signals of a good closeout.
- Time and a named owner for handover in the original plan.
- Documentation sufficient for someone new to run or rebuild the outputs.
- A data inventory showing what was returned, retained or deleted, and why.
- Lessons written down with an owner for each action.
How it is studied, and what the methods cannot say.
Questions and answers.
What is a lawful handover?
Why plan closeout at the start?
What do the DAC criteria cover?
What happens to personal data at closeout?
What if the host does not accept a deliverable?
Are closed assignments removed from the site?
What happens to personal data collected during the work?
Can I get a record of my contribution?
Around Nexus Agency.
Bring your expertise to this field.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.