Fleet & Shipment Operations Platform
Replaced spreadsheet dispatch and phone-tag updates with a live operations board for trucks, loads, and customer ETAs.
Problem statement
What was broken in the real operation
Reyan’s dispatch team ran daily operations across shared spreadsheets, WhatsApp threads, and driver phone calls. Load status was rarely trustworthy in real time—customers called for ETAs, and coordinators spent hours reconciling who picked up what, which trailer was free, and which exception had already been promised to a shipper.
A USA logistics operator moving freight across regional lanes. Growth meant more loads and drivers, but the ops stack stayed manual. Mistakes weren’t dramatic system outages—they were silent: double-assigned trucks, missed delivery windows, and no single source of truth when a driver went offline.
Operational challenges
- No shared live view of fleet availability vs. committed loads
- Status updates lived in chats and got lost between shifts
- Customer ETA answers depended on whoever answered the phone
- Exception handling (delay, partial pickup, re-route) had no audit trail
What Revilen did
Solution approach
We built an operations platform centered on dispatch: loads, drivers, and shipment events as first-class records. Status changes write once and fan out to internal boards and customer-facing updates—so the phone isn’t the system of record.
What we built
- Dispatch board with load → driver → trailer assignment
- Shipment timeline with timestamped status events
- Exception workflow for delays and re-routes with notes
- API hooks for future carrier / warehouse integrations
Systems delivered
Stack
Outcomes
What changed for Reyan Logistics USA
- Dispatchers stopped reconciling three spreadsheets every morning
- Customer ETA answers became consistent across the team
- Shift handoffs used the same live board instead of chat archaeology
- Leadership could see stuck loads without chasing coordinators