Confirmation must combine capacity and declared session resources while distinguishing a customer's request from an effective reservation.
Index
Booking a free room does not enable a session that also needs available equipment or support; the calendar must show the complete set.
The rule that changes the scope
Confirmation must combine capacity and declared session resources while distinguishing a customer's request from an effective reservation.
A room calendar covers ordinary meetings; an extension handles shared equipment and preparation by internal staff.
Mobile equipment may need transfer and setup between sessions. Adjacent bookings in different rooms can be impractical even without overlapping use. Bring that case into the prototype and define who confirms preparation completion. The module need not automatically optimize the entire schedule; a first release can expose conflicts and support an informed decision without turning a suggested change into a new promise already communicated to the customer.
Specify operational deliverables
- Associate the session with its room, specific resource and preparation owner.
- Show equipment conflicts between rooms during the same interval.
- Keep format changes and the confirmations that must be reviewed.
Test the exception before acceptance
In a hypothetical scenario, two available rooms request the same equipment; only one session can confirm the resource during the conflicting interval.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a special-resource session and the process used to prepare its environment.