The prompt
Score 10 of 10, Excellent
Use it when You have several supplier or customer contracts and need every renewal, notice and price-change date in one list, so none rolls over by surprise.
- {{audience}}
- {{contract_extracts}}
- {{today}}
- {{lead_time}}
Full prompt and why it works
Prompt
Build a renewal and notice calendar from the contract extracts below, for {{audience}}, who will set reminders from it. The goal is that no contract renews, expires or changes price without someone deciding in time, so the dates and the notice needed to act on them matter most. Contract extracts (for each contract: name, other party, start date, term, and the renewal, notice and price change clauses with their numbers): """ {{contract_extracts}} """ Today's date: {{today}} How far ahead of each deadline we want a reminder: {{lead_time}} Produce: 1. Next 90 days: contracts needing a decision soon, as a short list. Include any contract where a missing date means a deadline could already have passed or could fall in this window. 2. Calendar: a table sorted by the date action is needed (the earlier date where there are two readings), with the columns Contract, Other party, Event (renewal, expiry, price review, notice deadline), Date, Notice needed and how it must be given, Act by, Clause. Act by is the notice deadline minus our lead time; for an event with no notice requirement, it is the event date minus our lead time, marked "reminder only". Where a deadline runs from receiving the other party's notice, write "within X days of receiving their notice" in Act by and list it under gaps. 3. Workings: a table with the columns Contract, Date, Calculation, Clause, for example "Term ends August 31, 2027; 60 days' notice (clause 12.2), so notice by July 2, 2027; reminder 30 days earlier, June 2, 2027." 4. Gaps and questions: contracts with no renewal or notice clause in the extract, wording that could be read two ways (such as business or calendar days, or when notice counts as given), and any deadline that has already passed. Rules: - Quote dates and notice periods exactly as written, and calculate only from them. Do not fill in typical notice periods or renewal terms; write "Not stated in extract". - Where an extract does not say whether days are business or calendar days, give the calendar-day date and the business-day date (Monday to Friday, public holidays not removed), and list the question. - Restate what the clauses say. Do not interpret their legal effect or advise whether to renew; questions about how a clause works go to a lawyer. Keep the text outside the tables under 250 words. If an extract is incomplete, such as a renewal clause without a start date, list the contract under gaps rather than estimating its dates.
Variables
- {{audience}}
- Who will use the calendar, for example "the office manager and finance".
- {{contract_extracts}}
- For each contract: its name, the other party, start date, term, and the renewal, notice and price change clauses copied with their numbers.
- {{today}}
- Today's date.
- {{lead_time}}
- How long before each deadline you want a reminder, for example "30 days".
Why it works
- Who it's for. It works across all your contracts at once and puts the next 90 days first, so the output is the one list someone actually sets reminders from.
- What good looks like. Every derived date has its own row of arithmetic and its clause, which makes a wrong deadline easy to spot before it matters.
- If unsure. Unclear day counts get both dates and a question, missing clauses say "Not stated in extract", and a missing date that could hide a passed deadline is raised at the top.