Contract renewal dates missed: how to track them so none slip

Short answer: renewals slip when the dates live in the contracts and not in a tracker. Put every contract in one list with the renewal date, the notice deadline, the owner and the cost. Then set alerts well before the notice deadline, not the renewal date. The notice deadline is the date that costs you money.

At a glance

Swipe sideways to see all columns.

Item	Number	What it means for you
List view threshold	5,000 items	A renewal list will not reach this soon. If it does, filter the view to renewals due in the next 90 days.
File attached to a list item	250 MB	Keep the signed contract in a document library and link it on the renewal row.
Flow that keeps failing	14 days	A reminder flow that fails every run is turned off after 14 days. Check run history after a fix.
Flow with no trigger activity	90 days	A reminder flow that never fires for 90 days might be turned off. Microsoft warns the owner 30 days before.

Why renewals get missed

A contract is signed once and filed. The person who signed it may move to a new job. The renewal date sits on page nine. A year later the vendor sends an invoice, and the contract has renewed for another year.

Typical causes:

The date is only inside the PDF.
The notice deadline is not written down anywhere. The contract sets how many days of notice you must give before the end date. Find that number in each one.
No owner is named for the contract after it is signed.
Contracts are kept in different places: email, a shared drive, a desk drawer, a vendor portal.
The reminder is in one person's calendar. When that person leaves, the reminder leaves too.

The two dates that matter

Every contract has at least two dates:

The end or renewal date: when the term ends or renews.
The notice deadline: the last day to say you want to cancel, change or renegotiate.

The second date is the one people miss. If the contract says "renews automatically unless cancelled 60 days before the end date," your real deadline is 60 days before the end. Track that date, and alert on it.

Step 1. Collect every contract in one pass

Make a list of all contracts and where each one lives. Check these places:

The shared drive and email folders.
Accounts payable: every vendor that bills you regularly is a hint.
Each team lead: ask what they signed.
Software accounts, leases, carrier and 3PL agreements, service agreements, insurance and memberships.

You will not find every contract in the first pass. That is fine. Add new ones as they appear.

Step 2. Open each contract and record the facts

For each contract, write down:

Vendor or party name.
What it covers, in a few words.
Start date and end date.
Does it renew automatically? (Yes or No)
Notice period, in days.
Notice deadline (end date minus the notice period).
Cost per term and billing frequency.
Owner: the one person who decides on renewal.
Link to the contract file.

Do this once. It is slow the first time. After that, adding a contract is a few minutes.

Step 3. Build one tracker

A SharePoint list fits well. Make one row per contract, with a column for each fact above. Add a Status column (Active, Under review, Renewing, Cancelling, Ended). Add a calculated column for the notice deadline so it updates when dates change.

If you now keep this in a spreadsheet, that can work for a small number of contracts. Once several people need to update it, or you want automatic alerts, a list is a better home. See "Replace a spreadsheet tracker with a SharePoint list" for how to move the data.

Step 4. Set alerts before the notice deadline

Alert on the notice deadline, with more than one warning. One way to start, counting back from the notice deadline:

120 days before: owner starts review.
60 days before: owner confirms keep, change or cancel.
30 days before: second warning to the owner and their manager.

Adjust these for each contract's notice period. A flow in Power Automate can run each morning, find contracts whose deadline falls on those days and message the owner. Send a single summary and not one message per contract. For the setup pattern, see "Late tasks nobody notices: setting up late alerts."

Step 5. Hold a short renewal review

For each upcoming renewal, the owner answers four questions:

Do we still use this?
Is the price fair compared to other options?
Do the terms still fit how we work?
Should we negotiate, switch or cancel?

Record the answer in the tracker and set the Status. This is the point where you save money. Before the deadline you can still cancel, so you have room to negotiate. After it, you usually do not.

Step 6. Name a backup owner

Add a Backup Owner column. If the owner leaves, changes teams or is on leave, the alert goes to the backup too. Check the owner list every quarter.

Step 7. Review the whole list on a schedule

Once a quarter, sort the list by notice deadline and look at the next six months with the team lead. This catches contracts that were missed in the first pass and fixes wrong dates.

Honest limits

A tracker is only as good as the dates in it. If someone enters a wrong notice period, the alert will fire at the wrong time. Check each entry against the contract when you add it. Also, this guide covers tracking and not legal advice. If a contract is large or unclear, ask your lawyer to read the renewal and notice terms. Flows can also be turned off by Microsoft if they do not run for a long time, so check yours after any change.

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Updated 2026-10-27.

What is the most important date to track?

The notice deadline. The end date tells you when the contract ends. The notice deadline tells you when you must act, and it comes first.

How early should alerts go out?

Send the first alert well before the notice period starts, so there is time to review and negotiate. One way to start is 120, 60 and 30 days before the notice deadline.

Where should the contract files be stored?

In one shared library with limited edit access. Put a link to each file in the tracker row so the owner can open it in one click.

Do I need special software?

Not to start. A shared list with the right columns and a daily alert flow covers most small and mid-size teams. Dedicated contract software makes sense when you manage many hundreds of contracts.