The preferred person already has overlapping work, so staffing must change before the CIS can accept the team.
Track
Assignments
Phase
Conflict branch
Starts with
Selected person unavailable
Ends with
Valid staffing choice accepted
Trailhead detects that a selected person cannot cover the booking range. The conflict blocks the invalid team while Ops and the manager choose a valid alternative.
Trailhead flags a conflict while Ops assembles a booking team.
The complete CIS date range is checked for overlapping work.
This is the key moment: the invalid commitment cannot be added as though it were only a warning.
Protected assignment history remains unchanged.
Client preference informs the decision but never overrides availability.
Resolution changes the proposed team rather than rewriting existing work.
The branch rejoins team construction only after availability passes.
Stops the invalid addition and chooses a workable person.
Balances the conflict with the requested-guide context.
Blocks overlap and rechecks the replacement choice.
A blocking conflict beside the selected person
Why: Avoid saving an impossible commitment.
Conflict details and requested-guide context
Why: Choose the best valid staffing alternative.
An availability conflict blocks the team; passenger preference cannot override it.