# Closing your collective

***Applies to:** All collectives fiscally hosted by All For Climate*\
\&#xNAN;***Effective Date:** June 2025*\
\&#xNAN;***Owner:** All For Climate (A4C) ASBL*\
\&#xNAN;***Implementer**: All For Climate Back Office support team*\
\&#xNAN;***Reviewed:** Annually or as needed*

### 🎯 Purpose

{% hint style="info" %}
This policy outlines the steps to properly close a collective hosted by All For Climate (A4C), ensuring responsible financial management, clear communication, and space for collective continuity when relevant.
{% endhint %}

***

### 🔁 Valid closure pathways

If a collective decides to close, the admin team must take the following steps:

#### 1. **Notify A4C of intent to close**

* A written confirmation is required from **all current admins** of the collective.
* The confirmation should include:
  * A short explanation of the reason for closure.
  * Agreement on what to do with any remaining funds (see below).
* This helps ensure transparency and shared decision-making among the leadership.

#### 2. **Allocate remaining funds**

Collectives can choose one or a combination of the following actions:

* Upload [valid expenses](/collectives/spending-money.md) to spend the remaining funds on the collective’s mission.
* Donate the remaining balance to [another collective](https://opencollective.com/allforclimate#category-CONTRIBUTIONS) hosted by A4C.
* Donate the remaining balance to the A4C Treasury (used for shared community needs and initiatives).

Once the balance reaches €0, A4C will proceed to unhost and archive the collective.

#### 3. **Inform your donors**

* We recommend informing your contributors—especially recurring donors—about the closure.
* You can do this via the Contributors tab in your collective’s dashboard on Open Collective.

***

### ⚠️ Disputed or contested closures

To prevent issues where a collective is closed without consultation with the broader movement it represents, the following provisions apply:

#### ✅ **Requirement: admin consensus**

* A4C will only proceed with closure after **written confirmation from all current admins** of the collective.
* This protects against unilateral decisions that do not reflect the intent of the entire collective's leadership team.

#### 🧩 **Option: continuation by other members**

If people from the movement wish to continue the collective but are not platform admins, they may submit a takeover request:

**Takeover request must include:**

* A motivation letter signed by at least two individuals involved in the movement.
* A clear explanation of:
  * Their vision for the collective.
  * Proposed activities and use of funds.
  * A request to become the new admins.

A4C will share the takeover request with the current admins for them to evaluate on a case-by-case basis, with the intention to preserve continuity if there is good faith effort and clear community support.

If admins do not object within 10 working days, A4C may approve the new admins and transfer control of the collective.

***

### 🧾 Final review

Before officially unhosting the collective:

* A4C will verify that:
  * All funds have been appropriately allocated.
  * Final communications (e.g. to donors) have been made.
  * No active grant obligations or legal issues remain.

Once reviewed and approved, the collective will be marked as “Archived” on the Open Collective platform.

***

### 📨 Contact for closure or takeover requests

All requests related to collective closure or continuation should be sent to:

**<info@allforclimate.earth>**\
Subject: **Closure or Takeover – \[Collective Name]**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.allforclimate.earth/policies/closing-your-collective.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.