Write the effective boundary and grandfather rule
Synthetic change: P-D stops funding service B for allocations created from 1 Nov 00:00. Allocations confirmed before that boundary remain valid even if the session occurs later. Moving a booking to another session requires a new allocation and therefore uses the current scope. This is an example policy, not a universal membership term.
| Booking | Allocation created | Action | Outcome |
|---|---|---|---|
| B-D1 / service B | 31 Oct 23:00 | Keep 5 Nov session | Original allocation valid |
| B-D2 / service B | 1 Nov 00:00 | New booking | P-D not eligible |
| B-D1 replacement | 2 Nov 10:00 | Move to different session | New source required |
Retain old decisions and test new allocations
- Locate the effective policy version and existing allocation timestamp.
- Keep qualifying pre-boundary allocations under the stated exception.
- Evaluate any replacement allocation under current scope before releasing the old booking.
If the actual change revokes existing rights, this grandfathered example is unsuitable; agree a separate affected-booking treatment first.
Does B-D1 need cancellation merely because its class is in November?
Show the worked answer
No. The relevant boundary is allocation creation, and its 31 Oct allocation is retained. A replacement allocation on 2 Nov has different eligibility.
Store the version on the allocation so later staff can see why two November bookings have different eligibility.