Contract expiration tracking software built around the notice date, not the end date.

Contract expiration tracking is the practice of recording when each agreement ends, how much notice is required to get out of it, and what the contract does if nobody says anything - stops, rolls month to month, or renews for another full term. ExpiryEdge holds those fields on one record per contract, calculates the last date notice still counts, and alerts the named owner before it passes.

The end date is when the term stops. The act-by date is the end date minus the notice period, and it is the only one you can miss. A contract ending 31 March with a 60-day notice clause has an act-by date of 30 January. Write 31 March in a calendar and you will be two months late. ExpiryEdge ranks and alerts on the act-by date, and keeps the end date on the record for reference.

Anything with an end date that costs money or removes a right when it passes. In practice that is vendor MSAs, SaaS and enterprise software subscriptions, office and equipment leases, maintenance and service agreements, telecoms and utility contracts, insurance policies, fixed-term licences, framework agreements and SOWs, professional retainers, and data processing agreements tied to a parent contract. If nobody can say what happens on the day it expires, it belongs in the register.

Evergreen agreements never expire, so there is no date to put in a calendar - which is exactly why they get forgotten and why they quietly become some of the most expensive line items a business carries. Record the notice period and a review date instead. ExpiryEdge treats the review date as the act-by date and re-arms it on the cadence you choose, typically annually, so an open-ended contract still gets looked at on purpose.

Set it in months and ExpiryEdge counts calendar months back from the end date, which is what the contract usually means. Three months before 31 March is 31 December, not 90 days before. The difference is a couple of days, and a couple of days is enough to lose an exit window, so the record keeps the unit the contract used rather than converting it.

Not reliably, and not in B2B. The FTC amended its Negative Option Rule in October 2024 to tighten auto-renewal disclosure, but the 8th Circuit vacated that rule in July 2025 and it is back in rulemaking. The direction of travel is toward stricter disclosure. The practical position today is that the notice period written into your agreement is what binds you, so tracking it is the control that works regardless of where the rulemaking lands.

Start from accounts payable, not from the filing system. Pull recurring payments over the last 12 months, and every one of them has a contract behind it. Work down the list by annual value. An afternoon of this usually turns up agreements nobody remembered were still running. Upload each PDF against its record as you go, so the next person does not repeat the exercise.

Yes. When the owner marks a contract as cancelled or renegotiated, the date is stamped against the record along with who did it, and the notice letter or email can be attached. Every alert sent is logged too. If a supplier later argues notice arrived late, the sequence is one export rather than a week of reconstructing email threads.