Follow one change through the whole task
Synthetic proposal: let staff reschedule a booking rather than cancelling and recreating it. The old baseline has cancellation only. The change is not yet approved; no price is assumed.
| Affected area | New decision/work | Owner | Evidence before approval |
|---|---|---|---|
| Record identity | Preserve booking ID through the move | Data owner | Before/after synthetic record |
| Permission and conflict | Who may move, and what happens if new room is occupied? | Operations owner | Allowed/denied/conflict cases |
| Messages and staff guide | New status, bilingual message and handling procedure | Content and training owners | Reviewed wording and walkthrough |
Small interface changes can affect other work
The supplier says rescheduling adds just one button. Is that enough information to approve the change?
Show the worked answer
No. Resolve identity, authority, conflicts and communication shown in the sheet, then review the revised effort and scope. Button count does not establish the complete change.
This is an impact review, not a pricing formula or automatic authorisation. The change record should link to the original baseline and actual approving decision.