> 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/disbursements/for-grantmakers/customize-your-grant-letter.md).
# Customize Your Grant Letter
When Chariot sends a paper check on your behalf, the check is accompanied by a grant letter. The letter identifies the grantmaker, provides the grant details, and explains how the recipient can claim its Chariot account so future eligible grants can be delivered electronically.
Configure your letter before creating your first disbursement.
### What you can customize
Depending on your account configuration, your grant letter can include:
* Grantmaker or program name
* Logo
* Mailing address
* Support email address
* Authorized signature
* Legal attestation or other required language
* Grant details supplied with the disbursement
* Instructions for the nonprofit to claim its Chariot account
The recipient sees the grant as coming from your organization or the applicable program, even though Chariot manages check production and delivery.
***
### Update your grant letter
1. Open the grant-letter settings in your Chariot dashboard.
2. Add or update your organization name and logo.
3. Confirm the mailing address and support email recipients should use for grant questions.
4. Upload or select the authorized signature.
5. Review the legal attestation and other required language.
6. Preview the completed letter.
7. Save your changes.
***
### Program-specific letters
If your organization uses programs, each program can have its own name, logo, contact details, signature, legal attestation, and letter. Confirm that every program's letter is complete before sending disbursements from it.
See \[Set Up and Manage Programs].
---
# 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/disbursements/for-grantmakers/customize-your-grant-letter.md?ask=&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.
