How it works
The lifecycle type says whether the contract has a scheduled end, is open-ended, or ends on an event. For scheduled contracts, the effective date, the initial term, the renewal type and the renewal term are recorded, along with any cap on the number of renewals.
These values are extracted from the contract and linked to the clause they come from. A 20-year operating concession with two optional 5-year extensions, or a 3-year telecom framework that renews each year, are both described this way.
From the lifecycle, Formality calculates the expiration date and suggests a correction when the date entered does not match.
What you get
- Scheduled, open-ended or event-driven
- Initial term and renewal terms
- Maximum number of renewals
- Suggested expiration date
Why teams use it
Concessions and multi-year frameworks show their full possible duration.
The calculated expiry is compared with the date entered.
Each duration links back to its clause.
Durations are fields you can filter and export across the repository.
More in Deadlines & obligations
Notice periods and renewals
Renewal and notice dates calculated from the contract.
Learn more →Reminders
Reminders before or after each key date.
Learn more →Reminder templates
Apply the same reminders to every contract of a category.
Learn more →Upcoming and late tasks
A list of what is late and what is coming.
Learn more →