Skip to content
SummitstoneGroup

●Concept 08 · Regional freight

Meridian Freight

Load intake, dispatch and billing, connected

A 40-truck carrier running Ontario and Quebec lanes, booking loads from emailed PDFs and billing from paper. The concept: read rate confirmations automatically, give dispatch one live board, and invoice the day a load delivers.

Dispatch board: every load and truck in one place, with positions from the ELD system the trucks already carry.

Client
Meridian Freight (fictional)
Industry
Regional trucking, 40 trucks
Users
Dispatch, customer service, billing
Scope
Document AI, dispatch board, integrations, billing automation

The problem

The trucks were fast. The paperwork wasn’t.

Every load started as an email with a PDF rate confirmation that a dispatcher retyped. Customers phoned for updates. Proof of delivery arrived as photos in a text thread, so invoices went out days after delivery, and time trucks spent waiting at docks was rarely billed.

  • Each rate confirmation retyped by hand, field by field
  • Load status lived on a whiteboard and in dispatchers’ heads
  • Customers calling all day to ask where their truck is
  • Invoices waiting days on paperwork
  • Detention at docks happening, but rarely billed

The solution

Read the email. Track the truck. Bill on delivery.

Nothing gets replaced that already works. We’d connect the dispatch inbox, the trucks’ ELD/GPS system and the accounting software, and build the layer between them. Software does the copying; people approve what matters.

  • Rate confirmations read by AI into draft loads a dispatcher approves
  • One dispatch board with live truck positions
  • Customers emailed automatically at pickup and delivery
  • Proof of delivery matched to its load, invoice drafted the same day
  • Detention calculated from dock arrival and departure times

Before and after

One load, from email to invoice.

Today

  1. 01Rate confirmation PDF arrives by emailManual
  2. 02Dispatcher retypes it into a spreadsheetManual
  3. 03Truck assigned by phone, whiteboard updatedManual
  4. 04Customer calls for status; dispatch calls the driverManual
  5. 05Driver texts a photo of the signed delivery receiptManual
  6. 06Billing chases paperwork, types the invoice days laterManual

With the system

  1. 01Rate confirmation read; draft load createdAutomatic
  2. 02Dispatcher checks highlighted fields and books itDispatcher
  3. 03Truck assigned on the board; load sent to the driver’s ELD appDispatcher
  4. 04Customer emailed at pickup and delivery from GPSAutomatic
  5. 05Delivery receipt uploaded and matched to the loadAutomatic
  6. 06Invoice with detention drafted; billing approves and sendsBilling

How it fits together

It sits between the tools Meridian already pays for.

Connects to

  • Dispatch inbox (Outlook or Gmail)
  • ELD & GPS provider (e.g. Samsara, Motive)
  • Rate confirmations and delivery receipts
  • Customer and lane rate list

What we build

Meridian Ops

  • Document AI
  • Load records
  • Dispatch board
  • Rules & notifications

Delivers to

  • Accounting (e.g. QuickBooks Online)
  • Customer status emails
  • Load details in the driver’s ELD app
  • Weekly lane and margin report

Load intake

From emailed PDF to draft load, without retyping.

The AI reads each rate confirmation and fills in shipper, consignee, times, weight and rate, and highlights anything it isn’t sure of. Nothing is booked until a dispatcher approves it.

Customer updates

Customers know before they think to call.

When a truck leaves the shipper or reaches the consignee, the customer gets an email with the status and ETA. Delays go to dispatch first, so a person decides what to tell the customer.

Billing

Invoiced the day it delivers, detention included.

Uploaded delivery receipts are matched to their load. The invoice is drafted in the accounting system, with detention worked out from the times the truck arrived at and left the dock. Billing reviews and sends.

Phased rollout

  1. 01

    Phase 1 · Intake

    Rate-confirmation reading and the dispatch board, with dispatchers approving every load.

  2. 02

    Phase 2 · Tracking

    ELD connection, pickup and delivery emails, and late-risk alerts.

  3. 03

    Phase 3 · Billing

    Delivery-receipt matching, detention rules and invoice drafts in accounting.

How we’d measure it

  • Minutes from rate confirmation to booked load
  • Days from delivery to invoice sent
  • Detention hours billed vs. recorded
  • Inbound status calls per week

Concept project. Meridian Freight is a fictional company. Products named are examples of systems this would connect to; all data is illustrative.

Project notes

Meridian Freight

A quote-to-dispatch operations platform concept for a regional carrier: customer portal, dispatch board, automated follow-up and an owner dashboard.

Concept 08A fictional company created to demonstrate our approach. Not a client engagement, and no results are claimed.

What the concept covers
  • Customer quote & tracking portal
  • Dispatch board
  • Quote approval and follow-up automation
  • Owner dashboard
Built with
  • Next.js
  • TypeScript
  • PostgreSQL
  • Event-driven automation
Designed for
  • Shippers
  • Warehouse managers
  • Ops leads

Next concept

Veld Climate

Property · Energy data platform