> 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/june/applicant-milestone-submission.md).

# Applicant/Verifier Milestone Submission

Allows applicants and verifiers to create and submit milestones themselves, directly from the Milestones index page, without requiring an admin to create and assign them first.

## Problem

Previously, milestones could only be created by admins. Applicants and verifiers had no way to initiate a milestone themselves — they had to wait for an admin to set one up and publish it to their account. Additionally, both roles sometimes need to create milestones that are not tied to a specific application (e.g. compliance or reporting milestones linked to a contact).

## How It Works

### Organisation Settings

Two toggles are available in the **Milestone Settings** section of the organisation's settings page:

* **Applicant Milestone Submission** — enables the feature for applicants.
* **Verifier Milestone Creation** — enables the feature for verifiers.

### Milestone Template Configuration

When the corresponding org setting is enabled, each Milestone Template gains new options:

* **Allow applicants to submit this milestone** / **Allow verifiers to create this milestone** — marks the template as available for that role's milestone creation. Only templates with the relevant checkbox will appear.
* **Applicants can set the amount when creating** / **Verifiers can set the amount when creating** — when checked, the user will be prompted to enter a funding amount when creating. If unchecked, the amount is taken directly from the template.

### Creation Workflow (Applicant and Verifier)

When at least one eligible template exists, a **"+ Create New Milestone"** button appears at the top of the Milestones index page. Clicking it opens a modal with:

1. **Milestone Type** — a dropdown listing only the templates marked for the user's role.
2. **Application** — a searchable dropdown to select which application the milestone is for (optional for verifiers).
3. **Contract** *(optional, shown only if the selected application has contracts)* — lets the user associate the milestone with a specific contract.
4. **Amount** *(shown only if the template allows it)* — a numeric field for the user to specify the funding amount.

If a funding application is selected, the milestone is created as an `application` type (or `contract` type if a contract is also selected), linked to that application.

If no funding application is selected, the milestone is created as a `registration_entity` type (a "contact milestone") linked directly to the user's registration entity.

The **Continue to Deliverables** button is disabled until the required fields are filled. On submit, the milestone is created from the template and the user is taken directly to the deliverables completion page to fill in and submit it.

### Duplicate Warnings

If a milestone already exists for the same template (and same application, or no application), a warning is displayed with links to the existing milestones so the user can complete those instead of creating duplicates.
