TrailheadFishing OperationsProgram Planning
PL-03Exception

Resolve a Program Conflict

Let the best-ranked GC Lodge (the lodge's daily Guide Coordinator) of the lodges of the groups on a Beat resolve the shared conflict in mobile, with Head Guide as the final escalation.

Track

Program Planning

Phase

Exception

Starts with

A shared Beat conflict needs a human decision

Ends with

The current owner resolves the shared conflict or preserves its escalation

You are here

PL-03
  1. PL-01Choose the Program Variant
  2. PL-02Create the Contextual Program
  3. PL-03Resolve a Program Conflict

The situation

Each lodge starts the local day with one GC Lodge shared by every group there: the top-ranked working guide at the lodge, who accrues one USD 30 duty premium and sees GC Lodge in the app header and on their Program cards. Each group also has its own GC, who only assigns that group's guests. If more groups choose a Beat than it has places, including groups from two lodges on a shared or Transition Beat, the best-ranked coordinator of their lodges is notified, opens the banner before Calendar, compares the affected Programs, and either moves one Program, their own included, to a Beat its guide could choose or escalates the complete conflict to Head Guide.

What starts it

A shared Beat-capacity conflict blocks Programs of two or more groups on the same day.

How it unfolds

Guide CoordinatorHead GuideSystem
  1. 1

    Start one Guide Coordinator duty for each lodge

    System

    Choose the lowest rank number among active guides working at that lodge, snapshot the duty for the local day, and accrue USD 30 once for the guide and date. A Head Guide may also be selected.

  2. 2

    Open the conflict banner immediately before Calendar

    Guide Coordinator

    The banner shows the open count and opens one queue item per shared conflict; there is no conflict icon in the header.

  3. 3

    Compare the affected Programs and the Beats their guides could choose

    Guide Coordinator

    The stepper begins with no Program preselected and keeps FIE as non-binding decision support.

  4. 4

    Move one Program, their own included, to a verified available Beat

    Guide Coordinator
  5. 5

    Escalate the complete conflict with a reason

    Guide Coordinator
  6. 6

    Make the final decision on the escalated conflict

    Head Guide
  7. 7

    Recheck ownership, revision, source conflict, and destination capacity

    System

Who's involved

Guide Coordinator

Owns routine decisions for the conflicts where they are the best-ranked coordinator of the lodges of the groups on the Beat.

Head Guide

Makes the final human decision after the complete conflict is escalated, and decides conflicts where no lodge of those groups has a Guide Coordinator.

System

Assigns each lodge's daily duty from explicit guide ranking, accrues the premium once per guide and date, notifies whoever decides, and rechecks ownership and capacity before a change.

What each person sees

Guide Coordinator

The conflicts they decide, every affected Program with its lodge, the Beats each guide could choose, and the escalation action.

Why: Resolve routine conflicts in the app without hiding or duplicating the shared problem.

Head Guide

Complete conflicts escalated for a final decision, with their reason and prior context, and conflicts no group coordinator can decide.

Why: Act as the last escalation authority, not the default coordinator.

System

Explicit guide ranking, each group's daily duty owner, premium accrual, and current conflict revision.

Why: Keep assignment, compensation, authorization, and conflict mutation deterministic.

The rule to remember

The Guide Coordinator is a daily duty of each lodge, not a permanent company role. Resolve the existing shared conflict in mobile; escalate only to Head Guide and never create a second Program to bypass the blocker.