Skip to content

Operations platform

Northline Dispatch

A dispatch and exception console for a regional freight operator that had outgrown shared spreadsheets and radio updates.

Northline Freight · 2025

app.northline-dispatch.test

LIVE BOARD

Dispatch console

12 in transit

Assigned

38

Exceptions

4

Unassigned

6

LoadStatus

NL-2041

CHI → COL

On time

NL-2044

IND → CLE

Delayed

NL-2048

DTW → PIT

Assigned

Problem

What was breaking

Dispatchers were coordinating loads in a spreadsheet, a group chat, and a legacy tracking portal that nobody wanted to open. Status was always a conversation, never a system. When a trailer ran late, the only record was a thread of messages.

Solution

What we built

We built a dispatch application around loads, assets, and exceptions. Planners see a live board, drivers and partners update status through a simple interface, and every delay has an owner. Integrations pull location events instead of asking people to retype them.

Outcome

Northline now runs the day from one console. Handoffs between shifts are a board state, not a verbal briefing, and exception queues are reviewed instead of rediscovered.

Functionality

What the product does

  • Load board with filters for lane, status, and exception age
  • Asset and driver assignment with conflict warnings
  • Exception queue with reasons, owners, and timestamps
  • Inbound location events from existing tracking hardware
  • Shift notes so the next dispatcher inherits context

Stack

Technologies

  • Laravel
  • Vue
  • PostgreSQL
  • Redis
  • AWS

Related services

Next step

Have a system that needs to exist?

Tell us about the workflow, the constraint, and the people who will use the software. We will tell you whether a build is the right next step.