TrailheadFishing OperationsField Delivery and Evidence
FD-01ExecuteNo assistant eval · Coverage unknown

Execute the Variant Timeline

Advance the IN, OUT, Fishing, POA, or Transition timeline only as real events occur.

Track

Field Delivery and Evidence

Phase

Execute

Starts with

A ready Program is available for execution

Ends with

The required variant timeline and outcome are recorded

You are here

FD-01
  1. FD-01Execute the Variant Timeline
  2. FD-04Change the Program Beat After an Incident
  3. FD-02Submit the Fishing Report
  4. FD-03Finish the Daily Program

The situation

The guide follows the timeline owned by the Program variant. Fishing includes Beat, access, and report steps; POA uses activity execution and outcome steps; IN, OUT, and Transition focus on the authoritative passenger route without fishing-only work.

What starts it

A ready Program reaches its execution day.

How it unfolds

GuideOperations
  1. 1

    Open the ready Program and begin its variant-specific timeline

    Guide
  2. 2

    Record passenger custody and route events when they occur

    Guide

    IN, OUT, and Transition follow the authoritative CIS route and passenger context.

  3. 3

    For Fishing variants, record gear, access, Beat, and fishing events

    Guide

    When field payment is required, verify the displayed access details before using Paid + done.

  4. 4

    For POA variants, record activity arrival, start, completion, passenger return, and outcome

    Guide
  5. 5

    Use Issue when reality differs from the selected Program

    Guide
  6. 6

    Complete the final return or outcome step required by the variant

    Guide

Who's involved

Guide

Records real field events and issues at the moment they happen.

Operations

Monitors progress and responds when the day differs from the plan.

What each person sees

Guide

The steps required by the selected variant, completed events, and Issue action.

Why: Keep the digital timeline aligned with field reality without adding fishing-only work to other variants.

Operations

Program progress, its variant, and the exceptions the guide made visible.

Why: Support the work without inventing completion.

The rule to remember

Complete only the timeline steps owned by the selected variant and only when the real event occurs; use Issue when reality differs.