What failure modes and evaluation questions should I plan for?
A buyer-facing FAQ on checking whether a model succeeded for the right reason, the typical failure modes, over-escalation, memorisation, multiple valid outcomes and the limits of the evaluation.
**How do I know a model solved it for the right reason?** Compare its stated cause and its cited evidence with the labelled root cause and evidence set. Score the evidence, not only the outcome.
**What failure modes should I look for?** - Forcing the numbers to agree by editing the wrong record - Accepting the first plausible cause - Acting beyond the role's authority - Ignoring downstream items such as notices or payments - Citing a record that does not exist - Escalating everything
**How do I detect over-escalation?** Include cases where the expected outcome is a correction within authority, and report unnecessary escalation separately from missed escalation.
**Can I check for memorisation?** Ask for a split by template and by identifier style, and hold out whole templates, so a model cannot rely on having seen the same structure in training.
**What if two correct outcomes exist?** A task pack can list accepted alternatives, and the grader can accept any one of them while still rejecting unsafe actions.
**Does passing mean a model is ready for a live finance team?** No. A generated evaluation tests specific behaviours. Readiness for production use needs its own assessment, with your own controls and review.
Score evidence, route and escalation behaviour separately, hold out whole templates, and treat a pass as evidence about specific behaviours only.
- Audience:
- Model labs
- Content type:
- FAQ
- Buyer question:
- How to evaluate it
Content release: r-a220eb6e099b243b
Related questions
- How does path-level scoring separate two agents that both match the totals?
- How can a buyer inspect the quality of generated mismatch cases?
- What checks should I run on a pack before using it for evaluation?
- How should I score an agent that reaches the right fix for the wrong reason?
- Where do reset, trace and grading hooks fit around an agent run?
- How do we know a generated mismatch case is solvable from what the agent can see?