> 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-variations.md).

# Creating a Contract Variation

A contract variation allows you to create an amended version of an existing contract, with key details carried over automatically from the original.

**How to create a variation**

1. Open the relevant contract in Tahua.
2. In the sidebar, click **Create Variation** under the Actions section.
3. Follow the step-by-step wizard, which walks you through:
   * **Details** — the variation title, category, tags, contract number, dates, and contract manager are pre-populated from the original contract but can be edited as needed.
   * **Milestones** — review or update milestone information.
   * **Funding** — review or update funding details.
   * **Document** — upload or replace the contract document.
   * **Send Contract** — send the variation out for signing.

Most details will be imported automatically from the original contract, so you only need to make changes where something differs.

***

> **Note:** The Create Variation button is found in the **Actions** section of the contract sidebar, alongside other options such as Add Milestones, Replace Contract, and Download Contract.


---

# 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-variations.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.