How it works
Each contract has a lifecycle: scheduled, open-ended or event-driven, with renewal rules such as auto-renew or optional extension, the renewal term length, the maximum number of renewals, the renewal notice and any early termination schedule. These values are extracted from the contract and can be checked against the source text.
From them, Formality calculates the expiration date and the next date by which notice must be given. If the calculated expiry differs from the one entered, it suggests the correct date.
The contract shows a clear status, such as Renewing soon with the days left to cancel, or Expiring soon. Reminders and renewal workflows can then be based on these dates.
What you get
- Scheduled terms, renewals and expiry
- Last day to give notice
- Auto-renewal and optional extension
- Linked to the source clause
Why teams use it
You know the last day to cancel a tacitly renewed contract.
Optional extensions, renewal caps and early termination are part of the calculation.
Each value links back to the clause it comes from.
Contracts renewing or expiring soon are flagged in the repository.
Reminders and renewal workflows start from the calculated dates.
More in Deadlines & obligations
Contract durations
Initial term, renewal terms and maximum duration.
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 →