Complete the passengers, Beat, activity, provider, and logistics required by the selected variant.
Track
Program Planning
Phase
Create
Starts with
An assigned CIS needs a daily Program
Ends with
The Program is ready or visibly blocked by a conflict
A guide selects the context-valid Program variant, completes only its required inputs, reviews the day, and sends it through conflict review.
The guide opens an assigned CIS that still needs a Program.
Starting from the CIS preserves the date, lodge, and trip promise.
Fishing needs a Beat; POA needs an activity and may include a provider; IN/OUT and Transition keep CIS routes read-only.
IN preselects arriving clients; Transition automatically includes every transferring CIS client.
A conflict-free Program becomes ready automatically; coordinator review is only for exceptions.
Builds the practical day from the assigned trip context.
Owns coordination only when conflict review finds an exception.
Checks the submitted Program for conflicts and marks the clear path ready.
The contextual variant, required inputs, clients or manifest, review, and conflict result.
Why: Build and verify the day without duplicating CIS travel records.
Only Programs that require coordination after a conflict.
Why: Focus attention on real exceptions.
The submitted Program inputs and the resulting review state.
Why: Keep the normal path automatic and the exception visible.
Create the Program from the assigned CIS and keep variant-specific requirements intact; never force a Beat or Fishing Report onto non-fishing work.