Move Event Types

Move event types define driver actions at locations during moves. Each event type specifies the state of the equipment before arrival and after departure.

After reading this article you will understand:

The origin, intermediate, and destination event categories for shipment moves
Intermediate event subcategories: yard, cross-dock, stopoff, and equipment handling events
Equipment rules for hooks, drops, pickups, and delivers
How equipment state transitions between events
Virtual and billing events including non-routed and bobtail event types
The purpose and usage of non-shipment events prefixed with "ns-"
Event-specific fields that provide additional context based on shipment and event types
Guidelines for proper event sequencing and selection

Overview

Events are categorized by their role in the shipment workflow:

Origin Events: Initiate equipment or freight movement at the shipment origin
Intermediate Events: Handle equipment at stopoff locations, yards, and cross-docks
Destination Events: Complete delivery or return at the final location
Non-Shipment Events: Track driver activities unrelated to specific shipments

Equipment Rules:

All hooks/drops require a tractor and hookable equipment
All pickups/delivers require loadable equipment (truck, container on chassis, or trailer)
Tractor or truck must exist before all events (except ns-new-trip) and the tractor or truck remains after all events (except ns-end-trip)

Origin Events

Origin events mark the beginning of shipment work at the origin site. The driver arrives ready to obtain equipment or freight and departs with loaded equipment.

hook-origin

The hook-origin event is used when a loaded container sitting on top of a chassis, or a loaded trailer, is being picked up at the origination site on the shipment. Usually this is a customer loading dock, rail, or terminal. The event assumes that the driver is using a tractor to do the hook and indicates the beginning of a loaded leg in move.

Equipment Before: Tractor only
Equipment After: Tractor + loaded container on chassis or trailer

mount-origin

The mount-origin event is used when a loaded container is being mounted onto a bare chassis at the origination site on the shipment. Usually this is a customer loading dock, rail, or terminal. The event assumes that the driver is using a tractor already pulling a chassis to do the mount and indicates the beginning of a loaded leg in a container move.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor + loaded container on chassis

pickup-origin

The pickup-origin event is used when freight is being loaded into a trailer or container at the origination site on the shipment. Usually this is a customer loading dock, rail, or terminal. The event assumes that the driver is using a tractor pulling a container mounted onto a chassis, or trailer or a truck to do the pickup and indicates the beginning of a loaded leg in a move.

Equipment Before: Tractor or truck + empty or less than loaded (LTL) trailer or container on chassis
Equipment After: Tractor or truck + loaded trailer or container on chassis

Intermediate Events

Intermediate events occur at locations between origin and destination, including yards, cross-docks, and stopoff sites.

Yard Events

hook-yard

The hook-yard event is used when a container on a chassis or trailer is being picked up from a yard location. The event assumes that the driver is using a tractor to do the hook. The equipment being picked up may be loaded or empty.

Equipment Before: Tractor only
Equipment After: Tractor + container on chassis or trailer (loaded or empty)

drop-yard

The drop-yard event is used when a container on a chassis or trailer is being dropped off at a yard location. The event assumes that the driver is using a tractor to do the drop. The equipment being dropped off may be loaded or empty.

Equipment Before: Tractor + container on chassis or trailer (loaded or empty)
Equipment After: Tractor only

Cross-Dock Events

pickup-crossdock

The pickup-crossdock event is used when freight is being loaded into a trailer or container at a cross-dock location. Usually this is a freight consolidation facility. The event assumes that the driver is using a tractor pulling a container mounted onto a chassis, or trailer, or a truck to do the pickup. This event indicates the beginning of a loaded leg in a move.

Equipment Before: Tractor or truck + empty or less than loaded (LTL) trailer or container on chassis
Equipment After: Tractor or truck + loaded trailer or container on chassis

deliver-crossdock

The deliver-crossdock event is used when freight is being unloaded from a trailer or container at a cross-dock location. Usually this is a freight consolidation facility. The event assumes that the driver is using a tractor pulling a container mounted onto a chassis, or trailer, or a truck to do the delivery. This event indicates the end of a loaded leg in a move.

Equipment Before: Tractor or truck + loaded trailer or container on chassis
Equipment After: Tractor or truck + empty or less than loaded (LTL) trailer or container on chassis

Stopoff Events

pickup-stopoff

The pickup-stopoff event is used when freight is being loaded into a trailer or container at a site other than the origin on the shipment. Usually this is an intermediate site location. The event assumes that the driver is using a tractor pulling a container mounted onto chassis, or trailer, or a truck to do the pickup. This event indicates additional freight is being added to an already partially loaded move.

Equipment Before: Tractor or truck + less than loaded (LTL) trailer or container on chassis
Equipment After: Tractor or truck + loaded trailer or container on chassis

deliver-stopoff

The deliver-stopoff event is used when freight is being unloaded from a trailer or container at a site other than the destination on the shipment. Usually this is an intermediate site location. The event assumes that the driver is using a tractor pulling a container mounted onto chassis, or trailer, or a truck to do the delivery. This event indicates some freight is being removed from a loaded move before the final leg of the move.

Equipment Before: Tractor or truck + loaded trailer or container on chassis
Equipment After: Tractor or truck + less than loaded (LTL) trailer or container on chassis

hook-stopoff

The hook-stopoff event is used when a second or third container on a chassis or trailer is being picked up from a site other than the origin location. The event assumes that the driver is using a tractor to do the hook. The equipment being picked up may be loaded or empty. This event indicates that additional equipment is being added to the move before the final leg of the move.

Equipment Before: Tractor already pulling container on chassis or trailer
Equipment After: Tractor + multiple containers on chassis or trailers

drop-stopoff

The drop-stopoff event is used when a container on a chassis or trailer is being dropped off at a site other than the destination location. The event assumes that the driver is using a tractor to do the drop. The equipment being dropped off may be loaded or empty and the driver may be dropping off one of multiple containers or trailers. This event indicates that some equipment is being removed from the move before the final leg of the move.

Equipment Before: Tractor + containers on chassis or trailers
Equipment After: Tractor only or tractor + remaining containers on chassis or trailers

scale-stopoff

The scale-stopoff event is used when the driver stops at a weigh station or scale house during the shipment move. No equipment changes occur during this event. This event indicates that the shipment is being weighed or inspected without any change to the equipment configuration.

Equipment Before: Any equipment
Equipment After: Same equipment

Equipment Handling Events

hook-chassis

The hook-chassis event is used to pick up a bare chassis before mounting a container. The event assumes that the driver is using a tractor to do the hook. This event indicates that the driver is obtaining a chassis to prepare for mounting a container or only to reposition the chassis.

Equipment Before: Tractor only
Equipment After: Tractor + bare chassis

drop-chassis

The drop-chassis event is used to drop off a bare chassis after dismounting a container. The event assumes that the driver is using a tractor to do the drop. This event indicates that the driver is leaving the chassis behind after removing a container or only to reposition the chassis.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor only

hook-empty

The hook-empty event is used to pick up an empty container on a chassis or trailer. The event assumes that the driver is using a tractor to do the hook. This event indicates that the driver is starting an empty leg of a move.

Equipment Before: Tractor only
Equipment After: Tractor + empty container on chassis or trailer

drop-empty

The drop-empty event is used to drop off an empty container on a chassis or trailer. The event assumes that the driver is using a tractor to do the drop. This event indicates that the driver is completing an empty leg of a move.

Equipment Before: Tractor + empty container on chassis or trailer
Equipment After: Tractor only

hook-loaded

The hook-loaded event is used to pick up a loaded container on a chassis or trailer. The event assumes that the driver is using a tractor to do the hook. This event indicates that the driver is starting a loaded leg of a move.

Equipment Before: Tractor only
Equipment After: Tractor + loaded container on chassis or trailer

drop-loaded

The drop-loaded event is used to drop off a loaded container on a chassis or trailer. The event assumes that the driver is using a tractor to do the drop. This event indicates that the driver is completing a loaded leg of a move.

Equipment Before: Tractor + loaded container on chassis or trailer
Equipment After: Tractor only

mount-empty

The mount-empty event is used to mount an empty container onto a bare chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the mount and indicates the beginning of an empty leg in a container move.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor + empty container on chassis

mount-loaded

The mount-loaded event is used to mount a loaded container onto a bare chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the mount and indicates the beginning of a loaded leg in a container move.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor + loaded container on chassis

dismount-empty

The dismount-empty event is used to remove an empty container from a chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the dismount and indicates the end of an empty leg in a container move.

Equipment Before: Tractor + empty container on chassis
Equipment After: Tractor + bare chassis

dismount-loaded

The dismount-loaded event is used to remove a loaded container from a chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the dismount and indicates the end of a loaded leg in a container move.

Equipment Before: Tractor + loaded container on chassis
Equipment After: Tractor + bare chassis

Destination Events

Destination events complete the shipment work at the final destination. The driver arrives with loaded equipment and departs with empty equipment or no equipment.

drop-destination

The drop-destination event is used when a loaded container sitting on top of a chassis, or a loaded trailer, is being dropped off at the final destination site on the shipment. Usually this is a customer unloading dock, rail, or terminal. The event assumes that the driver is using a tractor to do the drop and indicates the end of a loaded leg in move.

Equipment Before: Tractor + loaded container on chassis or trailer
Equipment After: Tractor only

deliver-destination

The deliver-destination event is used when freight is being unloaded from a trailer or container at the final destination site on the shipment. Usually this is a customer unloading dock, rail, or terminal. The event assumes that the driver is using a tractor pulling a container mounted onto a chassis, or trailer, or a truck to do the delivery. This event indicates the end of a loaded leg in a move.

Equipment Before: Tractor or truck + loaded trailer or container on chassis
Equipment After: Tractor or truck + empty trailer or container on chassis

dismount-destination

The dismount-destination event is used to remove a container from a chassis at the final destination site on the shipment. The event assumes that the driver is using a tractor already pulling a chassis to do the dismount and indicates the end of a loaded leg in a container move.

Equipment Before: Tractor + loaded container on chassis
Equipment After: Tractor + bare chassis

Virtual and Billing Events

Virtual and billing events represent activities on a shipment itinerary that may not correspond to actual physical driver actions but are necessary for accurate billing, customer transparency, or representing logistical optimizations. These events help reconcile the difference between what the customer is billed for versus how the work was physically completed.

Non-Routed Events

Non-routed events are virtual placeholders representing equipment/freight movements without driver action. Used for street-turns, cross-dock warehouse transfers, and billing alignment where customer invoicing differs from physical logistics. Typically have no driver, times, or equipment assigned.

hook-non-routed

The hook-non-routed event is used to represent a virtual pickup of equipment that is street-turned to an export or from an import shipment rather than physically picked up by the driver. The event is assumed to have never occurred and may be used to represent optimizations from equipment reuse or as placeholders for customer billing purposes. This event indicates the beginning of a move that would have occurred if the equipment hadn't been street-turned.

Equipment Before: None or varies
Equipment After: None or varies

drop-non-routed

The drop-non-routed event is used to represent a virtual drop of equipment that is street-turned to an export or from an import shipment rather than physically dropped by the driver. The event is assumed to have never occurred and may be used to represent optimizations from equipment reuse or as placeholders for customer billing purposes. This event indicates the end of a move that would have occurred if the equipment hadn't been street-turned.

Equipment Before: None or varies
Equipment After: None or varies

pickup-non-routed

The pickup-non-routed event is used to represent freight transfer by non-driver personnel at cross-dock facilities. The event is assumed to be handled by warehouse workers and may be used as placeholders for customer billing purposes. This event indicates movement of freight at a location by non-driver personnel.

Equipment Before: None or varies
Equipment After: None or varies

deliver-non-routed

The deliver-non-routed event is used to represent freight transfer by non-driver personnel at cross-dock facilities. The event is assumed to be handled by warehouse workers and may be used as placeholders for customer billing purposes. This event indicates movement of freight at a location by non-driver personnel.

Equipment Before: None or varies
Equipment After: None or varies

Street-turn examples:

Import empty return: drop-non-routed → Export: hook-non-routed. Driver reuses empty directly; both shipments show complete itineraries for billing.

Cross-dock example:

Move 1: pickup-origin → deliver-crossdock Warehouse: deliver-non-routed → pickup-non-routed Move 2: pickup-crossdock → deliver-destination

Bobtail Events

Bobtail events track tractor-only movements on a shipment itinerary. Unlike non-shipment bobtail events (ns-bobtail), these are billable to the customer and represent work completed as part of fulfilling the shipment.

hook-bobtail

The hook-bobtail event is used when a driver departs a location with only the tractor, without any attached equipment. The event is assumed to be billable on the shipment. This event indicates the start of a leg in a move where the driver is moving without any load.

Equipment Before: Tractor only
Equipment After: Tractor only

drop-bobtail

The drop-bobtail event is used when a driver arrives at a location with only the tractor, without any attached equipment. The event is assumed to be billable on the shipment. This event indicates the end of a leg in a move where the driver is moving without any load.

Equipment Before: Tractor only
Equipment After: Tractor only

Distinction: Shipment bobtails are billable to customer and recorded on itinerary. Non-shipment bobtails (ns-bobtail) are for driver pay only and represent internal logistics efficiency.

Non-Shipment Events

Non-shipment events track driver activities that are not tied to specific shipment orders. These events help manage driver schedules, equipment movements, and operational activities. They are prefixed with "ns-" to distinguish them from shipment events.

ns-new-trip

The ns-new-trip event is used when a driver begins a new trip by entering their vehicle. The event assumes that the driver is starting fresh without any prior equipment. This event indicates the beginning of a driver's shift or trip.

Equipment Before: None
Equipment After: Tractor or truck

ns-end-trip

The ns-end-trip event is used when a driver ends their trip by exiting their vehicle. The event assumes that the driver is leaving behind any equipment they were using. This event indicates the conclusion of a driver's shift or trip.

Equipment Before: Tractor or truck
Equipment After: None

ns-bobtail

The ns-bobtail event is used when a driver is moving without any attached equipment. The event assumes that the driver is using only the tractor for internal logistics purposes. This event indicates that the driver is traveling without any load.

Equipment Before: Tractor only
Equipment After: Tractor only

ns-hook-chassis

The ns-hook-chassis event is used when a driver picks up a bare chassis to prepare for mounting a container or to reposition the chassis. The event assumes that the driver is using a tractor to do the hook and does not need to be billable on a shipment. This event indicates that the driver is obtaining a chassis.

Equipment Before: Tractor only
Equipment After: Tractor + bare chassis

ns-drop-chassis

The ns-drop-chassis event is used when a driver drops off a bare chassis after dismounting a container or to reposition the chassis. The event assumes that the driver is using a tractor to do the drop and does not need to be billable on a shipment. This event indicates that the driver is leaving the chassis behind.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor only

ns-hook-container

The ns-hook-container event is used when a driver picks up a container on a chassis. The event assumes that the driver is using a tractor to do the hook and does not need to be billable on a shipment. This event indicates that the driver is obtaining a container on chassis.

Equipment Before: Tractor only
Equipment After: Tractor + container on chassis

ns-drop-container

The ns-drop-container event is used when a driver drops off a container on a chassis. The event assumes that the driver is using a tractor to do the drop and does not need to be billable on a shipment. This event indicates that the driver is leaving the container on chassis behind.

Equipment Before: Tractor + container on chassis
Equipment After: Tractor only

ns-hook-trailer

The ns-hook-trailer event is used when a driver picks up a trailer. The event assumes that the driver is using a tractor to do the hook and does not need to be billable on a shipment. This event indicates that the driver is obtaining a trailer.

Equipment Before: Tractor only
Equipment After: Tractor + trailer (loaded or empty)

ns-drop-trailer

The ns-drop-trailer event is used when a driver drops off a trailer. The event assumes that the driver is using a tractor to do the drop and does not need to be billable on a shipment. This event indicates that the driver is leaving the trailer behind.

Equipment Before: Tractor + trailer (loaded or empty)
Equipment After: Tractor only

ns-hook-unknown

The ns-hook-unknown event is used when a driver picks up equipment of unspecified type. The event assumes that the driver is using a tractor to do the hook and does not need to be billable on a shipment. This event indicates that the driver is obtaining equipment without specifying its type.

Equipment Before: Tractor only
Equipment After: Tractor + undefined equipment

ns-drop-unknown

The ns-drop-unknown event is used when a driver drops off equipment of unspecified type. The event assumes that the driver is using a tractor to do the drop and does not need to be billable on a shipment. This event indicates that the driver is leaving behind equipment without specifying its type.

Equipment Before: Tractor + undefined equipment
Equipment After: Tractor only

ns-mount-container

The ns-mount-container event is used when a driver mounts a container onto a bare chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the mount and does not need to be billable on a shipment. This event indicates that the driver is mounting a container onto chassis.

Equipment Before: Tractor + bare chassis
Equipment After: Tractor + container on chassis

ns-dismount-container

The ns-dismount-container event is used when a driver removes a container from a chassis. The event assumes that the driver is using a tractor already pulling a chassis to do the dismount and does not need to be billable on a shipment. This event indicates that the driver is removing a container from chassis.

Equipment Before: Tractor + container on chassis
Equipment After: Tractor + bare chassis

ns-misc

The ns-misc event is used to record miscellaneous driver activities such as breaks, fuel stops, or other operational tasks that do not involve specific equipment changes. The event assumes that the driver may have any equipment configuration before and after the event.

Equipment Before: Any
Equipment After: Any

Event Structure

Events include common fields like type, site, and times, but depending on the shipment type and event type, additional fields may be present to provide context-specific information. The table below shows which fields apply to which event types across different shipment scenarios.

Pickup By (`pickupBy`)

The latest possible ISO datetime for the pickup to occur without incurring a delay or penalty in the shipment process.

{
  "type": "hook-origin",
  "site": { ... },
  "pickupBy": "2020-02-27T15:00:00",
  // other common event fields...
}

Event Type	Export	One-Way
hook-origin	✓	✓
pickup-origin	✓	✓
mount-origin	✓	✓

Note: More event-specific fields to be supported in the future.

Tip: If the GET or PUT response returns an optional field like pickupBy, then it is supported for that event type. Field support is dynamically determined based on the actual API response.

Usage Guidelines

Event Sequencing

Events must be ordered logically within a move. Equipment state after one event must match the state expected before the next event.

Valid:

hook-origin → drop-destination → hook-empty → drop-empty

Invalid:

hook-origin → drop-chassis → dismount-destination

Event Type Selection

Choose event types based on:

Location type: Use yard, cross-dock, or stopoff events at appropriate location types
Equipment type: Distinguish between containers (mount/dismount) and trailers (hook/drop only)
Shipment role: Use origin/destination events at shipment endpoints, intermediate events elsewhere
Driver involvement: Use deliver/pickup when driver stays for loading/unloading, drop/hook when driver leaves equipment

Virtual Event Usage

Use non-routed events when:

Equipment is street-turned between shipments
Warehouse workers handle freight transfers at cross-dock facilities
Customer invoicing requires visibility into movements being paid for
Moves need to appear complete while actual work was delegated elsewhere

Non-Shipment Event Usage

Use non-shipment events to:

Track complete driver shifts with ns-new-trip and ns-end-trip
Plan equipment movements between shipments
Record breaks, fuel stops, and other operational activities with ns-misc
Manage driver schedules when no shipment work is assigned

Conclusion

You now understand the origin, intermediate, and destination event categories that structure shipment moves, along with the four intermediate subcategories: yard events, cross-dock events, stopoff events, and equipment handling events. You've learned the equipment rules that govern hooks, drops, pickups, and delivers, and how equipment state transitions between events, ensuring logical sequencing throughout a move. Virtual and billing events, including non-routed and bobtail event types, allow you to reconcile operational efficiency with billing requirements and customer visibility. Non-shipment events prefixed with "ns-" enable tracking of driver activities outside specific shipment contexts. You've also learned about event-specific fields that provide additional context based on shipment and event types. Finally, the guidelines for proper event sequencing and selection ensure accurate itinerary planning based on location type, equipment type, shipment role, and driver involvement.