{"id":"exec-audit-committee-top-risks-table","audience":"executives","category":"leadership-work","track":"leadership","level":"intermediate","technique":"verification","title":"Rank the top three risks for the audit committee with scores","free":false,"task":"Rank the top three risks for the audit committee. Score is likelihood times impact (each 1 to 5), using the latest scores in the register. Break ties by higher impact. Output a table with the header Rank | Risk | Score | Owner and exactly three rows, with the working in the Score column like \"4 x 5 = 20\". Add a last line: Scores are management estimates for committee review. Plain text, under 80 words.","materialLabel":"Risk register extract (attached to your prompt automatically)","material":"Enterprise risk register, Q3 (likelihood x impact, each 1-5)\n\nR1 Key supplier failure - L3 I5 - Owner: Priya Nair\nR2 Ransomware attack - L2 I5 - Owner: Dev Oyelaran\nR3 Loss of top-5 customer - L3 I4 - Owner: Sam Whitaker\nR4 Regulatory fine for late filings - L2 I3 - Owner: Elena Costa\nR5 Key-person loss in finance - L4 I3 - Owner: Elena Costa\nR6 Data center outage - L3 I4 - Owner: Dev Oyelaran\nR7 Currency swings - L4 I2 - Owner: Priya Nair\n\nUpdates after the register was printed:\n- Sep 30: Dev re-scored R2 ransomware to L3 I5 after a near-miss at a peer firm.\n- Oct 4: Priya lowered R1 supplier failure to L2 I5 after signing a backup supplier.\n- Sam says R3 is \"probably a 4 on likelihood\" but has not updated the register.","rules":[{"type":"maxWords","max":80},{"type":"plainText"}],"mistakes":[{"title":"Using the printed scores","why":"The AI ranks supplier failure first using L3 I5.","fix":"Say: \"Use the latest scores in the register updates.\"","checks":["r1","r2"]},{"title":"Trusting hearsay","why":"The AI changes R3 to likelihood 4.","fix":"Say: \"Use only recorded scores, not what someone says.\"","checks":["r1"]},{"title":"No working shown","why":"The AI shows only the total.","fix":"Say: \"Show the working like 4 x 5 = 20.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds columns.","fix":"Say: \"Header Rank | Risk | Score | Owner, three rows.\"","checks":["r0"]},{"title":"Missing closing line","why":"The AI adds commentary.","fix":"Say: \"End with the exact line.\"","checks":["r2"]},{"title":"Markdown","why":"The AI uses bold.","fix":"Say: \"Plain text.\"","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each part instead, for example: \"each line under 15 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Gives the header","patterns":["rank \\|","risk \\|"]},{"label":"Says latest scores","patterns":["latest","updates","re-scored"]},{"label":"Asks for the working","patterns":["x 5","working","likelihood times impact"]},{"label":"Handles ties","patterns":["tie","higher impact"]},{"label":"Gives the closing line","patterns":["management estimates"]}],"hint":"Give the header, tell it to use the latest recorded scores, and ask it to show the working.","rubricLabels":["Has the header Rank | Risk | Score | Owner and exactly three rows ranked 1, 2, 3","Rank 1 is ransomware attack with 3 x 5 = 15 (Dev Oyelaran); the other two are data center outage with 3 x 4 = 12 and loss of a top-5 customer with 3 x 4 = 12 (Sam's unrecorded 4 not used)","The tie between the two scores of 12 is placed with equal impact so both appear in the top three, supplier failure (2 x 5 = 10) is not in the list, and the last line is exactly \"Scores are management estimates for committee review.\""]}