What can a utility account review teach about authority and handovers?

A utility account administrator opens scheduled review `REV-0412` for account `ACC-2187`. The contact record lists an account holder, while a recent service note says an estate representative has requested correspondence. The representative's authority document is still awaiting verification.

The administrator records the discrepancy and changes the review state from `in_progress` to `awaiting_authority_check`. A specialist team receives follow-up case `CASE-0631`, linked to the service note and the outstanding document request. The billing address remains unchanged until the authority check reaches an outcome.

Closing the review immediately would hide unfinished work. Changing the correspondence details immediately would treat a service note as sufficient authority. Leaving the discrepancy only in free text would make it harder for the specialist team to discover what requires action.

A generated task pack could ask a model to choose the state transition, identify the receiving role and explain which account fields must wait. For resellers, the teaching point is precise: scheduled maintenance can uncover a separate authorisation process, and successful handling depends on creating a traceable handover rather than completing every action inside the original review.