Use safe fixture data to verify both the coordinator-resolution and Head Guide escalation branches.
Before you start
- Act as
- The assigned Guide Coordinator for the fixture lodge and day
- Starting state
- Two Programs claim one capacity slot on the same Beat
- Ranking
- Active working guides have unique explicit ranks; rank 1 is highest
Run the scenario
- 1Guide CoordinatorTrailhead Mobile · Calendar
Open the Program conflicts banner immediately before the calendar.
Expected evidence
The banner shows the open count, the header has no conflict icon, and the queue contains one shared conflict.
- 2Guide CoordinatorTrailhead Mobile · Resolve conflict
Choose one Program, select an available Beat, review the exact change, and confirm.
Expected evidence
Trailhead rechecks live ownership and capacity, moves only the selected Program, and clears the shared conflict when capacity is restored.
- 3Guide CoordinatorTrailhead Mobile · Escalate conflict
Repeat with the second fixture, choose Escalate to Head Guide, and provide a reason.
Expected evidence
The complete conflict stays blocked and ownership transfers to Head Guide; the original coordinator becomes read-only.
- 4Head GuideTrailhead Mobile · Escalated conflict
Open the escalated item and make the final resolution.
Expected evidence
The audit identifies Head Guide as final decision-maker and no duplicate Program is created.
Scenario completed
The current owner resolves the shared conflict or preserves its escalation
- Lodge/day duty
- Not started→Guide Coordinator assigned · USD 30 accrued
- Program conflict
- Guide Coordinator owned→Resolved
- Decision owner
- Guide Coordinator→Head Guide
- Escalated conflict
- Blocked→Resolved
If it does not match
- If the signed-in guide is not the current coordinator for that lodge and day, resolution and escalation must remain unavailable.
- If ownership, conflict revision, or destination capacity changed, keep the Programs blocked and refresh current data before another decision.