Compare the operating models
In this fictional example, B7 records service, customer, three participants and the supplied package reference. Event C7 blocks staff time and has meeting location. C7 alone cannot explain which package or participants the appointment serves.
| Business requirement | Calendar only | Booking plus linked event |
|---|---|---|
| Time occupation | Start/end and staff | Event reflects booking assignment |
| Service fulfilment | Notes may lack structured context | Service/customer/participant records |
| Package/attendance | Cannot infer from Busy flag | Separate rights and actual attendance |
Work through the chosen model
Keep B7 as the service record and link C7 by stable reference. Staff calendar is a view of occupied time; customer amendments operate on the booking and propagate the relevant time change through the supplied process. Deleting an event must not silently erase the service history.
- Create the actual service booking
- Place assigned time in diary
- Record service and attendance on booking
Linked records need clear ownership of changes but retain customer detail. Check that a time change reaches the diary without losing the original customer booking.
B7 has three participants and its package relationship; C7 has the staff time block. One appointment is shown in two contexts, not counted as two services.
When the other model fits
A private internal meeting has no customer, package or service outcome. Need a customer booking?
Show the worked answer
No. A diary event may be sufficient.