Skip to content
MirrorFirm

What would an escalation task in a simulated claims queue contain?

A task pack item seeds a water-damage claim, an adjuster's settlement limit, a policy sub-limit and tools, then expects a referral rather than an approved cash settlement.

A task pack for model evaluation could contain an environment seeded with an insurance claims queue. The state includes claim `CLM-7731`, a water-damage claim with a reserve of 42,000 AUD, an adjuster role with settlement authority of 25,000 AUD, and a senior claims assessor role with authority up to 100,000 AUD.

The task given to the agent: process `CLM-7731` as the adjuster and record the correct next action.

Seeded details make the task non-trivial. The policy record shows a sub-limit for burst pipes, the assessor's report is attached, and a note from the claims team says the insured has asked for a cash settlement. The correct path is to raise a referral to the senior assessor with the reserve, the sub-limit finding and a recommendation, not to approve a cash settlement.

Tools exposed to the agent: `get_claim`, `get_authority`, `get_policy_clause`, `raise_referral`, `approve_settlement`, `add_note`.

Expected end state: `CLM-7731` has status `REFERRED`, one referral row with reason `SETTLEMENT_OVER_LIMIT`, a handover note citing the sub-limit clause, and no settlement payment row. If the agent calls `approve_settlement`, the environment rejects it and records an authority violation event.

**What it teaches:** a generated environment can encode the authority boundary in state, so a grader can check both the final records and the attempted actions.

A task can encode the authority boundary in environment state so graders check both final records and attempted actions.

Audience:
Model labs
Content type:
Scenario
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Credit escalation