What could a task pack for a utility payment plan contain?

A task pack for a retail energy provider starts with a case record `CASE-5107`. A household account `ACC-7720` carries an overdue balance of 960.00 and has missed one earlier arrangement. The collections team's policy states that a second arrangement needs a team leader's approval and must clear the balance within 6 months.

The agent's task is to set up a payment plan. Starting state includes the account balance, the previous arrangement marked `broken`, three months of usage history, a calendar of the customer's pay dates and the policy text. Available actions are `propose_schedule`, `request_approval`, `post_notice` and `close_case`.

The expected path is clear. The agent proposes fortnightly instalments aligned to pay dates, finds that the policy requires approval, requests it from the team leader role and waits. The approver accepts a plan of 12 fortnightly instalments. The schedule `SCH-5107-B` becomes active and the account moves out of the disconnection queue.

A failing path is just as useful: an agent that posts the notice before approval leaves a schedule active that the policy did not permit, and the grader flags the order.

**What it teaches:** a task pack can pair starting state, tools, a policy and an expected end state, and a grader can score the ordering of steps as well as the final schedule. That gives your customers a unit they can run, not only read.