# Export

The Coalitions export generates an Excel (.xlsx) workbook containing data from your coalitions. The export includes coalition details, members, meetings, and collaborators across multiple worksheets.

## Getting Started

To export coalitions, navigate to the Coalitions list under the **Engage** menu and click the **Export** button. The export includes all coalitions matching your current filters.

{% hint style="info" %}
**TIP:** Apply filters before exporting to limit the results to a specific reporting period, program area, or completion status. Large exports are processed in the background and you will receive an email when the file is ready to download.
{% endhint %}

## Workbook Structure

The export workbook contains the following worksheets. Data can be linked across worksheets using the **coalition\_id** column.

* **Codebook** — Describes each column in the workbook and provides notes about the exported data.
* **Coalition Data** — One row per coalition with fields including name, reporting periods, organization, unit, program areas, jurisdiction level, member and sector counts, assistance received and provided, relationship depth, assessment tools and results, accomplishments, intervention involvement, and timestamps.
* **Members** — One row per coalition member, including the member name, sector of influence, entity type, site details, and role and resources.
* **Meetings** — One row per meeting or event, including the event title, start date, attendance, purposes, and notes.
* **Collaborators** — One row per collaborator per coalition, including the user's name, access level, contributor status, and contribution description.


---

# 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://support.pears.io/engage/coalitions/export.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.