How to track contract renewal dates with an AI agent

What matters is the notice deadline, not the renewal date. Many contracts renew automatically unless you give notice months ahead, in a set form. The agent extracts those terms from every signed contract and amendment, computes each deadline, alerts the owner well before it, and drafts the notice. The owner decides; legal or procurement sends the notice.

What does renewal tracking involve, and who owns it?

Supplier contracts for software, facilities, equipment leases, outsourced services and subscriptions often renew on their own. Missing a notice deadline can lock you into another full term, sometimes at a higher price. The terms that matter are spread across the contract: the initial term, the renewal term, the notice period, how notice must be given, price changes on renewal and any termination for convenience.

Each contract should have a business owner who decides whether it continues. Procurement owns the contract register. Legal owns notices and their form. Finance cares because renewals are commitments that should be in the forecast. In many organisations nobody owns the dates, which is why they are missed.

What are the steps, and at what depth?

1. Agent, depth 1: builds the register. Reads every signed contract and amendment in the repository, extracts parties, owner, initial term, renewal mechanism, notice period, notice method and address, price change on renewal and termination rights.
2. Person, procurement: confirms the register. Especially for contracts where the agent marked terms as unclear.
3. Agent, depth 1: computes deadlines. The last day notice can be given, counting from the right date under the contract's own rules: expiry date, anniversary, or end of a notice month, and allowing for business days where the contract says so.
4. Agent, depth 2 or 3: alerts the owner. At set intervals before the deadline, such as ninety, sixty and thirty days, with the contract summary, current annual cost and price change on renewal. Standard alerts can go at depth 3 once certified.
5. Person, owner: decides. Renew, renegotiate or terminate, and records the decision.
6. Agent, depth 2: drafts the notice. For terminations or renegotiation, in the form and to the address the contract requires.
7. Person, legal or procurement: sends the notice. And keeps proof of delivery.
8. Agent, depth 1: updates the register. New dates after renewal, closed status after termination, and the evidence of notice.

What stays with a person, and what evidence does each control leave?

The decision to renew is a business decision; sending a notice is a legal act with consequences. Both stay with people. The agent's job is to make sure no deadline passes without a decision. It never sends a termination notice and never agrees a renewal; whether an agent can sign a contract at all is a separate question with a clear answer.

Signed versions only. Evidence: signature status for each document in the register.

Deadline calculation shown. Evidence: the clause, the dates and the arithmetic for each deadline.

Alert acknowledged. The owner acknowledges each alert; unacknowledged alerts escalate to their manager. Evidence: acknowledgement records.

Decision recorded. Evidence: the owner's decision with date.

Proof of notice. Evidence: the notice sent and proof of delivery, stored with the contract.

What does a deadline look like for one contract?

Take an illustrative facilities services contract with an initial term ending on 31 December, renewing automatically for two years unless either party gives at least six months' written notice by recorded delivery to the supplier's registered office. The agent computes the deadline as 30 June, sends alerts in April, May and early June, and notes that email notice is not valid under the contract. The owner decides to retender; legal sends the notice by recorded delivery on 10 June and files the proof.

What should you measure?

• Contracts in the register against contracts in the repository.
• Deadlines missed. Should be zero.
• Alerts acknowledged on time.
• Renewals with a recorded decision, against all renewals.
• Savings from contracts renegotiated or ended at renewal.

Where does it usually go wrong?

Contracts outside the repository. A manager signed a subscription online with a click-through. The agent cannot track what it cannot see. Compare supplier spend with the register to find contracts nobody filed.

Amendments change the dates. An extension letter moves the expiry; the register still shows the old date. Every amendment triggers a re-read.

Notice in the wrong form. Notice by email when the contract requires post, or to the account manager rather than the registered office. The agent should include the method and address in every alert.

Owners who have left. Alerts go to someone no longer at the company. The agent should check owners against the staff directory and escalate orphaned contracts.

Renewals not reviewed before signature. Renegotiated renewals are new contracts; review supplier contract terms before signature applies to them too.

The agent's own authority also expires: certificates lapse after 90 days, and a certificate renewal checklist for AI agents keeps that from being missed in the same way.

Where Pryme fits

In Pryme, extracting terms, computing deadlines and alerting owners are separate capabilities, each certified on your own contract repository. Signed contracts arrive as signed sources and owners' decisions as declared, so the register shows what rests on the contract and what on a person's word. Sending notices sits outside the agent's role scope. The finance bounds are in AI agents for finance.