Library › Operations AI › Operations and supply chain
Build an incident timeline correcting a camera clock, without blame
- For Operations and supply chain
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Advanced
About this exercise
Write a prompt for a markdown table with columns Time, Event and Source and exactly five rows in time order, then one line starting "Conflicts:". Use 24-hour times. Correct any source whose clock is known to be off and show the corrected time. The Conflicts line notes where accounts disagree or cannot be verified. Do not say who was at fault. Under 190 words.
Common mistakes when you ask AI for this
- Using the raw camera times. The AI copies 14:12 and 14:13 from the CCTV. Try: Say: "The CCTV clock runs 4 minutes fast; subtract 4 and show it."
- Assigning fault. The AI concludes the driver caused the damage. Try: Say: "Do not say who was at fault."
- Wrong row count. The AI lists every minor event or leaves out the gate rows. Try: Say: "Exactly five rows" and name them.
- Trusting the AI to count words. AI is bad at counting and usually runs long, so a vague "keep it short" lands over the limit. Try: Cap each part instead of the total, for example "each line under 15 words".
What a strong prompt includes
- Names the columns
- Fixes the clock
- Asks for a Conflicts line
- Rules out fault
- Sets a length limit
Related exercises
- Accrue unpaid wages for the working days after the last pay period (Finance AI · Accountants)
- Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)
- Alert sales to a competitor's price change, facts only (Research & AI Search · Product managers)
- Annualize recurring revenue without the one-time fee (Data AI · Finance and accounting)
- Answer a credit dispute with the full-hour rule and the math (Customer Support & Success AI · Customer support teams)