TrailheadFishing OperationsField Delivery and Evidence
FD-04AdaptNo assistant eval · Coverage unknown

Change the Program Beat After an Incident

Move the active Fishing Program to a safe same-lodge Beat while preserving the planned Beat and the reason for the change.

Track

Field Delivery and Evidence

Phase

Adapt

Starts with

An approved Fishing Program is in progress on its planned or current Beat

Ends with

The Program, timeline, draft report, and Operations view share one current Beat

You are here

FD-04
  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

After execution starts, an access closure, safety issue, weather, water conditions, client need, or another field incident makes the planned Beat unsuitable. The assigned guide selects an active Beat from the same lodge, records the motive, reviews the exact operational effects, and confirms the move. Trailhead keeps the planned Beat, updates the current Beat immediately, records the event, notifies Operations without waiting for approval, and makes the Fishing Report inherit the new Beat.

What starts it

A field incident requires the active Fishing Program to use a different Beat before its report is submitted.

How it unfolds

GuideOperationsSystem
  1. 1

    Recognize that the current field conditions require another Beat

    Guide
  2. 2

    Search and select an active alternative Beat from the same lodge

    Guide

    The current effective Beat is excluded; the original planned Beat remains recorded.

  3. 3

    Select the incident motive and add an optional note

    Guide

    Other requires a note; standard motives may include one when useful.

  4. 4

    Review the planned/current Beat, destination Beat, motive, and operational effects

    Guide
  5. 5

    Confirm the Beat change once

    Guide
  6. 6

    Update the current Beat, timeline, and linked draft report in one operation

    System
  7. 7

    Notify Operations of the recorded change without creating an approval gate

    System

Who's involved

Guide

Owns the immediate field decision and records why the active Program must move.

Operations

Receives the recorded change and follows the updated Program without approving it first.

System

Preserves planned context, applies one idempotent current-Beat change, and keeps report evidence consistent.

What each person sees

Guide

A searchable same-lodge Beat list, motive step, and exact current-to-new review.

Why: Adapt the active Program to field reality without creating a replacement Program or contradictory report.

Operations

The planned Beat, current Beat, incident motive, actor, time, and Program timeline event.

Why: Follow the operational change and respond when needed without delaying the guide for approval.

System

The Program execution state, assignment, same-lodge Beat eligibility, mutation identity, and report status.

Why: Reject stale or contradictory changes while keeping accepted field evidence aligned.

The rule to remember

Change the Beat only inside the assigned, approved, in-progress Fishing Program and before report submission; never create a replacement Program, select a report-only Beat, or wait for Operations approval when the field move is valid.