> For the complete documentation index, see [llms.txt](https://urd.gitbook.io/compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://urd.gitbook.io/compass/implementing/closure.md).

# Closure

### <mark style="color:orange;">Why?</mark>

The project closure confirms the completion of activities, recognises the level of achievement, facilitates learning from field experience and allows responsible administrative and contractual closure.

During the project closure phase, organisations may decide to either: 1. Terminate project activities (because the project has achieved its objectives and/or people’s needs have been satisfied, or because funds are no longer available and activities cannot continue, which can finish on a closure/handover); 2. Extend project activities by handing them over to another organisation, or the affected population or the local authorities take over responsibility for them; or 3. Start up a new project (because new needs have emerged or the project has not achieved its objectives).

### <mark style="color:orange;">When?</mark>

The project closure phase is the sixth phase in the project cycle. It starts when all the planned activities have been implemented. It ends when all the project components have been finalised, transferred and/or completed.

### <mark style="color:orange;">What?</mark>

This phase principally involves the operational closure (end of activities and monitoring); administrative closure (Finance; Logistics; HR…); learning; and internal and external communication.

<figure><img src="https://703690093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjVZ7GutuuOfKVB2ccnej%2Fuploads%2Fitz0tZuYxXfP6D6mvUV6%2FClosure_Graph.png?alt=media&amp;token=404ae76c-346d-4c91-a876-355ae7500981" alt=""><figcaption></figcaption></figure>

### <mark style="color:orange;">Q\&A control points:</mark>

8. Closure - The operational closure
9. Closure - The administrative closure

### &#x20;<mark style="color:orange;">Who?</mark>

* Communities and people affected by crisis should participate in the final data collection and analysis, learning activities and communication. &#x20;
* Operational staff and potential partners should be involved in the last data collection and analysis; a lessons learned workshop; the last project review; a final evaluation (if any); project archiving; information sharing (e.g. End of project report).
* Support services (logistics, technical, HR, etc.) should be involved to facilitate the last data collection and analysis; the lessons learned workshop; a final evaluation (if any) and the closure of any contractual files in accordance with national law, donor rules and internal regulations.

### <mark style="color:blue;">Checklist</mark>

You can download the checklist for Implementation - Closure in PDF version, available in English, French and Spanish.

{% file src="/files/gKHmUF2U2ECeAMdasOBI" %}

{% file src="/files/hyOaX3CTQoRY843HlhRs" %}

{% file src="/files/zwph6iu1HMNYjxTSESey" %}

***

### <mark style="color:$primary;">Good practices for the Closure phase by CHS commitments</mark>

#### People and communities affected by crisis

{% stepper %}
{% step %}

#### 1. Can exercise their rights and participate in actions and decisions that affect them

<mark style="color:$danger;">Essential</mark>

* Involve communities and people affected by crisis in the closure review, evaluations, and handover. &#x20;
* Make sure that all groups of stakeholders are informed about the achievements and the termination of the project.
  {% endstep %}

{% step %}

#### 2. Access timely and effective support in accordance with their specific needs

<mark style="color:$danger;">Essential</mark>

* Evaluate the extent to which the project addressed the affected communities’ needs and generated positive changes for them.
* If need be, refer all needs not covered to relevant organisations or advocate for them to be covered.
  {% endstep %}

{% step %}

#### 3. Are better prepared and more resilient to potential crises

<mark style="color:$danger;">Essential</mark>

* Finalise the exit strategy that was planned to ensure long term positive effects or justify any changes.
  {% endstep %}

{% step %}

#### 4. Access support that does not cause harm to people or the environment

<mark style="color:$danger;">Essential</mark>

* Make sure environmental impacts have been properly managed/mitigated.
* Store data properly in safe spaces. Any paper documents containing sensitive data should be equally secured or destroyed if necessary, and when possible.
  {% endstep %}

{% step %}

#### 5. Can safely report concerns and complaints and get them addressed

<mark style="color:$danger;">Essential</mark>

* Make sure all feedback and complaints have been addressed managed before the closure of the project.
  {% endstep %}

{% step %}

#### 6. Access coordinated and complementary support

<mark style="color:$danger;">Essential</mark>

* Share final project information with other organisations intervening in the same area.
* Ensure the effectiveness of activity transfers and their continuity in response to the needs and expectations of communities
  {% endstep %}

{% step %}

#### 7. Access support that is continually adapted and improved based on feedback and learning

<mark style="color:$danger;">Essential</mark>

* Identify, formalize and disseminate the main lessons learnt from this experience and any innovations, including community feedback.
  {% endstep %}

{% step %}

#### 8. Interact with staff and volunteer that are respectful, competent and well-managed.

<mark style="color:$danger;">Essential</mark>

* Anticipate the end of human resources contracts and facilitate staff transition.

<mark style="color:$success;">Ideal</mark>

* Organise an internal team event to promote team achievements.
  {% endstep %}

{% step %}

#### 9. Can expect resources are managed ethically and responsibly.

<mark style="color:$danger;">Essential</mark>

* Provide the necessary financial, time and logistical resources for the closure of the project.
* Make sure that project resources (especially real estate and equipment) are used by relevant partners or stakeholders after project completion.
* Share key information and lessons learnt with the relevant partners and through the appropriate communication channels.
  {% endstep %}
  {% endstepper %}