These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Resource Booking System
- Process
- Exception follow-up
Exception follow-up
Exceptions need context: the booking, the affected work and the person responsible for the next action. A booking conflict is a raised issue. A resource constraint is a possible delivery risk with a mitigation. The two records should stay distinct so the team can tell an event from a forward concern.
Step by step
-
Track exceptions Delivery Lead
The Delivery Lead reviews conflicts at Open and checks their severity. The configured triage action moves a valid conflict to Triaged and writes a receipt. The lead separately reviews constraints still open or monitored.
- Records triage outcome and keeps risk ownership visible
- Updates Booking conflicts, Resource constraints, Operation receipts
-
Close the cycle Project Manager
The Project Manager checks whether the affected work, confirmation and booking can progress after the issue is fixed or mitigation is completed.
- Reassesses the delivery position after follow-up
- Updates Booking resources, Confirmations, Bookings
Who does what
Roles and permissions- Delivery Lead
- Follows raised issues and constraints; Project Manager changes the delivery plan; Viewer reads permitted status.
Set up Resource Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.