Library › Legal & Compliance AI › Compliance and risk

Turn four incident notes into risk register entries as JSON

  • For Compliance and risk
  • You practice Setting limits and rules
  • Time about 5 minutes
  • Level Intermediate

About this exercise

Turn the incident notes into risk register entries. Output one JSON array in one code block, nothing else. Merge incidents with the same cause into one entry. Each object has exactly these keys: risk, source_incident, first_reported, owner, status, likelihood, impact. risk is under 12 words, source_incident is one string of the incident ids joined by "; ", first_reported is the earliest incident date as YYYY-MM-DD, owner comes from the notes (Unassigned if none), status is Proposed, and likelihood and impact are both TBD because the risk owner rates them.

Common mistakes when you ask AI for this

  • Not merging duplicates. The AI gives each incident its own entry. Try: Say: "Merge incidents with the same cause into one entry."
  • Inventing ratings. The AI fills in likelihood and impact scores. Try: Say: "likelihood and impact are both TBD."
  • Guessing owners. The AI assigns someone to the invoice issue. Try: Say: "owner is Unassigned if the notes name nobody."
  • Extra code blocks or chatter. The AI adds a second block or explains around the code. Try: Say: "One code block only, no text outside it."
  • Chatter around the block. The AI adds an intro and notes outside the code. Try: Say: "Output only the code block, no other text."

What a strong prompt includes

  • Merge duplicates
  • Exact keys
  • TBD ratings
  • Unassigned owner
  • Code block only
  • Date format

Practice this now ↑

Related exercises