{"id":"exec-risk-register-json-from-status","audience":"project-managers","category":"leadership-work","track":"leadership","level":"intermediate","technique":"format","title":"Convert status notes into a risk register in JSON","free":false,"task":"Convert the project status notes into a JSON array in one code block. Each object has exactly these keys: risk, impact (high, medium or low), owner, due. Include only items described as risks, not issues that have already happened. Use owner \"TBD\" when none is named. At most 14 lines inside the block and no text outside it.","materialLabel":"Status meeting notes (attached to your prompt automatically)","material":"Warehouse system rollout - status Nov 5\n\n- Risk: the vendor might miss the Dec 6 delivery of the scanner firmware. Impact would be high; owner Nia; decision needed by Nov 20.\n- Issue (already happened): the test environment crashed Monday. Fixed by Ben. Not a risk now.\n- Risk: pick-path training for night shift is not scheduled and the shift lead has not been told. Impact medium. Nobody owns this yet. Due before go-live.\n- Risk: data migration of 80,000 SKUs could duplicate items. Impact high; Ben owns it, test migration due Nov 18.\n- Complaint: someone said the scanner screens are too small. This is a preference, not a risk.\n- Risk: go-live on Dec 14 coincides with holiday peak. Low impact now that the CEO accepted a soft launch. Owner: Nia. Review on Dec 2.\nUpdate: the vendor confirmed Dec 6 in writing on Nov 5, so the firmware risk drops to medium.","rules":[{"type":"codeBlocks","count":1},{"type":"maxCodeLines","max":14},{"type":"maxProseWords","max":5}],"mistakes":[{"title":"Including issues","why":"The AI adds the test environment crash.","fix":"Say: \"Only risks, not issues that already happened.\"","checks":["r0"]},{"title":"Ignoring the update","why":"The AI keeps firmware as high.","fix":"Say: \"Apply the vendor's written confirmation: medium.\"","checks":["r1"]},{"title":"Wrong keys","why":"The AI adds extra keys like status.","fix":"Say: \"Exactly the keys risk, impact, owner, due.\"","checks":["r2"]},{"title":"Extra text","why":"The AI explains the register.","fix":"Say: \"Only the code block.\"","checks":["codeBlocks","maxProseWords"]},{"title":"Long output","why":"The AI spreads objects across many lines.","fix":"Say: \"At most 14 lines inside.\"","checks":["maxCodeLines"]}],"promptHints":[{"label":"Keys","patterns":["risk","impact","owner","due"]},{"label":"Only risks","patterns":["only risks","not issues","already happened"]},{"label":"TBD","patterns":["tbd"]},{"label":"Update","patterns":["update","confirmed","latest"]},{"label":"One block","patterns":["code block","json"]}],"hint":"Name the keys, the include/exclude rule, the TBD rule and the update.","rubricLabels":["The JSON has exactly four risk objects (firmware delivery, night-shift training, data migration, holiday-peak go-live) and does not include the crashed test environment or the screen-size complaint","The firmware risk has impact medium (the update), owner Nia, and the training risk has owner TBD","Every object has exactly the keys risk, impact, owner, due and nothing appears outside the code block"]}