> 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/launch.md).

# Launch

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

The launch phase establishes and strengthens the preconditions for optimal activity execution.

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

The launch phase is the fourth phase in the project cycle. It starts when the proposed project is funded and ends when the project activities are ready to be implemented and when a MEAL framework is established.

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

The launch phase involves:

a) Re-assessing project relevance and feasibility because the context may have evolved since the development of the project proposal;

b) Developing a detailed MEAL framework;

c) Mobilising resources (Human Resources, Partners, Procurement…); and d) Communicating with stakeholders.

<figure><img src="https://703690093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjVZ7GutuuOfKVB2ccnej%2Fuploads%2Fa2bpRp8NTZKqVGpzpOvf%2FLaunch_Graph.png?alt=media&amp;token=8fcae9bd-e57e-43b3-a901-18a3c7b58ec1" alt=""><figcaption></figcaption></figure>

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

4\. Launch - The Planning, Monitoring, Evaluation, Accountability and Learning (MEAL) framework

5\. Launch - Resource mobilisation & communication

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

* Communities and people affected by the crisis should be involved in reviewing the proposed intervention and receive clear information about project objectives, modalities, and the feedback mechanism.&#x20;
* Operational staff and potential partners should be involved in the analysis of the proposed intervention, the development of a detailed MEAL framework, the mobilisation of resources and communication about the project launch.
* Support services (logistics, technical, HR…) should be involved in sharing examples of guidelines and tools in similar contexts; the development of a detailed MEAL system, the mobilisation of resources and communication about the project launch.

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

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

{% file src="/files/5umMpEF4riHft2l9ltkZ" %}

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

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

***

### <mark style="color:$primary;">Good practices for the Launch 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 %}