Skip to main content

Why can't I assign a driver to a route block?

If you’re unable to assign a driver to a route block in Laminar Copilot, there are a few common reasons the assignment may be restricted.

Updated over 2 months ago

Driver has a scheduling conflict

The driver may already be assigned to a different route block that overlaps with the one you're trying to assign.

  • Use the Driver Breakdown page to check if the driver is already scheduled during that time.

  • Copilot will block overlapping assignments to avoid scheduling conflicts.

Driver is unavailable

The driver may be marked as unavailable due to:

  • Time Off Blocks (visible in the Breakdown and Time Off Tracker views)

  • Unavailability status marked in the Driver Roster

Drivers marked as unavailable during the block’s timeframe cannot be assigned.

Driver exceeds DOT 60/70 Rule

Laminar Copilot enforces DOT hour limits using the 60/70 Rule:

  • No more than 60 hours of work in any 7-day period

  • No more than 70 hours of work in any 8-day period

If assigning the block would cause the driver to exceed these limits, Copilot will prevent the assignment.

  • Check the driver's total hours in the Driver Breakdown view.

Driver does not have the correct Route Type assigned

Each route block is associated with a Route Type, and drivers must have that same Route Type assigned in the Driver Roster to be eligible.

  • If the Route Type doesn’t match, Copilot will block the assignment.

  • To override this, you can check the Exception box during the assignment process to allow the driver to be assigned regardless of Route Type.

Driver is assigned to a route in the following week

Please check future routes to see if the driver is assigned to routes in future weeks, making them unavailable to take a route in the current week.

None of the above

If none of the above apply and you still can’t assign the driver, contact our Support Team through Amazon Chime for assistance.

Did this answer your question?