Check a system
Answer 13 questions about one AI system that can take actions. As you answer, the page shows the system’s gaps, the incidents in the record that had the same gaps, and the guidance that covers them, and at the end it produces a short report for whoever runs the system.
How to answer
Choose one system and one kind of action it can take, such as issuing refunds, merging code, or answering customers about fees. Controls differ by action, so a system that is well controlled for one action can have gaps for another. Answer “Yes” only if you have seen the control work, and “Not sure” when you would have to ask. A “Not sure” is treated as a gap until someone checks.
Fills in answers for a fictional customer support agent to show a finished report. Clear the answers to start your own.
Your report
Answer the questions above to see which gaps this system has.
Using the report
- Take each gap to whoever runs the system, with the question under it. If a vendor runs the system, the matching contract clause puts that question in writing.
- Priorities depend on the system. In the record, direct access (G2) and instruction-only limits (G1) recur in agent incidents and unchecked statements (G3) in incidents involving a conversational assistant, and review in name only (G7) appears in most incidents in which people approved AI output.
- The implementation guide describes one way to add an outside check to a single workflow, and the specifications page shows which published specifications address each gap.