Contract renewal alerting

The job is to fire an alert early enough to change the outcome, using the executed end date and the notice period in the signed file. The anniversary in a tracker, the date the CLM record was opened, and the date the first draft was circulated are not that clock.

Most auto-renew clauses bind on notice, not on expiry. If the MSA ends 30 June and requires 90 days of written notice, the last day you can still refuse the rollover is about 1 April. An alert on 1 June is a courtesy note that the contract already renewed.

Speed here is time to a decision, not time to a signature. The output is a recommendation brief on a named owner's desk: renew as-is, renegotiate, re-compete, or exit. It is not a renewal. It does not send a notice letter. It does not extend the term because nobody clicked.

CLM and source-to-pay suites such as Ironclad, Icertis, SAP Ariba, Coupa, and Zip are the usual home for the executed file and the obligation calendar. Treat them as one class of system of record. The model is a watcher and a drafter on top of that record, not a ranking of those products, and not a robot that renews.

Watch three fields, and only from the executed version.

Executed term

Start date and end date come from the signed PDF or the executed record, not from the shell that contract term pre-population filled while legal was still redlining. A draft start date is when sourcing began. Alerting from it will fire months early or, worse, months late relative to the real notice window.

If the executed file and the structured fields disagree, the file wins until a contracting owner recodes the fields. Do not "correct" a signed end date with a spreadsheet.

Notice period

Extract the notice required to prevent renewal or to terminate for convenience: 30, 60, 90 days, or a date certain. The alert date is end date minus that period, minus the working time your category owner actually needs to decide. A complex re-compete needs a longer lead than a commodity rollover. Set that buffer by category with the people who run those events, not with a single global "60 days."

Missing the notice window is the failure that looks like a process. You did run an alert. You ran it after the clause had already locked.

Auto-renew clauses

Record whether silence extends the term, for how long, at what price, and whether the extension is once or repeats. If the calendar is quiet, the clause still operates. A quiet calendar is not consent. Do not treat an unopened alert as approval to roll.

If the clause is not auto-renew, the opposite risk applies: you can still miss an expiry that takes a plant offline. Alert those too, with a different action list (extension, bridge, or exit), still as a recommendation.

A date alert without a file is a reminder. A date alert with the last term's evidence is a decision pack.

Attach, for this legal entity and this contract:

• Spend against the contracted rates and volumes, not a global vendor total.
• Delivery and quality from receipt quality scoring where goods are received, and from historical performance retrieval for the dispute, claim, and SLA file that never hit a goods receipt.
• Open risk events from supplier risk continuous monitoring so a filing, sanction, or ESG hit during the term is on the page, not in a separate mailbox.

A thin file is unknown, not a clean record. If you have two receipts and no SLA data, say so. Do not write "strong performer" because nothing was logged.

The recommendation line is one of four: renew, renegotiate, re-compete, or exit. State why in a sentence that a category lead can defend. Re-compete and consolidation ideas that outgrow a single contract belong on the rolling list in category opportunity identification. Do not file them as already-saved money.

The walkthrough is illustrative, not a measured result.

A category owner holds a national facilities cleaning MSA. The CLM record was opened on 1 May, when sourcing started. The executed agreement is dated 1 July, twelve-month term, end date 30 June the following year. Non-renewal requires 90 days of written notice. Silence auto-renews for another twelve months at the same rates. The notice deadline is 1 April.

If the watcher keys off the draft start date of 1 May, a "12-month" alert lands around 1 May. That is 30 days after the notice window closed. If the watcher keys only off the end date and fires 30 days prior, the alert lands in late May. Same miss. If the alert went to a shared procurement inbox in March and nobody owned it, the calendar looks quiet and the clause still rolls the MSA.

The useful alert fires off the executed end date minus 90 days, with a category buffer. In early February the named owner gets a brief:

• Executed term 1 July to 30 June, 90-day notice, auto-renew 12 months.
• Spend through the term, by site, against the contracted unit rates.
• Site coverage misses and two months where SLA credits were invoiced.
• No open risk event on the supplier.

The drafted recommendation is renegotiate (coverage and credits into the next term) or re-compete the two weak regions, not renew as-is, and not exit the whole MSA. The owner still chooses. Nothing is sent to the supplier until they do.

The three failures in one file: alerting on the draft start date, missing the notice window because the reminder was tied to expiry, and auto-renewing because the mailbox was quiet.

Route every alert to a named category or contracting owner, with a backup who is actually authorized to send notice. A shared inbox is how quiet calendars happen.

Give them the executed clauses, the performance and spend pack, the four-option recommendation, and a deadline that is still inside the notice window. They pick one option, or they send it back with a reason. Legal still owns the notice letter. Sourcing still owns a re-compete.

Do not auto-renew. Do not send a non-renewal notice because a score was red. Do not extend the term in Ironclad, Icertis, SAP Ariba, Coupa, or Zip because an SLA was green. Those systems store the executed file and can host the workflow. They are not ranked here, and they should not be wired to treat silence as a signature.

If metadata is missing (no notice period, no end date, draft dates only), stop and extract from the executed PDF before you trust the calendar. An early, wrong alert trains owners to ignore the queue. A late alert is how you discover, in May, that April was the deadline.

Tune lead time by category, then look at last year's renewals that actually rolled by silence. Those are the files the watcher has to catch next time. A brief that arrives inside the window, with evidence attached, is the speed you are buying.