Programs and readiness

A Program is the daily unit of guide work connected to a CIS. It can represent fishing, a POA activity, arrival or departure duty, or an internal lodge transition. The CIS day context determines which variants are valid.

Program variants

IN + POA, Fishing + OUT, and POA + OUT are not supported. A missing or ambiguous IN/OUT transfer blocks Program creation until Operations corrects the CIS. The same guide may perform one OUT and one IN on the same date; together they represent 1.00 guide units and appear as two halves in the mobile calendar.

Start from the right source

CIS creates the demand: the trip dates, service, and work the lodge has promised. Fishing turns that demand into a Program. Guides provides the people-readiness context that shows whether the work can be delivered.

What a ready Program makes clear

A useful Program gives the team one shared view of the day:

• the client commitment it serves and the day it belongs to;
• the work to deliver, the people involved, and the intended field context;
• the access and beat context when it is relevant to the plan; and
• the readiness questions or changes that need attention before execution.

Readiness is not a separate copy of guide information. Fishing uses the availability, credential, gear, and assignment signals supplied by Guides to make a practical decision about the Program. Guides remains responsible for the underlying people record.

Follow the contextual planning sequence

Create the Program from the assigned CIS so its date, lodge, and trip context stay connected:

1. Open the assigned CIS date and select only the Program variant offered for that context.
2. Confirm the preselected arrival clients, ordinary-day participants, or read-only transition manifest.
3. For Fishing, choose a Beat and check access, capacity, and recommendation reasons.
4. For POA, choose the activity; keep the Trailhead guide required and add an external provider only when relevant.
5. For IN, OUT, and Transition, review the authoritative CIS route instead of recreating it.
6. Review the variant, people, route, Beat or POA activity, lodge context, and compensation.
7. Send the Program into conflict review.

A recommendation is decision support, not clearance. An unavailable access or insufficient capacity can still block a highly ranked beat.

Execution and evidence by variant

• Fishing, IN + Fishing, and Transition + Fishing use Beat/access execution and require a submitted Fishing Report before closure.
• IN only, OUT only, and Transition use the passenger-transfer timeline and omit fishing-only steps.
• POA and Transition + POA use activity, participant, provider, outcome, notes, and incident context; they do not create access usage, catch rows, or a Fishing Report.

Readiness and conflict states

• No conflict: Trailhead marks the Program ready automatically; coordinator review is not required.
• Conflict found: the Program remains blocked until the coordinator works with the guides and resolves the exception.

Do not describe every Program as waiting for manual review. Coordinator involvement is the exception path, not the default path.

When the plan needs to change

Conditions, travel, client needs, or a people constraint can make the original plan unsuitable. Keep the decision visible on the Program: what changed, why it changed, and what the team will do next. Do not hide an unresolved readiness issue by treating it as completed work.

An accepted exception is still part of the Program record. It gives Operations a clear signal to follow and gives CIS an honest view of what the trip received.

Continue the planning path