Skip to content

Custom Software

Atlas Freight

A dispatch and tracking platform replacing eleven spreadsheets.

Client
Atlas Freight (placeholder client)
Industry
Logistics
Year
2025
Services
Custom Software, Web Applications, Cloud & DevOps

Overview

A regional freight operator ran dispatch, driver assignment and customer updates across spreadsheets and phone calls. We replaced it with a single operations platform.

Technology

  • Next.js
  • TypeScript
  • Node.js
  • PostgreSQL
  • Redis
  • AWS

01 — Challenge

Challenge

Dispatchers coordinated 200+ daily loads through shared spreadsheets and a wall-mounted whiteboard. Customer status requests were answered by phoning the driver. Nothing was recorded against a load after it left the yard, so disputes about delivery times had no evidence behind them.

02 — Strategy

Strategy

We spent two weeks in the dispatch office mapping how loads actually move — including the exceptions that never appear in a process document. That produced a data model built around the load lifecycle rather than the spreadsheet columns, and a decision to ship dispatch first and customer visibility second, so the internal team stabilised before external users arrived.

03 — Solution

Solution

A dispatch console with drag-and-drop assignment and live capacity, a driver mobile view for status updates and proof of delivery, and a customer tracking portal fed from the same event stream. Every state change is written to an immutable event log, which became the source for both reporting and dispute resolution.

What we built

The parts that carry the workload.

  • 01

    Dispatch console

    Loads, drivers and vehicles on one board with conflict detection and capacity warnings before an assignment is confirmed.

  • 02

    Driver mobile view

    A lightweight offline-tolerant interface for status updates, photo proof of delivery and signature capture.

  • 03

    Customer tracking portal

    Shipment status, documents and estimated arrival, replacing the phone calls that consumed the operations team.

  • 04

    Event log and audit trail

    Every status change recorded with actor, timestamp and location — the evidence base for delivery disputes.

  • 05

    Operations reporting

    On-time performance, utilisation and lane profitability, produced automatically instead of by monthly export.

Screens

A look at the interface.

  • Dispatch board with live capacity
  • Driver status and proof of delivery
  • Customer shipment tracking

Results

What changed after launch.

Spreadsheets replaced
11 → 1
Status enquiry calls
−62%First quarter after the portal launch
Dispatch board load time
< 2sP95, full day of loads
Loads with an audit trail
100%

Figures shown are illustrative placeholders for this sample case study.

“They sat in our dispatch office before writing a line of code. It shows — the system handles the messy exceptions, which is the part every previous vendor ignored.”
Operations DirectorAtlas Freight (placeholder attribution)

Next case study

Verdant Organics

Subscription commerce rebuilt around checkout completion.

Let’s build

Have a project like this?

Tell us where you are now and what needs to be true in six months. We will map an approach and give you a realistic estimate.

Prefer email? info@saftasoft.site