Adding Milestones to a Live Contract
You've made a Contract live and realised more Milestones are needed. You can still add them, but they won't appear on the signed Contract document unless you create a Variation. This explains both opt
Short answer: you can add Milestones to a Contract that's already live, and they will track and appear on the Applicant's Dashboard as normal. What you can't do is make them appear on the signed Contract document — that document is fixed. If the new Milestones need to form part of the agreement, you'll need a Contract Variation.
Why the Contract document doesn't update
A Contract document is generated once, at the point the Contract is signed, and saved as a snapshot. It's a record of exactly what both parties agreed to at that moment, which is what makes it binding as at that date. It is never regenerated afterwards.
That's why the Add Milestones flow has no option to push a Milestone into an existing Contract document — allowing it would change an agreement that has already been signed.
This is the same reason reordering Milestones after signing doesn't change the order shown on the document.
Option 1: Add the Milestones to the Contract via a Variation
Use this if the new Milestones need to be contractually binding.
Open the original Contract.
In the Actions section of the sidebar, click Create Variation.
Work through the wizard. At the Milestones step, add the new Milestones — via Create Milestone, Import Template, or Link Milestones (see Which option should I use? below).
Complete the remaining steps and send the Variation out for signing.
The Variation produces a brand new Contract document containing the new Milestones, signed by both parties in its own right. The original Contract and its document stay exactly as they were.
Create Variation only appears on an original Contract, and only once that Contract is fully executed (Contract Signed by Admin). It is not offered on a Variation — a Variation can't be varied further. If you need to change a Variation, create another Variation against the original Contract.
Option 2: Add the Milestones without changing the Contract
Use this if the new Milestones are operational rather than contractual, and a Variation would be overkill.
Create the Milestones and assign them to the other party as you normally would. They won't appear on the Contract document, but they will show on the Applicant's Dashboard and can be completed, submitted and reviewed exactly like any other Milestone.
Because nothing in the signed Contract mentions them, it's worth letting the other party know the new Milestones are there and are expected to be completed — otherwise they'll simply appear on the Dashboard without explanation.
Which option should I use?
The Contract's Add Milestones flow offers three routes, and they behave differently:
Create Milestone — builds a new Milestone from scratch, tied to this Contract.
Import Template — pulls from your saved Milestone Templates only. It will not list a Milestone you've already created via Create Singular Milestone or Create Milestone Batch. If you built the Milestones elsewhere and can't find them here, this is why.
Link Milestones — the only route that surfaces existing, not-yet-linked Application Milestones for that Funding Application, so you can attach one without recreating it.
Link Milestones only appears when the Contract is against a Funding Application and that Application has existing, unlinked Milestones. If the Contract is against a Registration Entity (an Applicant-level Contract rather than an Application-level one), there is currently no way to pull in a pre-existing Milestone — use Create Milestone or Import Template instead.
See also
Last updated
Was this helpful?