Sales records guide preferences and unnamed POA guide spaces without creating operational assignments.
Track
Assignments
Phase
Staffing demand
Starts with
Guide preferences or POA capacity known
Ends with
Planning demand visible without assignments
A booking includes zero or more requested guides and may need POA guide capacity. Trailhead preserves both as planning demand while Operations builds actual Guide/AUX teams separately.
Sales or Operations reviews Guide Requirements while creating or editing a CIS.
This booking control captures demand, not the operational team.
An active guide may be requested before Program-readiness checks are complete.
The count reserves unnamed calendar capacity and does not assign a person.
This is the key moment: requested guides and blank POA rows inform planning but never become assignments by themselves.
The request remains visible; availability and role checks apply only to the team.
Records guide demand without presenting it as confirmed work.
Uses requested guides and POA capacity when building the operational team.
Keeps preferences, capacity, and named assignments separate.
Requested Guides, POA guide count, and a separate Operational Teams section
Why: Preserve demand without promising staffing.
Preferences beside actual team planning and availability checks
Why: Turn demand into a valid named team deliberately.
Requested guides are preferences, POA rows are unnamed capacity, and only saved operational teams are assignments.