What does a future customer move teach a model about effective dates?

A utilities customer has arranged to leave a property under MOVE-2187. The customer then tells a service adviser that the move will occur after the date currently recorded. The account remains active, a final meter reading is booked and a closing bill is queued.

The adviser records the revised departure date immediately. Service responsibility, however, must continue until that future date. The meter booking needs rescheduling, and the closing bill must remain pending until the revised reading is available. Closing the account when the message arrives would allocate subsequent usage incorrectly.

A scheduling coordinator updates READ-0412 and returns the new booking reference. The adviser links that confirmation to MOVE-2187 and leaves the closure pending. The resulting state distinguishes an accepted request from a completed departure.

A generated scenario can expose the model to both the request timestamp and the effective date, along with dependent events scheduled between them. It teaches temporal reasoning across business records: which facts are known now, which obligations remain active and which actions must wait for a future event. The consequence is visible in service continuity and the eventual billing period.