Overview
Follow the CIS journey from creating the trip through assigning people and handing required work to Fishing.
CIS is Trailhead's operating record for a client trip. The name refers to both the area and the record it produces: each booked trip becomes "a CIS" the whole lodge can rely on. Use it to build the booking, itinerary, passenger context, assigned team, and required fishing work before the lodge begins delivery.
CIS operating journey
From booked trip to delivery-ready plan
- 01Operations
Create the CIS
Record the group, dates, lodge context, and trip-wide notes.
- 02Operations
Plan travel and lodge stays
Put arrivals, departures, stays, and responsibility handoffs in order.
- 03Operations
Add passengers and their needs
Confirm who is travelling and the preparation context relevant to the trip.
- 04Operations
Add the booking team
Assign guides or assistants with explicit roles and dates.
- 05Operations
Review and save the CIS
Confirm the complete trip before it becomes the operating reference.
- 06Trailhead
Notify newly assigned people
Create assignment visibility without approving a daily Program.
- 07Shared
Define required Fishing work
Identify the exact dates and groups that need Programs.
- 08Operations
Mark non-fishing days
Keep travel, transfer, and rest days out of false blockers.
The operating journey
- Create the CIS β Record the group, booking dates, lodge context, and trip-wide notes.
- Plan travel and stays β Keep arrival, departure, lodge stays, and responsibility handoffs in chronological order.
- Add passengers and needs β Confirm who is travelling and capture only the preparation context relevant to this trip.
- Add the booking team β Select the guides or assistants responsible for the CIS and confirm their roles and dates. This happens while creating the CIS and is confirmed during review.
- Review and save β Check the complete trip before it becomes the operating reference. Saving a new team creates assignment visibility and notifications; it does not approve a daily Program.
- Define required Fishing work β Make the exact dates and groups requiring Programs visible so Fishing can plan, execute, report, and close them.
- Mark non-fishing days β Keep intentional travel, transfer, and rest days visible without creating false missing-Program blockers.
Saving a CIS does not approve a Program
The CIS confirms the trip and its assigned people. Fishing still owns each daily Program, including planning, conflicts, execution, and reporting.
Start with the task in front of you
Create a CIS
Start a new client trip and establish its operating window.
Plan the itinerary
Add travel, lodge stays, and the handoffs between them.
Add passengers
Build the trip list and capture passenger-specific needs.
Review and save
Confirm the trip, team, and resulting assignment visibility.
Define required Fishing work
Turn trip demand into exact dates and groups needing Programs.
Mark non-fishing days
Keep travel and rest days out of missing-Program blockers.
Next: create a CIS.