> 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/milestones/manage-milestones/milestone-ordering.md).

# Milestone Ordering

Milestone order can be changed at any time, but **when** you reorder determines how it appears to the applicant.

### Before a contract or variation is published

If you reorder milestones before a contract or contract variation is published, the new order will be captured in the contract snapshot. The applicant will see milestones in the order you set.

### After a contract or variation has been published

If you reorder milestones after a contract or variation has already been published, the published contract document will *not* reflect the new order — it stays as it was when snapshotted. However, the applicant will see the updated order when they view their Contract Milestones.

### How to reorder milestones

Open the **Milestones** tab on the contract, then use the **View** dropdown on any milestone row to access the ordering options:

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


---

# 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/milestones/manage-milestones/milestone-ordering.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.