Open Compliance and add an obligation. Choose its type (seeded by your pack), give it an expiry date, and attach it to an asset — or leave the asset empty for something that belongs to the organisation or a site, such as a premises permit or a floating software licence.
The three clocks
- Expiry — the day it runs out. Always required.
- Cancellation notice — for anything that renews automatically. Set the number of days' notice the contract requires, and you are alerted before the last day you can still cancel.
- Renewal lead — how many days the renewal takes to arrange. You are alerted on the day you have to start, not the day it is too late.
Each clock alerts independently, and each alert says which clock it is about.
Everything else
Issuer, reference number, seats, cost, owner, notes and custom fields are optional. Link an obligation to the compliance frameworks it satisfies and it will count towards the framework coverage report.
Dates are dates
An expiry is a calendar date in the organisation's timezone, not a moment in time. Something that expires on 31 March expires on the 31st, wherever the person reading the alert happens to be.