Library › Legal & Compliance AI › Compliance and risk

Update a risk register CSV from new notes without changing other rows

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

About this exercise

Update the risk register using the notes and output the full register as one CSV code block, nothing else. Add a sixth column named Change after Last_updated (header ID,Risk,Owner,Status,Last_updated,Change). Keep the order R-01 to R-05. Change only what the notes support. Set Last_updated to 2026-11-06 for rows you change or add, and leave other rows exactly as they are. Change is Owner changed, Status changed or New for rows you touch, and None for the others. Do not use commas inside fields. If the notes say something is claimed but not evidenced, use the status Closure pending evidence.

Common mistakes when you ask AI for this

  • Marking R-04 closed. The AI trusts the owner's claim. Try: Say: "Claimed but not evidenced means Closure pending evidence."
  • Touching other rows. The AI updates dates on every row or changes R-03. Try: Say: "Leave unchanged rows exactly as they are."
  • Broken CSV. The AI adds commas, quotes or a note around the block. Try: Say: "One code block, no commas inside fields, nothing else."
  • 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

  • Full register
  • Update date
  • Closure pending evidence
  • Leave other rows
  • Unassigned
  • Change column

Practice this now ↑

Related exercises