Define the exact change set
Synthetic change moves three selected session starts by thirty minutes. It does not alter duration, staff or room. Each occurrence gets its own before/after record, affected bookings and response result. A bulk command is complete only when every occurrence has a recorded disposition, including blocked ones.
| Occurrence | Before → proposed | Review finding | Disposition |
|---|---|---|---|
| O-B1 | 18:00 → 18:30 | All affected bookings accept | Ready to apply |
| O-B2 | 19:00 → 19:30 | One package expires at 19:15 | Blocked for that booking |
| O-B3 | 20:00 → 20:30 | One response outstanding | Response pending |
Apply only resolved occurrence decisions
- Capture selected occurrence IDs and their original revisions.
- Evaluate each proposed start against booking eligibility and required responses.
- Save applied, blocked or pending outcome per occurrence and update reminders only for applied changes.
If the batch must succeed as one indivisible change under the actual policy, leave all three pending until every blocker is resolved.
Can the register mark all three changes completed because every proposed time was calculated?
Show the worked answer
No. Only O-B1 is ready. O-B2 has a validity blocker and O-B3 lacks a response; calculating a time does not resolve those conditions.
Retain an occurrence disposition count for staff follow-up; customer pages need only the individual’s actual confirmed outcome.