Write a complete AI risk register entry with cause, event, impact, controls, owner, and trigger.
The risk register entry says only 'AI hallucination in support bot.' ISO 31000 risk record: cause, event, impact, controls, owner, trigger A vague risk label creates anxiety but gives the team no monitoring signal, treatment action, or accountability path. Cause Because the assistant can answer without retrieving an approved policy source... Start with the condition that makes the event plausible. The cause should be something the team can control or monitor. Event ...it may invent refund terms in customer replies... Name the specific event. Avoid broad labels like 'hallucination' unless they are attached to a workflow. Impact ...causing incorrect customer…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in