Library › Customer Support & Success AI › Revenue operations

Find each contract's last notice date, with amendments and weekends

  • For Revenue operations
  • You practice Catching mistakes and made-up facts
  • Time about 5 minutes
  • Level Advanced

About this exercise

Build a plain-text table with the header row exactly "Account | Notice days | Last day | Status" and six rows sorted by Last day, earliest first. Use the latest notice period (an amendment overrides the original). If the raw last day falls on a Saturday or Sunday, use the Friday before. Status is Passed if the last day is before today (Nov 9), otherwise Open. Last line exactly: "Dates are for planning; Legal confirms notice terms."

Common mistakes when you ask AI for this

  • Using the original period for Cedar. The AI keeps 60 days. Try: Say: "An amendment overrides the original notice period."
  • Ignoring the weekend rule. The AI leaves Fir on Saturday. Try: Say: "If the last day is Saturday or Sunday, use the Friday before."
  • Sorting by account name. The AI keeps the alphabetical order. Try: Say: "Sort by Last day, earliest first."
  • Getting markdown back. AI adds bold and headings by default, which show up as stray symbols where this is pasted. Try: Say "plain text, no bold, no headings, no asterisks".
  • Trusting the AI to count words. The AI runs long and cannot count its own words. Try: Cap each part ("each line under 12 words") and add "under N words in total".
  • Leaving a requirement unstated. The AI follows its own defaults unless the prompt spells this out. Try: State it plainly in your prompt: the header row is exactly 'Account | Notice days | Last day | Status' followed by six rows and the exact last line 'Dates are for planning; Legal confirms notice terms.'.

What a strong prompt includes

  • Gives the header
  • Amendments win
  • Weekend rule
  • Status and closing line
  • Asks for plain text
  • Sets a word cap

Practice this now ↑

Related exercises