TrailheadInventory & GearDaily Client Gear
DG-01Trip requestNo assistant eval · Coverage unknown

Daily Client Gear Request

Tomorrow's clients need gear. Trailhead prepares the list from their CIS requirements, and the guide checks and submits the request for the trip.

Track

Daily Client Gear

Phase

Trip request

Starts with

CIS has passenger gear needs

Ends with

Gear request pending packing

You are here

DG-01
  1. DG-01Daily Client Gear Request
  2. DG-02Daily Client Gear Checkout
  3. DG-03Daily Client Gear Return

The situation

A guide is preparing for a CIS, trip day, or client group that needs company gear. The guest form records each passenger's equipment needs in the CIS. Trailhead pre-populates the trip request, but the guide still reviews and submits it so Inventory knows what to pack and check out.

What starts it

The guide opens the CIS gear request flow in Trailhead Mobile.

How it unfolds

GuideSystemInventoryOperations
  1. 1

    The guide opens the CIS or trip context

    Guide

    Starting from the trip keeps the request connected to the clients who will use the gear.

  2. 2

    Trailhead loads the passenger equipment needs from the CIS

    System

    Each guest's form answers update the corresponding passenger requirements that feed the draft request.

  3. 3

    The guide reviews the pre-populated items, sizes, and quantities

    Guide

    The guide checks that the draft matches the clients and resolves missing or incorrect gear before submission instead of rebuilding the request from zero.

  4. 4

    The guide reviews known replacement values

    Guide

    These values explain what the gear is worth; they do not create a charge or decide responsibility.

  5. 5

    The guide submits the trip gear request

    Guide

    This is the key moment: guest or office-entered needs do not bypass the guide; the reviewed gear becomes a visible packing request tied to this CIS or trip.

  6. 6

    Inventory and operations receive the request

    Inventory

    Inventory can now prepare the physical gear while operations sees the trip's pending gear work.

Who's involved

Guide

Checks the pre-populated client gear, resolves any practical exception, and sends the trip request to Inventory.

System

Builds the draft request from guest-form equipment needs stored per passenger in the CIS.

Inventory

Receives a trip-specific packing request rather than a permanent guide assignment.

Operations

Tracks whether the trip gear is pending, packed, or checked out.

What each person sees

Guide

A pre-populated request with passenger, item, size, quantity, and known replacement values inside the CIS.

Why: Check what the clients need and remain responsible for submitting the trip request.

Inventory

A trip-specific list of items and quantities that needs packing.

Why: Prepare the right physical gear for the right trip.

Operations

The trip's daily gear moving from pending toward packed and checked out.

Why: Know whether gear readiness could block the trip.

The rule to remember

Guest-form requirements pre-populate the draft; the guide reviews, submits, and may edit it only before checkout, while physical custody remains the next journey.