01
Named-load coordination
Access can be tied to a specific customer relationship and load instead of broad tenant data.
- Scoped load relationship
- Approved carrier coordination
- Minimum necessary customer details
For brokers & 3PLs
Coordinate the load without taking over release authority.
Freight Passport is being designed to let brokers and 3PLs participate in a named-load workflow while the shipper retains the final custody decision.
Capability map
How this part of Freight Passport is structured.
02
Current carrier relationship
The workflow can keep visible which carrier and equipment relationship the customer approved for a load.
- Carrier and assignment context
- Evidence status
- Protected substitutions
03
Visible exceptions
A material change can become an attributable request instead of disappearing into email, phone, or chat history.
- Requested old and new values
- Actor and reason history
- Fresh evaluation required
04
Customer stays authoritative
Coordination does not grant customer release authority or a way to force a protected load green.
- Separate customer policy
- Separate release decision
- No self-issued cargo authority
Broker workflows, integrations, and broader service accounts are not represented as ready for use.
See it in context
Bring one brokered workflow into SHADOW.
Use one customer, one facility, one carrier relationship, and a small load set to review the coordination model before expanding.