Contract renewals with AI: tracking without a CLM

A watch list of renewals and notice periods can be built from the contract archive with an AI tool, without a contract lifecycle management (CLM) system. Money leaks through contracts that renew automatically because nobody gave notice in time, and through price increases nobody challenged. Here is how the list is built, what it can do, what it cannot do, and when it is time for a system.

Updated by Nils-Erik Jansson

What is tracked

The list has nine columns.

Column Content
End date The contract's end date
Notice period The notice period and the last day to give notice
Renewal terms Automatic renewal, and for what period
Price adjustment clause When and how the price is adjusted, and against which index
Owner Owner in the business
Counterparty The other party to the contract
Contract type Type of contract
Annual value The contract's annual value
Location Where the contract is kept

The programme for WorldCC's European summit in April 2026 shows that renewals and value leakage occupy contract professionals: renewals on autopilot and the move from project to operations were recurring themes [2]. The problem is the same for large companies and small departments.

How the list is built

Step one: gather the contracts. They sit in an archive, a folder, a document management system or in email. Connect the archive to the tool if a connector exists and the permissions have been reviewed. Otherwise, import a batch. Start with a limited number of contracts.

Step two: have the tool extract the nine columns for each contract into a table, with a page reference showing where in the contract each item appears. Anthropic has built artifacts for legal work in which every answer links to its source [1], and a watch list is one of the simplest to build: a table filled from the documents that can be sorted by the last day to give notice. In the setup it is built as an artifact from the contracts the team provides and then filled from the archive.

Step three: check. Every row with an amount or a deadline that matters is checked against the contract once. The check is what makes the list reliable. Scanned contracts with poor text and contracts with schedules get particular attention, because the tool is more likely to miss information there.

Step four: assign owners and reminders. Every row gets an owner in the business. Reminders go out ninety and thirty days before the last day to give notice, to the owner and to the legal department, through the calendar or whatever task tool the company uses.

What the list cannot do

The list does not catch:

  • oral changes, and changes agreed by email that never became a formal amendment
  • contracts that are not in the archive
  • schedules that change the main agreement's terms, when the schedule has not been read together with the agreement
  • price adjustment clauses that refer to an index the tool cannot calculate
  • new contracts that are not added after the list has been built

The last item is the job of the routine.

The routine

One review a month, thirty minutes: new contracts in, ended contracts out, and the next ninety days gone through with the owners. One person in the department owns the routine. The business receives the reminders and decides whether to renew or terminate. The legal department makes sure those decisions are taken in time and that notices are given correctly. Once a year, count what was terminated or renegotiated because of the list. That figure is what justifies the next step.

When it is time for a system

It is time when the business will create contracts from templates in volume, when contract data needs to go into the finance system, when the list has grown so large, with so many owners, that it can no longer be run by hand, or when tracking must cover obligations in the contracts as well as dates. Then it is a technology selection, and the CLM requirements checklist starts with exactly the figures the list has now given you: how many contracts, how many with renewal terms, how many owners.

The watch list as an artifact built from your contracts is part of step three of the setup of Claude for Legal. The routine around it, with owners and a monthly review, is part of the contract process design engagement under legal operations. If the list is not enough, the next step is a technology selection.

See also projects, skills, plugins and connectors in Claude.

Frequently asked questions

How reliable is a watch list built by an AI tool?
Reliable enough as a first version, but not as the final word. The tool reads dates, notice periods and renewal clauses well when the text is legible and the clause is clear. It misses scanned contracts with poor text, schedules that amend the main agreement, and anything agreed orally or by email. So a person checks every row with an amount or a deadline that matters against the contract, once.
Which contracts should go into the list?
Start with the ones that cost money: supplier agreements with automatic renewal, licences, leases and subscriptions, and the customer agreements where you have a notice period of your own to watch. Employment contracts and NDAs rarely have renewal deadlines that need tracking. Start with a limited number of contracts. All contracts is a project for later.
Can the business use the list itself?
Yes, and that is the point. The reminder about a notice period should go to the person who owns the contract in the business, and not only to the lawyer. The list is shared, every row has an owner, and the legal department owns the routine rather than every decision. That is also how the list stays current: the owner knows when the contract has been renegotiated.

Sources

  1. [1]Introducing artifacts for legal work, Anthropic, 28 October 2026
  2. [2]WorldCC EMEA Summit 2026, agenda, the sessions on renewals, value leakage and moving from project to operations

Back to Claude for Legal

More under Claude for Legal