Renewal radar — 2026-09-14
Produced by: Run EXAMPLE-RNW-01 · read-only · document artifact · demo values
- Act now
- Stack Harbor Cloud's Order Form #SH-2024-118 has 2 days before its notice window shuts on 2026-09-16, so the decision is due 2026-09-14. The raw due date would have fallen before today, and a ticket born overdue sorts into the pile of things already failing — so it is shown as today instead of as a date behind you.
- Windows that already shut
- Cobalt CRM renewed on its own: the notice deadline was 2026-09-05, 9 days ago. It gets its own status and its own ticket the Monday it happens, with the clause quoted and the page named, rather than being reported as an ordinary row that needs nothing.
- Decide soon
- Helio Observability renews 2026-11-30 under a clause on page 7 reading “unless either party gives written notice of non-renewal at least sixty (60) days prior to the expiration of the then-current Subscription Term” — 60 days, which puts the last day for notice at 2026-10-01 and the decision at 2026-09-17. The deadline is the subtraction, not a date anybody typed into a column.
- Terms we could not read
- Kestrel Fasteners's Supply Agreement is signed, priced and plainly in force, and the document never says when the term ends. It is reported as no_renewal_date with no date at all, and its ticket is due today — the clock may already be running and nobody knows how much of it is left. Signature date plus twelve months would have looked right and been a guess.
- On the radar
- 2 agreements are further out than the 90-day horizon or inside it with nothing to do, so they are rows on the sheet and nothing else. 4 of the 6 agreements read this week needed a decision; filing work for the rest every Monday is how a radar turns into a queue nobody reads.
- What this does not show
- Aestus holds no accounts-payable ledger, no finance system and no CRM, so this reports no spend figure and no term-over-term drift. It reports the dates and terms the contracts themselves state, and nothing about what you actually paid. Contracts are files attached to one ticket: dragged in, dropped as an archive, or exported from wherever they are kept. No mailbox is read, and forwarding a renewal notice does not attach its PDF to a ticket today — upload the file. No calendar is read. A renewal date in a calendar is a date somebody typed, and that copy is the field that is wrong when a window gets missed — so the deadline here is derived from the clause in the contract and shown with the page it was read from. Nothing is ever sent to a vendor. No notice, no cancellation, no renewal and no negotiation. The decision becomes a ticket with a due date and a person acts on it.
- Sources
- One numbered row per contract file behind the lines above, each with the 1-based page a term was read from. A date with no quoted clause behind it is refused before the sheet is written, and so is a notice deadline that is not the renewal date minus the notice period.