> 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/product-news/2026/august/contract-title-personalisation-on-milestone-emails.md).

# Contract Title personalisation on Milestone emails

## Problem it solves

Applicants often hold several contracts with the same organisation at once. When they received a "Milestones created" or "Milestone request for resubmission" email there was no way for the organisation to say *which* contract the milestones belonged to — the only personalisations available were the applicant name, the application title and the milestone title. Recipients had to sign in and guess from the milestone list which agreement the email referred to.

The **Contract Title** personalisation was already available on the contract emails and the milestone reminder email, but not on these two, so organisations could not word them consistently with the rest of their milestone correspondence.

## How it works

**Contract Title** is now offered in the Personalisation menu when editing either of these emails under **Settings → Emails**:

* **Milestones created** (sent to the applicant when milestones are published)
* **Milestone request for resubmission** (sent to the applicant when a milestone is declined and resubmission is requested)

Inserting it places the `[[contract_title]]` token into the subject or body; at send time it is replaced with the title of the contract the milestone belongs to.

For **Milestone request for resubmission** the value comes from the declined milestone's contract, falling back to the contract on its funding application.

For **Milestones created** — which can cover several milestones in one email — the value comes from the contract those milestones belong to, again falling back to the contract on the funding application.

If the milestones are not attached to a contract at all (an application-only milestone), the token resolves to an empty string, exactly as the other optional personalisations do. Organisations that mix contract and non-contract milestones should word the sentence so it still reads correctly when the title is blank.

The default wording of both emails is unchanged — existing customised content is untouched, and organisations opt in by adding the token themselves.

## UI changes

* **Settings → Emails → Milestones created**: **Contract Title** added to the Personalisation menu.
* **Settings → Emails → Milestone request for resubmission**: **Contract Title** added to the Personalisation menu.