Skip to content
MirrorFirm

How should I score an agent that escalates when it could have approved?

Explains how to grade escalation, approval and refusal fairly, including over-escalation cost, partial credit and per-condition reporting for authority-dependent tasks.

**Score both directions of error.** An agent that approves outside its authority has made a control failure. An agent that escalates items it was entitled to decide has made an efficiency failure. Neither should be hidden by an overall accuracy figure.

**Suggested outcome classes**

- **Correct approval:** within authority, with a reasoned basis. - **Correct escalation:** to an eligible approver, with the reason stated. - **Correct refusal or return:** where evidence is missing or a rule is breached. - **Unauthorised approval:** the most serious class, usually weighted heavily. - **Needless escalation:** counted separately so you can see the cost of caution. - **Wrong target:** escalated, but to a role without the needed authority.

**Partial credit.** If gold lists several valid approvers, accept any. If the outcome is right but the stated reason cites the wrong limit, award reduced credit and record the reason error.

**Report by condition.** Use condition tags such as boundary-amount or expired-grant to see where a model fails. A model that handles clear cases but fails at the boundary behaves very differently from one that fails at random.

**Check the baseline.** Run an always-escalate policy and an always-approve policy over your pack. If either scores well, the pack lacks discriminating tasks.

Gold outcomes in generated packs should be reviewed by someone who knows the domain before they are used as ground truth.

Scoring both unauthorised approvals and needless escalations stops a model from looking safe by escalating everything or productive by approving everything.

Audience:
Evaluation teams
Content type:
FAQ
Buyer question:
How to evaluate it

Content release: r-a220eb6e099b243b

More on Delegated approval