> 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/upcoming-registration-and-contract-changes.md).

# Coming Soon: Registration and Contract Management Improvements

We're getting ready to release two sets of improvements: a tidier admin experience for managing registrations, and a more flexible contracts workflow. That workflow lets you use Tahua to manage contracts with anyone, not only funding applicants. Here's an early look at what's coming.

## Registrations: a simpler admin experience

The registration page has been reorganised so everything about a registration and its people is in one place.

### People are now on the registration page

The separate **Users** tab has been replaced by a **Users** panel on the registration's main page. From the panel you can:

* see everyone linked to the registration at a glance
* add a user
* accept a pending invitation
* remove a user from the registration

The remove option depends on the user's role, so you only see the options that apply.

### One Actions panel

The registration's details and actions have been combined into a single **Actions** panel. The page layout now matches the user profile page, so moving between a person and their registration feels consistent.

### One list for applicants, assessors and verifiers

**Users > Registrations** now brings applicants, assessors and verifiers (e.g. institutions) together in one list, with filters for each. Columns that only apply to applicants, such as status and review status, are hidden when you view **All**.

Verifiers can also be bulk-imported using the same CSV template as applicants.

### Safer transfers and deletes

* **Transfer Records** now moves an applicant's access to funding rounds as well, such as private round invitations. It also shows any **live** funding rounds the applicant is part of before you confirm.
* **Delete** also warns you when the applicant is part of a live funding round. If they're a duplicate, it suggests transferring their records first.
* Tahua now stops you creating a second Individual registration for the same person when adding or granting roles.

### Small naming change

**Settings > Registrations** is being renamed **Settings > Registration Types**, to make it clearer what's managed there.

## Contracts: manage contracts with any counterparty

Contracts in Tahua no longer need to start from a funding application. These changes let you use the contracts module as a general contract management system, for funded projects and for your other agreements.

### Linking an application is now optional

When you create a contract, you choose the **counterparty**: the organisation or person the contract is with. Linking an application is now **optional**:

* **If you link an application,** the counterparty and its details and milestones are pulled through, as they are today.
* **If you don't,** you can select an existing counterparty, or invite a new one, directly from the contract.

Across contracts, milestones and payments, the wording now says **counterparty** instead of "applicant". In contract templates, the **Applicant Signature Block** personalisation is now called the **Counterparty Signature Block**.

### Contracts with institutions, without the extra step

You can choose a verifier (e.g. an institution) as the counterparty directly, so you no longer need to tick **"This Contract is with the Institution only"** when setting up the contract.

### Organisation-supplied milestones

Contracts often include things *your* organisation owes the counterparty, such as reports, resources, training or payments due back to you. With the new **Enable organisation-supplied milestones** setting, each milestone can be marked as supplied by:

* **Counterparty** (default), completed by the counterparty in their portal, as today
* **Your organisation**, completed and submitted by your admins, and reviewed using the usual milestone review process

Milestones supplied by your organisation never appear in the counterparty's portal, and the counterparty isn't notified about them. Payments on these milestones are tracked as **incoming**, money owed to you. They aren't synced to your accounting system as bills, and they're excluded from bank payment files. They show a **Supplied by us** label in the admin milestones list.

### Contract expiry reminders

A new **Contract Expiry** email reminder, under **Settings > Emails > Email Reminders**, warns you before a contract ends:

* **Recipients:** send it to the contract's **Contract Manager** or to all **Admins**.
* **Timing:** choose how many days, weeks or months before the contract end date it's sent.
* **Categories:** optionally limit it to particular contract categories.

Each reminder is sent once per contract. If a contract has a variation, the variation's end date is used. The email can be fully edited, with personalisations such as the contract title, counterparty name, contract manager and days remaining.

### Contracts-only setups

For organisations that use Tahua mainly for contract management, the applications and assessments areas can now be switched off. Menus, lists, reports and settings then only show what's relevant. Talk to us if this would suit your organisation.

## When can I use these?

These improvements are being tested now and will be released soon. We'll let you know when they're live and update the relevant help articles. If you'd like a walkthrough or have questions in the meantime, get in touch with our support team.