> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/contracts/contract-templates/setting-up-your-contract-template.md).

# Setting up your Contract Template

If you are using the Tahua platform to send and receive digitally signed contracts, your first step is to set up a Contract Template. The beginning of this [Contract Overview](/knowledge-base/administrator-help-guides/contracts/overview.md) video has a good breakdown of how to do this.

As with all templates within the Tahua platform, you can create and edit this by going to the top right hand section of your Dashboard, and clicking Settings > Templates > Contracts.

You can then opt to Edit an existing Contract, or create a New Template.

<figure><img src="/files/LUdGrHSN5pI8dTsQtObM" alt=""><figcaption></figcaption></figure>

As with all Templates, you can use [Field Tags](/knowledge-base/administrator-help-guides/contracts/contract-templates/personalisations-and-field-tags.md) containing relevant information from other templates (i.e. Applications, Grants) to pull through personalisations into the Contract document.


---

# 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 dynamically by asking a question.

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

```
GET https://help.tahua.io/knowledge-base/administrator-help-guides/contracts/contract-templates/setting-up-your-contract-template.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.