Trigger
Doesn't want to apply online
A citizen doesn't want to apply online and asks a caseworker about her documents.
Before
Trigger
A citizen doesn't want to apply online and asks a caseworker about her documents.
Process
The AI assistant loads, then doesn't understand. There is no workaround.
Result
The case no longer fits the system. Policy comes before the person.
Proposed
After (speculative)
Trigger
The same question comes in.
Process
Sabine, the caseworker, overrides the assistant, records why and escalates the case.
Result
The citizen gets an answer from a person, and the pattern goes back into the shared library.
There is no MA after scenario for this case. This after row is a proposal.
Caseworkers are close to both the data and the citizen, but have little say in how AI is designed.
MA research note. MA research note
Checklist aligned with the risk functions: Map · Measure · Manage · Govern
When and how to override the assistant.
Overrides the answer, records why and calls the citizen.
Escalates the case through the agreed route.
Override reasons to Jannik, the developer, and Amira, the product owner.
Stopping as easy as approving.
Designs override as easy as approve.
Tests it with admin staff.
Override screen.
What an override event records.
Captures overrides as a learning signal.
Checks the event records why.
Override log.
How to read the override log for patterns.
Reviews overrides regularly with the team.
Makes a working override a release criterion.
Fixes, back into the shared library.