TL;DR
A missed renewal is a data problem, not a reminder problem. The date lived in a PDF nobody queries, owned by nobody, with no consequence attached.
Stop treating it as a reminder problem. A missed renewal is a data problem wearing a calendar costume, and the reminder you are about to set will work for about four months.
Four conditions have to be true at once for a renewal to be missed, and every one of them is fixable.
Why do renewals actually get missed?
Because all four of these were true on the same day:
| # | Condition | Why it holds |
|---|---|---|
| 1 | The date lived in a document | It was a sentence in a PDF, not a field anything could query |
| 2 | Nobody owned it | The person who negotiated it changed role, and ownership was never a field either |
| 3 | The notice window was invisible | The renewal date was known; "90 days' written notice" was not extracted |
| 4 | Nothing broke when it passed | Auto-renewal is silent by design. The first signal is an invoice |
Condition 3 is the one that turns a near-miss into a miss. Teams track the renewal date and discover the notice window closed three months before it — so knowing the date was never enough.
And condition 4 is why this recurs. A missed delivery is loud. A renewal that quietly extends is indistinguishable from one you intended.
Why does setting a reminder not fix it?
Because a reminder inherits every one of the four conditions.
It is set by a person, from a date they read in a document, into a calendar nobody else sees, with no owner if that person leaves and no consequence if it is dismissed. You have mechanised the symptom.
Three specific ways reminders fail, and they are all ordinary:
- The date changes. An amendment moves it, the reminder does not move with it.
- The owner changes. The reminder fires into an inbox that is no longer read.
- It fires and is dismissed, because the person receiving it has no context and no authority to act.
A reminder is a note about data. The fix is to make it data — with an owner, a window, and something that visibly fails when it passes.
What does the date need in order to be reliable?
Four properties. A date with fewer than four is still a note:
- A typed field, queryable — so "what renews in the next ninety days" is a query rather than a reading exercise.
- The notice window, extracted separately. Renewal date minus notice period is the date that actually matters, and it is the one nobody stores.
- A named owner who exists as a record, not a memory.
- A consequence. Something visibly changes state when the window opens — a task, a flag, an exception on a report. A date that passes silently will pass silently again.
Extracting all four is what [obligation extraction](/blogs/what-is-obligation-extraction) is for, and a renewal is the simplest possible obligation — one party, one date, one action.
Where should the date actually live?
Wherever your team already looks daily — and in procurement that is usually the ERP, which already thinks in dates.
Microsoft's purchase agreement carries a validity period as a first-class property: "Each purchase agreement has a validity period that is defined by the person who creates the purchase agreement. The receipt date of a purchase must be within the effective dates of this validity period."
So the ERP is not storing the date — it is enforcing it. Orders outside the window do not qualify. And the agreement's own state is explicit: it must be activated by setting "Mark agreement as effective", and it can be closed to stop it being used.
That is what a renewal date with a consequence looks like, and it is already in the system. The gap is almost never the ERP's capability — it is that the date from the signed contract never got in there, which is the same drift that separates the document from the record.
What do you do, in order?
- List every agreement and its two dates — renewal, and notice deadline. This is the whole exercise. Most teams discover at this step that they cannot produce the list, which is the finding.
- Assign an owner per agreement, as a field.
- Put the notice deadline where work already happens — the ERP if it prices orders, the calendar of a named person if not.
- Give it a consequence — a task that appears, an exception that reports.
- Then consider extraction to keep the list current as contracts are amended.
Steps 1 and 2 prevent most repeat misses and need no software. Step 5 is what stops the list decaying, and it is the only step where a system is genuinely required.
About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/
Legal AI Ops. We transform legal workflows with agentic AI, copilots, agentic workflows and decision intelligence — built into core workflows rather than beside them, to raise productivity and cut operational overhead. Contract Review Copilot is the contract-review app in that family. It ships as Paralegent AI, in production today. How we build Legal AI Ops — custom AI capabilities on top of legal work, against your playbook and your Dynamics 365.
Bring the agreement you missed to a 15-minute call and we will trace which of the four conditions was true — it is usually the notice window, and it is usually still true for the rest of your contracts.
Sources
Sources and fact-check
| # | § | Claim | Tier | Source | Verdict |
|---|---|---|---|---|---|
| 1 | 1 | The four conditions for a missed renewal | T2 — ours, a diagnostic framework stated as ours | Internal definition | PASS |
| 2 | 1 | Auto-renewal is silent; the first signal is often an invoice | T2 — ours, an observation, unquantified and not attached to a client | Internal definition | PASS |
| 3 | 2 | Three ways reminders fail | T2 — ours | Internal definition | PASS |
| 4 | 3 | The four properties of a reliable date | T2 — ours | Internal definition; profile §11 | PASS |
| 5 | 4 | The validity-period passage, quoted whole | T1 — verbatim | purchase-agreements (ms.date 2026-09-08), fetched 2026-09-10 | PASS — load-bearing |
| 6 | 4 | Activation via Mark agreement as effective; closing stops use | T1 — verbatim | Same page, opening section | PASS |
| 7 | 4 | The gap is that the contract's date never reached the ERP | T2 — ours, an argument, not a claim about any customer | Internal definition | PASS |
| 8 | 5 | The five-step order, two of which need no software | T2 — ours | Internal definition | PASS |
Tier summary: 2 × T1 (both verbatim), 6 × T2 — 0 × T4.
No figures. No count of missed renewals, no value, no percentage, no customer. "Four months" in the opening is rhetorical and attached to nobody. The one number in the article — "90 days' written notice" — is an illustration of a notice window, not a claim about anyone's contract.
Disclosure: §5 states that steps 1 and 2 prevent most repeat misses and need no software.
