What rules define the Card filtering on the Dispatcher page

Modified on Thu, 26 Jun at 10:23 PM

Dispatcher Card Logic and Filtering Criteria

The Dispatcher Card applies specific filtering logic to surface only the most relevant container information for operational visibility and action. Each card is designed to highlight loads that meet predefined conditions, ensuring dispatchers can quickly identify exceptions, missing data, or time-sensitive actions.



Container Arriving On Vessel

  • Vessel ETA date must fall within the Default Date Range

  • Load Status must be Pending

  • Last Free Day (LFD) and Pickup Appointment (APT) should not exist

Released

  • All Containers on Vessel conditions must be true

  • Both Custom and Freight must be Released

On Hold

  • All Containers on Vessel conditions must be true

  • Either Custom or Freight must be On Hold




Containers Needing Pickup

  • Either Last Free Day (LFD) or Containers At Port conditions must be true

LFD

  • Load Status must be Pending or Available

  • LFD must exist within the Default Date Range

Pickup APT

  • Load Status must be Pending or Available

  • Pickup Appointment must exist within the Default Date Range


Containers Needing Delivery or Loading

  • Load Status must be any status from Pending to Arrived at Return

  • Delivery / Load Appointment must exist within the Default Date Range

  • Delivery / Load event in routing must not have a driver assigned

At Port

  • Load Status must be one of: Pending, Available, Dispatched, Enroute to Pickup, Arrived at Pickup

  • Delivery Appointment must exist within the Default Date Range

  • Delivery / Load event in routing must not have a driver assigned

In Yard

  • Load Status must be Dropped

  • Delivery Appointment must exist within the Default Date Range

  • Delivery / Load event in routing must not have a driver assigned


Containers Needing to Be Returned

  • Load Status must be Dropped

  • One of Cut Off, Return Day, or Return Appointment must exist within the Default Date Range

  • Return Container event in routing must not have a driver assigned

Ready

  • All Containers to Return conditions must be true

  • Container must be marked as Ready to Return

Not Ready

  • All Containers to Return conditions must be true

  • Container is marked as Not Ready to Return


Containers Dropped

  • Load Status Must be Dropped

In Yard

  • If current drop leg is Drop after Pull, appears only if Drop Location and Next Location are different locations

  • If current drop leg is Drop after Delivery, appears only if Drop Location and Previous Location are different locations

At Customer

  • If current drop leg is Drop after Pull, consider only if Drop Location and Next Location are the same

  • If current drop leg is Drop after Delivery, consider only if Drop Location and Previous Location are the same


Dispatched Loads


Load Status should be one of the statuses from Dispatched up to Before Completed (excluding Dropped status). The Dropped status will only be considered if the driver is assigned to that load.

Additionally, at least one of the following dates should fall within the Default Date Range:

  • LFD

  • Pickup APT

  • Delivery APT

  • Return APT

  • Cut Off

  • Return Day



Finished Loads

  • Load Status should be either Completed or Dropped.

  • If Completed, the Load Completed Date must be today's date.

  • If Dropped, the Load Delivered Date must be today's date.


This filtering logic helps prioritize containers that require attention, supports proactive logistics management, and reduces the risk of missed deadlines or compliance issues.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article