When teams set out to track contract expiration dates, they usually add one column called Expiry or Renewal and put a calendar reminder a few weeks before it. That works for agreements that simply end. For agreements that renew unless someone gives notice, it tends to go wrong in a quiet way: the reminder arrives after the last day to act.
Good contract tracking separates four dates that often get merged into one. This guide defines each of them, shows the difference with the fictional Northline Studio sample, and sets out a short routine a small team can run every month.
1. Four dates, not one
These are the working definitions used in this guide and in Agreedio. Your agreements may use other words for them, which is exactly why the column name alone is not enough.
| Date | What it means |
|---|---|
| Expiry | The date a fixed-term agreement ends with no renewal |
| Term end | The end of the current term, which may renew if nobody acts |
| Latest notice date | The last date produced by the confirmed notice rule |
| Internal reminder | When your own team is prompted to prepare, well before that |
2. Why the expiry date is often the wrong alarm
Take the fictional Alder Works retainer. The term ends on 30 September 2027. After Amendment A1, notice not to renew must be given at least 90 calendar days before the term ends. 30 September 2027 minus 90 calendar days is 2 July 2027.
A reminder set 30 days before the term end would arrive on 31 August 2027, nearly two months after the latest notice date. The date column was right; the alarm was set against the wrong date.
Agreements that genuinely expire still need a date to watch, just a different one. The fictional Ines Baró contractor agreement in the sample ends on 31 March 2027 with no renewal. The useful reminder there is ahead of the expiry, with enough time to decide whether to extend the work or plan the handover. That row is also a manual entry: typed in by hand rather than taken from a source document, and labelled that way so nobody mistakes it for a confirmed term.
The sample also shows an honest gap: its auto-renewal field is marked missing source, because neither SOW-S1 nor Amendment A1 contains a clause that states it. That is worth showing rather than assuming. If you do not know whether an agreement renews, treat the notice date as the one to watch until someone has reviewed the wording.
3. Record the rule, not only the date
A date in a cell tells you what someone calculated once. The rule tells you how to calculate it again when something changes. Record the notice wording as quoted, the number and unit, and the convention used.
Agreedio uses calendar-day arithmetic with no silent business-day or weekend adjustment. Under the original 60-day rule the Alder Works result was 1 August 2027, a Sunday, and it stays a Sunday. If a real clause refers to business days, receipt, holidays or a notice method, review it rather than shifting the date. Months and days are different rules too: two months is not 60 days.
4. Set reminders from the notice date, with time to decide
The reminder is for the decision, not the deadline. Work backwards from the latest notice date and leave enough time to review usage, talk to the counterparty and get approval. In the sample, reminders run at 60, 30, 14, 7 and 1 days before 2 July 2027: 3 May, 2 June, 18 June, 25 June and 1 July 2027.
These are internal reminders. They prompt your owner to act; they do not notify the other party, and marking one done does not mean notice was given. When an amendment changes the rule, pending reminders under the old rule should be replaced, not left running alongside the new ones.
5. A monthly routine to track contract expiration dates
Contract tracking fails more often from drift than from a single mistake. A short routine on the same day each month keeps the dates trustworthy.
- Add any agreement signed in the past month, with its source, owner, term end and notice rule.
- Log any amendments or renewal order forms and check which dates they change.
- Look 120 days ahead by latest notice date, not by term end.
- Confirm each upcoming row has an owner who is still here and knows it is theirs.
- Resolve rows marked needs review or missing source, nearest date first.
- Record decisions: renew, renegotiate or give notice, and when and how notice was sent.
- Move ended agreements out of the live view, but keep them.
6. After the date: record what happened
If the decision is not to renew, a person sends the notice using the method the agreement requires and keeps evidence that it was sent. Record that on the agreement. If the agreement renews, update the term end and recalculate the next latest notice date from the confirmed rule, so next year's reminders are set from the right date.
Where Agreedio fits
For a handful of stable agreements, a spreadsheet and the free notice-date calculator may be all you need. Agreedio keeps the four dates apart for every agreement: it suggests the term end and notice wording from the signed document, holds them as suggestions until a person confirms them against the source, calculates the latest notice date with the arithmetic shown, and sends internal reminders to a named owner. Failed reminders stay visible, and confirmed reminders keep running on deterministic logic even when the AI allowance is used up.
What this guide does not cover
This guide is not legal advice. It does not interpret notice clauses, decide whether a notice is valid or cover business-day, holiday, receipt or time-zone rules. It explains how to keep the dates apart and how to run a tracking routine.
Examples on this page use a fictional sample workspace. Nothing here is legal advice; obtain qualified advice for your own agreements.