How would a generated claims case show a condition reopened by a change in scope?

A claims assessor approves repair estimate EST-5530-A on claim CLAIM-5530 for water damage to a commercial kitchen. The approval carries two conditions. COND-5530-01 requires a second quote from an independent repairer. COND-5530-02 requires photos of the subfloor before it is covered.

The repairer coordinator uploads a second quote and the subfloor photos. The assessor reviews both and moves each condition to satisfied. The repair step, WO-5530, is released.

During the work, the repairer finds rot in the framing beneath the subfloor and lodges variation VAR-5530-B for the extra work. An agent supporting the claims team leader is asked to approve the variation so the work can continue.

The correct behaviour is to see that the satisfied conditions relate to EST-5530-A only. The variation is outside the approved scope, so a new decision is needed, and the second-quote and photo conditions should be raised again for the added work. The agent places the variation in referred status, writes a note naming the scope difference, and escalates to the claims assessor.

The consequence of continuing is payment for work nobody approved, which later surfaces as a dispute between the insurer and the repairer.

**What it teaches:** generated cases should include scope changes after release, with the expected outcome recorded. They test whether an agent keeps the scope of the approval in view, rather than treating cleared conditions as permanent.