Free Contract Renewal
Tracking Template

Most contract trackers have a renewal date column and stop there. That is the date the contract rolls over — the outcome, not the decision point. The date that constrains you is the notice deadline: the last day you can tell a vendor you are leaving or renegotiating before the renewal happens on its current terms.

A contract renewing on 15 March with a 60-day notice period has a notice deadline of 14 January. If your reminder is set for the renewal date, it arrives two months after your leverage expired. You are not negotiating at that point; you are asking for a concession.

So this sheet calculates that date rather than asking you to work it out. Enter the renewal date and the notice period in days, and the notice deadline column derives itself. It stays correct when a renewal date is corrected, which a typed date does not.

Start from payment records, not memory. Pull twelve months of recurring charges from your bank and card statements, then add anything invoiced annually from accounts payable. Payment data is the only source that reliably surfaces subscriptions nobody remembers signing up for, which are exactly the rows worth having.

For each vendor, open the contract and find three things: the renewal or end date, the notice period, and whether it auto-renews. Those three fields do most of the work. If you can only get two, take the renewal date and the notice period — they are what produce the deadline.

Fill in an owner for every row while you are there, and use a person's name rather than a department. Shared responsibility reliably becomes nobody's, and the gap only shows up when a renewal is three weeks out and the person who used to handle it has left.

Do not try to complete the whole portfolio in one sitting. Enter the contracts renewing in the next six months first, because those are the only rows that can hurt you this quarter, then fill in the rest as they surface.

A tracker decays. Contracts get renegotiated, dates move, and the sheet quietly stops describing reality — the failure is invisible, because a stale sheet looks exactly like a current one. Thirty minutes a month is enough to prevent it if the thirty minutes actually happen.

Sort by notice deadline, ascending, and look at everything inside 90 days. For each of those rows, ask whether a decision is needed, whether the owner knows, and whether anything about the contract has changed since it was entered. Update the status column as you go.

Then scan for gaps: rows with no owner, no notice period, or a status nobody has touched in six months. Those are the contracts most likely to slip, precisely because nothing about them is being maintained.

A spreadsheet has one structural weakness, and it is not capacity: it cannot tell you anything. It sits there being correct until somebody opens it. Every reminder in this system depends on a human remembering to look, on a schedule, forever.

That works while one diligent person owns it and the portfolio is small. It starts failing when contracts arrive from several directions at once, when more than a couple of people need answers from it, or when the person maintaining it goes on holiday during a notice window. The honest test is not a count at all. It is whether anything has already been missed, whether next quarter's deadlines would still reach someone if the maintainer left tomorrow, and — the question worth asking first — what your largest single commitment is and what missing its notice window would cost.

None of that is an argument for buying software today. It is an argument for knowing which failure you are exposed to, so that when a deadline does slip you treat it as a signal rather than bad luck.