A booking-change record should show what was requested, what was authorised and what the customer or internal requester has actually been told. Keep the proposed change separate from the confirmed booking until the correct decision has been made.
This guide uses an original office-room example. Apply the actual booking terms, authority and record process for your workplace rather than assuming the example determines cancellation rights or payment outcomes.
Identify the current confirmed arrangement
Start with the correct booking reference and approved details. Check the date, time, location, resources and relevant conditions before considering the change.
Use the current authoritative record, not an old email attachment or someone’s recollection. If the records conflict, identify the discrepancy and refer it for resolution before issuing another confirmation.
Record the request date and the person making it through the approved verification process. A request from an unfamiliar contact should not automatically alter someone else’s booking.
Use a practical change register
For each proposed change, record:
- Booking: reference and current confirmed details.
- Request: the specific difference sought and when it was received.
- Checks: availability, dependencies and applicable conditions.
- Decision: authorised approval, refusal or information still needed.
- Status: pending, confirmed or another clearly defined outcome.
- Communication: what was sent, to whom and when.
- Follow-through: calendar, resource or other records requiring an update.
- Owner: the person responsible for closing the change.
Keep necessary personal information in the approved system. A general room-use calendar need not display private reasons for a requested change.
A fictional date-change example
In this invented scenario, an internal requester asks to move a meeting from Tuesday morning to Wednesday afternoon. The booking coordinator finds the room available, but an additional requested resource has not been confirmed.
The change remains pending while the resource owner checks. The coordinator tells the requester what is unresolved and does not cancel the original arrangement prematurely under an assumed rule.
Once the authorised decision is made, the coordinator updates the correct records and sends a clear confirmation identifying the new arrangement. The message explains which previous confirmation it replaces, using the organisation’s actual process.
Coordinate connected records
Check calendars, equipment, staffing, access and any supplier or service arrangement affected by the change. Update only what has been authorised and identify tasks requiring another owner’s action. For an administration application, an invented booking-change example can demonstrate the coordination work described in our administration roles guide, including checking that related records reflect the confirmed decision.
Comcare’s effective communication guide offers broader context for clear work communication. In booking administration, that means the people implementing a change need the same confirmed details.
Avoid several conflicting confirmations from different team members. Agree who communicates the outcome and how later enquiries find the current record.
Close the request against evidence
Check that the authorised change has been implemented and the relevant recipient has received the appropriate update. A completed internal edit does not prove that the requester knows the new arrangement.
If a request is declined or withdrawn, record the outcome and confirm which booking remains in place. Preserve the history through the approved records process. A useful register lets another coordinator understand the current booking and the path from request to decision without reconstructing the whole email chain.
