TrailheadTrips & CISTrip Promise
TC-01Trip recordNo assistant eval · Coverage unknown

Create a CIS

A booked client trip needs one trusted record before detailed planning begins.

Track

Trip Promise

Phase

Trip record

Starts with

Booked trip outside CIS

Ends with

CIS shell ready for planning

You are here

TC-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

Operations has a confirmed group, operating window, and lodge context to record.

What starts it

A client trip is ready to enter Trailhead.

How it unfolds

  1. 1Operations

    Start a new CIS.

    Begin with the client trip, not a daily Program.

  2. 2Operations

    Enter the group, dates, size, FOC count, and lodge context.

    FOC is a commercial classification separate from participation type; an unknown historical value is never treated as zero.

  3. 3System

    Save the trip shell for detailed planning.

    Travel, stays, passengers, and services can now reference one trip.

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

The CIS establishes the trip promise; it does not execute the daily field plan.