Skip to content
MirrorFirm

Which features make an escalation task a real test of agent judgement?

A checklist for separating tasks that test delegated-authority judgement from tasks that only look up a threshold and return a label.

Use this list to check whether a proposed task is testing escalation judgement rather than simple classification.

- The authority limit depends on at least two fields, such as product and aggregate exposure. - A related record elsewhere in the case changes the answer. - More than one next approver exists, and only one is correct. - The handover requires a rationale, a policy reference and attached evidence. - Some cases sit inside the agent's authority and should not be referred. - The senior reviewer's possible outcomes include conditions and return-for-information, not only approve or decline. - The case history records earlier referrals, so repeated or circular escalation can be detected.

A task that meets only the first item is closer to a threshold lookup. Tasks meeting most of the list start to resemble how delegated authority works in a credit team, where the decision, the route and the paperwork are all assessed.

Whether a given task pack covers these items is something to confirm in a sample before relying on it, and a sample is also the place to see how many of the cases meet more than one item at once.

Use the list to reject tasks that reduce to a threshold lookup and keep those where decision, route and paperwork are all assessed.

Audience:
Evaluation teams
Content type:
Checklist
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Credit escalation