TrailheadInventory & GearDaily Client Gear
DG-04Return discrepancy branch

Daily Client Gear Issue

Something did not come back as expected. The guide reports what happened, but operations—not the field report—decides who is responsible.

Track

Daily Client Gear

Phase

Return discrepancy branch

Starts with

Return has a discrepancy

Ends with

Responsibility explicitly resolved

Product flow defined, walkthrough pending: the current product supports clean Return all gear, while item-level discrepancies and reconciliation still await their client-facing surfaces.

Before you start

Availability
Pending implementation of item-level return outcomes and reconciliation
Act as
The trip's guide and an Operations user with reconciliation access
Trip
A CIS with at least one daily gear item in Checked out status
Starting state
One item is damaged, lost, replaced, not issued, or otherwise different from the expected return
Evidence
The guide knows the field facts and can add notes, a client, or photos when available

Run the scenario

  1. 1GuidePlanned · Trailhead Mobile · CIS gear return

    Mark the affected item with its actual return outcome and add the known field context.

    Expected evidence

    The discrepancy shows the item, issue type, notes, and linked client when known without showing a charge.

  2. 2GuidePlanned · Trailhead Mobile · Gear return

    Submit the return with the item discrepancy.

    Expected evidence

    The issue becomes pending reconciliation and no guide or client charge is created.

  3. 3OperationsPlanned · Trailhead · Gear · Reconciliation

    Open the discrepancy, review the evidence, and choose client, guide, or operational responsibility.

    Expected evidence

    The selected path stays attached to the CIS and records operations as the decision-maker.

  4. 4GuidePlanned · Trailhead · Guide responsibility confirmation

    If guide responsibility is proposed, review and explicitly confirm it.

    Expected evidence

    A guide-account charge exists only after confirmation; an unconfirmed proposal remains open.

  5. 5AccountsPlanned journey · Trailhead · Accounts

    Review Accounts only after the responsibility path is completed.

    Expected evidence

    Accounts shows only a confirmed guide deduction, approved write-off, or other confirmed financial movement—not the raw issue report.

Scenario completed

Operations has resolved responsibility and only confirmed financial outcomes reach Accounts.

Return status
Expected back→Discrepancy reported
Responsibility
Unresolved→Client follow-up
Responsibility
Proposed for guide→Guide confirmed
Responsibility
Unresolved→Operational loss

If it does not match

  • If item-level issue choices are unavailable, do not complete a clean return; keep the physical discrepancy open for operations.
  • If a charge appears immediately after the guide reports the issue, stop: the report must reach reconciliation before any responsibility decision.
  • If the guide-responsibility charge exists without confirmation, leave the outcome unresolved and correct the confirmation step.
  • If Accounts shows the raw issue, confirm that only approved financial outcomes are being sent beyond reconciliation.