Skip to content

Case 02 · A regional livestock hauler

Every load, signed for.

A regional livestock hauler replaced text-message dispatch with one system where yards order, dispatch fills, drivers deliver, and every head is counted and signed for at the gate.

Case02

  • About 10 customer yards
  • A roster of about 30 drivers
  • About 48 head a load
  • Upper Midwest to the Plains

Scale shown as ranges. Client not named.

01The problem

The week lived in text threads.

Yards ordered by text and phone. Dispatch held the week in its head and a group chat. Drivers carried paper bills of lading that came back creased, late or not at all.

When a count was disputed there was nothing to settle it: no record of head loaded against head delivered, no signature, no time stamp anyone trusted.

Drivers work in the cab and at the chute, often out of range. Whatever they use has to work offline and catch up later without losing the order of events.

02The data that comes out

What the system records, and what it is for.

Data producedDecision or check it enables
Orders becoming loads: a dispatch board in list, week and month views with double-booking guardsDispatch fills the week from yard orders instead of text threads
Stage and arrival time for both yards; exact position only for staffYards plan unloading without calling; driver location stays private outside dispatch
Head loaded against head delivered, a required reason for any difference, receiver, signature, frozen as a tamper-evident bill of ladingProof of delivery that settles the argument before it starts
Append-only load history with device time and server timeAn honest audit trail, even for actions taken offline
GPS trail and loaded milesRoute replay for disputes, and invoices built from what was actually driven
28-hour clock, document expiries, health and brand papers per loadCompliance kept on the load, not in a glovebox
Delivered loads, head hauled, on-time rate by driver and yardThe first operating view of the business

03Decisions it makes possible

The questions it answers.

01

Signed at the gate

The bill of lading freezes when the receiver signs, with the count and any reason for a difference.

Readout

Example data
Loaded
48 head
Delivered
48 head
Receiver
signed 14:22
BOL
frozen · tamper-evident

02

Arrival without a phone call

Both yards see the stage and an arrival time. Only dispatch sees the map.

Readout

Example data
Stage
In transit
ETA
16:40 local
Visible to
pickup yard, receiving yard

03

The clock on every load

Time on truck and the 28-hour limit tracked from the moment the first animal is loaded.

Readout

Example data
Loaded
06:05
On truck
7 h 40 m
Rest due by
10:05 next day

04

Invoices from what was driven

Loaded miles and stops come from the trail, so the invoice matches the trip.

Readout

Example data
Loaded miles
from trail
Stops
2
Invoice
drafted at delivery

04What we will measure

Results to follow after the first season.

The system has no season of operating history yet, so this page claims no time saved, errors reduced or money made. These are the measures we will report, published with the client's approval.

  1. 01Loads a month and share ordered by yardsPENDING
  2. 02On-time ratePENDING
  3. 03Order to driver assignedPENDING
  4. 04Share of loads with a signed BOLPENDING
  5. 05Head mismatch per 1,000 hauledPENDING
  6. 06Delivery to invoice timePENDING
  7. 07Disputes a monthPENDING

Start a project

Tell us what happens to your animals today.

Tell us about your operation and what you want to fix. We reply within 1 business day.

Or write directly

juastins@icloud.com

Replies within 1 business day. Call or email; what we agree is kept in writing, in your portal.