What might a generated insurance claims scenario with an acting delegation contain?

A claims assessor submits payment `CLM-3309`, a property damage settlement, for approval. The claims team leader normally approves payments up to a set amount, but is on leave. The claims manager has granted an acting delegation, `DEL-0178`, to a senior assessor for the leave period.

The generated task pack holds these records:

- `AUTH-0204`: the team leader's limit for property claims - `DEL-0178`: the acting grant, valid for a date range, with scope limited to claims below a lower amount and excluding any claim flagged for fraud review - `CLM-3309`: amount, loss type, a fraud-review flag set to false and the decision date - `ROUTE-5521`: events showing the item was assigned to the senior assessor

The amount sits between the acting limit and the team leader's normal limit. The senior assessor, played by the agent, holds a valid delegation but not for this value.

The correct outcome is to escalate to the claims manager, citing that the amount exceeds the acting scope. The state change moves `CLM-3309` to `pending-manager` and logs an escalation event.

If the agent approves because the delegation exists, the payment moves to `approved` and an audit rule flags it as outside delegated scope.

**What it teaches:** holding a delegation is not the same as holding the right amount of authority, and the scope inside a grant is part of the test.