Verified against ChatGPT · 2026-08-10
Build a renewal-and-notice-window tracker from a stack of contracts before an auto-renewal sneaks past you
Reads multiple contracts' renewal and termination-notice clauses and produces a single sorted tracker of upcoming deadlines with lead-time buffers, so nobody discovers an auto-renewal three days after the notice window already closed.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You're building a renewal and termination-notice tracker across several contracts, sorted by which deadline is coming up soonest, so nothing auto-renews or lapses by surprise. CONTRACTS AND THEIR RENEWAL CLAUSES Contract A: 2-year term ending Nov 30 2026, auto-renews unless written notice 90 days prior. Contract B: term end unclear, notice window not specified. TODAY'S DATE FOR CALCULATION 2026-08-14 HOW MUCH LEAD TIME YOUR TEAM NEEDS Two weeks internal buffer before the contractual notice deadline, to allow for approval routing. WHO SHOULD BE ALERTED FOR EACH Contract A owned by Procurement lead; Contract B owned by Legal ops. STEP 1 — EXTRACT THE RENEWAL MECHANICS PER CONTRACT For each contract, identify: the current term end date, whether it auto-renews or requires affirmative renewal, the length of the notice window required to prevent auto-renewal or to terminate, and who the notice must be given to and in what form if the contract specifies one (written notice, certified mail, a named contact). If any of these facts are missing from what I gave you, list the contract with "needs source document check" rather than guessing the term length or notice window. STEP 2 — CALCULATE THE ACTUAL ACTION DEADLINE For each contract with enough information, calculate the real internal deadline: the notice window's start date, minus your stated internal lead time, working backward from the term end date. Show your calculation, not just the final date, so it can be double-checked against the source contract. STEP 3 — SORT AND FLAG Sort every contract by action deadline, soonest first. Separately flag any contract where the action deadline has already passed relative to 2026-08-14 — this is the most important line in the whole output, since a passed deadline may mean an unwanted auto-renewal already locked in and needs immediate attention, not routine tracking. WHAT NOT TO DO Do not assume a default notice window (like 30 or 60 days) for any contract that doesn't state one — mark it unknown. Do not advise on whether it's actually worth terminating or renewing any given contract; this tracker is about deadline mechanics only, not a recommendation on the underlying business relationship. OUTPUT FORMAT A sorted table: Contract | Term End | Auto-Renew (Y/N) | Notice Window | Calculated Action Deadline | Alert Owner | Status flag (upcoming / URGENT-already-passed / needs-source-check). Then a short paragraph highlighting the single nearest deadline. Close with a line stating this tracker is a draft scheduling aid only, not legal advice, and that a qualified lawyer should verify the actual notice requirements and deadlines against the signed contracts before anyone relies on these dates.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Requiring GPT-5.1 to show the calculation rather than just the final deadline date exists because a language model computing backward from a term-end date through a notice window and an internal lead-time buffer is doing multi-step arithmetic on dates, a task where a fluent-sounding wrong answer is common and hard to spot without the intermediate steps shown — a visible calculation lets a human catch an off-by-one error in the notice window before it becomes a missed deadline, where a bare final date would hide the exact same error behind confident formatting. The flag for already-passed deadlines is placed as the single most emphasized output element because that's the one scenario where an auto-renewal may have already silently locked in, and a sorted list that treats a passed deadline the same visual weight as a comfortable future one buries the actual emergency inside routine housekeeping. The refusal to assume a default notice window like 30 or 60 days when the contract doesn't state one directly targets a plausible-completion failure mode: those are the two most common notice-window lengths in commercial contracts, so a model filling the gap with one of them will often just happen to be right, which is exactly what makes it dangerous — an occasionally-correct guess presented with the same confidence as a verified figure teaches the user to trust a number that was, this time, fabricated. Keeping the tracker to deadline mechanics only, with no opinion on whether renewing is a good idea, is what keeps this a scheduling tool instead of a business-advice tool, which matters because the consequence of getting the underlying renewal decision wrong is a business call for a human, while the consequence of getting the date math wrong is the kind of error this specific prompt structure is built to catch.
What you get back
URGENT — Contract B: action deadline needs source check, term end date unclear from input, cannot confirm status relative to 2026-08-14. Contract A: term end 2026-11-30, 90-day notice window starts 2026-09-01, minus 14-day internal buffer = action deadline 2026-08-18. Nearest deadline: Contract A in 4 days. This tracker is a draft scheduling aid only — a qualified lawyer should verify actual notice requirements against the signed contracts before anyone relies on these dates.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
