TrailheadTrips & CISDelivery Handoff
DH-01Fishing demandNo assistant eval · Coverage unknown

Define Required Fishing Work

Fishing needs exact trip demand, not a vague count of missing work.

Track

Delivery Handoff

Phase

Fishing demand

Starts with

Trip demand not classified

Ends with

Exact required work visible to Fishing

You are here

DH-01
  1. TC-01Create a CIS
  2. IT-01Plan Arrival and Departure
  3. IT-02Build the Lodge Itinerary
  4. PS-01Add Passengers
  5. PS-02Capture Passenger Needs
  6. TC-02Review and Save the CIS
  7. DH-01Define Required Fishing Work
  8. DH-02Mark Non-fishing Days
  9. CT-01Find and Add a Returning Client
  10. CT-02Link an Invoice
  11. CT-03View or Export the CIS Document

The situation

A saved CIS contains dates and groups that require fishing delivery.

What starts it

Operations reviews what the confirmed trip requires from Fishing.

How it unfolds

  1. 1Operations

    Review the trip dates, groups, lodge, and assigned team.

    Start from the confirmed CIS promise.

  2. 2Operations

    Identify each date and client group requiring fishing delivery.

    Separate work when groups or teams need distinct Programs.

  3. 3System

    Make missing or changed demand visible to Fishing.

    Fishing can now create or adjust the exact Programs.

What each person sees

Operations

The current CIS state and the exact details that still need attention.

Why: Make the next responsibility clear without duplicating ownership.

System

The current CIS state and the exact details that still need attention.

Why: Keep one current operating reference.

The rule to remember

CIS explains why work is required; Fishing owns each daily Program, report, and outcome.