Two customers book different staff members at the same time, but both visits need the only available treatment room. Checking staff calendars independently does not establish that the complete appointment fits.
Shared-resource scheduling needs to reserve every required resource for the relevant interval.
Describe the appointment as a resource requirement
List which staff, room, equipment, preparation time, and cleanup time the service needs. Some resources may have capacity greater than one; others are exclusive.
For a fictional studio, a consultation might need only a staff member, while a treatment needs that person and a particular room. The rules should come from operations, not from a model guessing what a service usually requires.
| Resource question | Scheduling implication |
|---|---|
| Is it required for the full visit? | Reserve the correct interval |
| Can several visits share it? | Model actual capacity |
| Does setup extend occupancy? | Include the required buffer |
| Can a substitute be used? | Apply an approved eligibility rule |
Use one authority for coupled availability
If a room is booked in one system and staff in another, define how the overall workflow avoids partial reservations. Independent success responses can leave a customer with only half the required appointment.
A scheduler with native resource support may reduce custom coordination. A custom system can encode more specialised rules, but it needs concurrency control, recovery, and operational maintenance.
For dental-specific rules, the provider-and-operatory article explains why resource eligibility needs more than an empty calendar space.
Handle partial reservation explicitly
Suppose the staff reservation succeeds but the equipment reservation fails. Decide whether to release the first reservation, hold it temporarily, or ask staff to resolve the request.
Track individual resource references under one operation. A retry should not reserve the staff member again while trying to finish the equipment step.
Do not describe the visit as confirmed until the agreed resource conditions hold. A useful pending request is preferable to an appointment that staff must quietly rearrange later.
Test conflicts across different appointment types
Use fictional requests for two services that share one resource, two that do not, an equipment outage, and a resource becoming unavailable during the call.
Inspect the whole resource plan and test direct office bookings too. Protecting only AI-created appointments leaves another path for conflicts.
The last-slot guide covers concurrent claims against capacity. Shared-resource booking adds the question of which capacity must be claimed together.
Shared-resource questions
Can separate free calendars prove the combined booking works?
Only if the coordination rules establish that the resources remain jointly available.
Should every service use the same resource list?
Use the actual approved requirements for each service.
What belongs in the project brief?
Include resource eligibility, capacity, buffers, and partial-failure decisions when scoping booking.