> For the complete documentation index, see [llms.txt](https://help.givechariot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.givechariot.com/gift-processing/export-templates.md).

# Export Templates

Export Templates are reusable column layouts for donation exports. This allows your team to generate import-ready CSVs in one click instead of manually restructuring exports every time.

Build a Template once for each downstream system you use — like your CRM, accounting platform, or internal reports — then reuse it every time you export donations from Chariot.

Templates define exactly how your export should look — including fields, column order, naming conventions, formatting, and transformations.

***

### Building A Template

1. Click on Exports → New Template
2. (Optional) Upload a sample CSV from your CRM or downstream system to help Chariot automatically match your expected format.
3. Click on Mapping to refine template
4. Save Template

For the full list of fields available in an export, see [Donation Fields](/getting-started/donation-fields.md).

***

### Generating An Export

1. Go to the Donations page
2. Select donations ready for export
3. Click **Export**
4. Choose an Export Template
5. Download the formatted CSV


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.givechariot.com/gift-processing/export-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.