Execution

Execution is the point where a planned Program becomes a field day. Fishing keeps the work connected to the plan while making the actual conditions, changes, and outcome understandable afterward.

During the field day

Use the Program as the shared reference for the work that is being delivered. The team should be able to see what is planned, who is responsible, and the access or beat context that matters for the day. When conditions require a change, record the decision with enough context for a later reviewer to understand it.

Follow the variant timeline

• Fishing, IN + Fishing, and Transition + Fishing use the passenger, gear, Beat/access, Fishing Report, and return sequence.
• IN only, OUT only, and Transition use the authoritative passenger route and omit Beat, access, catch, and Fishing Report steps.
• POA and Transition + POA use activity preparation, arrival, start, completion, passenger return, outcome, notes, and incidents.

For variants with Fishing, Guide Mobile advances through the implemented sequence: pick up passengers, pick up gear, enter access, fish at the beat, leave access, return gear, submit the Fishing Report, and return to the lodge. A step becomes complete only when the real event occurs; upcoming steps remain unavailable until the timeline reaches them.

Use Issue on the affected step when reality differs from the plan. An issue adds execution context; it does not silently rewrite the CIS, access rule, inventory custody, or ready Program.

Preserve field evidence

• Start and monitor GPS only when the guide has field-location permission.
• Treat offline GPS points as queued—not confirmed server evidence—until they synchronize.
• When an access requires field payment, Paid + done records the access, direction, amount, currency, time, and payment method. Stop and contact Operations if those details are wrong.
• Record the actual access entry and exit instead of copying the plan.

Make an exception explicit

An exception is a real operating outcome, not an absence of information. A Program may be changed, delayed, cancelled, or completed differently from the original plan. Record the reason, the impact on delivery, and the next action so CIS and Operations can see the true state of the commitment.

Fishing owns the execution account. It does not rewrite a beat's curated knowledge after one day, decide the commercial terms of a crossing, or settle a charge. Those records remain with their respective areas.

Finish with the required evidence

For a variant with Fishing, the day only becomes trusted evidence when it has a clear Fishing Report. That report can support trip progress, operational closure, and future knowledge review without conflating those uses with the execution record itself.

Trailhead refuses Finish program on a Fishing variant until the Fishing Report is submitted. Non-fishing and POA variants close after their own required timeline and outcome without a Fishing Report. Completion closes active execution and attempts to stop GPS, but it does not reconcile inventory, correct the CIS, or replace account review.

Follow the complete procedure in Execute the Program.