Define the extension unit and scope
Synthetic rule: an approved extension adds seven calendar days to the existing unusable-from boundary. It changes no session quantities and revives no cancelled booking. Use the approved old boundary as the starting point; applying the same approval twice must not add fourteen days.
| Record | Before | Decision | After |
|---|---|---|---|
| P-X / expiry | 11 Oct 00:00 | Approval X-1: +7 days | 18 Oct 00:00 |
| P-X / available | 3 sessions | No quantity adjustment | 3 sessions |
| B-X / cancelled | Cancelled for prior expiry | No automatic revival | Customer must rebook |
Save the approved boundary change
- Read approval X-1, its target package and old boundary.
- Move the boundary to 18 Oct 00:00 and record both timestamps.
- Re-evaluate future eligibility without recreating cancelled bookings.
If a different extension has already changed the boundary, reconcile approvals before adding days.
A new session starts at 18 Oct 00:00. Can P-X fund it?
Show the worked answer
No. The rule requires a start before the unusable boundary. A 17 Oct 23:30 start would meet the time test, subject to the other booking conditions.
The approval record should explain why validity changed; the session statement should still reconcile to the unchanged package total.