SHADOW pilot guide

Learn from one controlled handoff.

Use an approved controlled workflow to see what the system reports, examine the reasons, and compare them with the process your team already knows.

Before the exercise

Agree on the boundaries first.

The pilot owner coordinates readiness and approval. Participants should know what they are testing, who is reviewing it, and when to stop.

01

One agreed scenario

Choose a fictional pickup and the question you want to review. Use test loads, carriers, drivers, equipment, and evidence approved for this exercise.

02

Named participants

Confirm the pilot owner, invited users, organization, facility, and assigned roles. Each person uses their own account and completes required authentication.

03

A clear comparison

Agree on the expected result and how the customer’s existing process would handle the same scenario. A difference is something to investigate, not permission to act.

04

A person who can stop the test

Name the person responsible for pausing the exercise, recording a problem, and deciding when another test can be scheduled.

One controlled run

Observe, compare, and record.

Follow the scenario agreed with the pilot owner. If a step cannot be confirmed, pause and reconcile the result before continuing.

  1. 01 / Confirm

    Check the test context.

    Verify the environment, organization, facility, participants, and fictional load before starting. The pilot owner must confirm that the exercise is approved to run.

    Record the scenario and expected outcome.

  2. 02 / Observe

    Run the agreed SHADOW workflow.

    Use only the approved test scenario. Read the advisory result and its reasons alongside the customer’s existing process. Do not use the result to direct a real handoff.

    Record the result, reasons, and any missing information.

  3. 03 / Compare

    Review what the result means.

    Have the named reviewer compare the observed outcome with the agreed expectation. Identify unclear evidence, confusing steps, and any difference that needs investigation.

    Record the reviewer’s findings and unresolved questions.

  4. 04 / Close

    End the exercise deliberately.

    Sign out, retain only the approved test record, and assign an owner to each follow-up. A completed exercise does not approve another pilot or activate live operations.

    Record the outcome and the next approval needed.

Know when to pause.

Tell the named pilot owner what happened. Keep the test paused until the issue and the next step have been reviewed.

  • Real customer, shipment, identity, or payment data appears in the test.
  • The organization, facility, user, or role is different from the agreed scope.
  • A result is unclear, a required check fails, or the system becomes unavailable.
  • Anyone is asked to release real cargo or take a financial action from a SHADOW result.

Prepare for your part

Confirm your account and assigned role.

Invited participants can review the setup and access guides. Teams exploring a future pilot can discuss a single scenario with the pilot team.