Dispatch operations
A command center for the loads in motion, from intake through exceptions.
- Jobs board and job detail
- Driver and vehicle assignment
- Inbound load intake by SMS and voice
Live freight operations platform
Vigil
A freight operations platform connecting dispatch, driver execution, shipment visibility, documents, and exceptions in one controlled workflow.
Built for small and medium-sized carriers replacing fragmented calls, texts, spreadsheets, and manually rebuilt paperwork.
- Live in production
- In active use by an Atlanta carrier
- Dispatcher and driver workflows
- Automated logistics documents
- Carrier-scoped access controls
The operating problem
The hard part is not moving freight. It is coordinating everything around it.
Carriers lose time to coordination across people, roles, jobs, documents, exceptions, and customer communication. When that coordination lives in message threads and someone’s memory, it cannot scale, transfer to a new hire, or be produced on request.
01
Fragmented dispatch coordination
Assignments, status updates, and exceptions travel through calls, texts, and spreadsheets, so the operating picture lives in fragments rather than one place.
02
Limited operational visibility
Answering where a load actually stands means calling the driver, and the answer is not recorded anywhere afterwards.
03
Repeated administrative work
Bills of lading, rate confirmations, and delivery orders get rebuilt by hand for every load, from data the operation already has.
Vigil in action
One job, from intake to operational record.
-
01 Dispatch
Job intake
-
02 Dispatch
Assignment
-
03 Driver
Driver execution
-
04 Driver
Pickup and proof
-
05 Driver
In-transit status
-
06 Driver
Delivery
-
07 Dispatch
Documents and billing
-
08 Platform
Operational record
Core product surfaces
Four surfaces, one operating loop.
Driver execution
A focused mobile workflow for the load a driver is actually running.
- Step-by-step status check-in
- Pickup and delivery proof capture
- Pre-trip, chain of custody, incidents
Documents and communications
Paperwork generated from the job record rather than rebuilt by hand.
- Bill of lading and delivery order
- Customer and driver rate confirmations
- Invoices, packets, and notifications
Carrier platform
Carrier-scoped, tenant-aware architecture with role-appropriate access.
- Carrier-specific workspaces
- Role-aware dispatcher, driver, and admin access
- Configurable carrier branding
Capability spotlight
Documents generated from the operating record.
A load already contains everything its paperwork needs. Vigil converts the job record into the documents the operation has to produce, instead of asking a dispatcher to rebuild them by hand for every load.
Documents carry the carrier’s branding, customer rates stay separate from driver pay, and each document keeps a durable record of what was generated and what was sent.
- Bill of lading
- Customer rate confirmation
- Driver rate confirmation
- Delivery order
- Invoices
- Document packet delivery
Platform design
Built as a carrier platform, not a single deployment.
Vigil is built on a carrier-scoped, tenant-aware architecture. It is structured around carrier-specific operational workspaces, with users, records, documents, and permissions scoped to the appropriate carrier. Dispatchers and drivers get role-appropriate experiences.
That structure is designed to support additional carrier organizations.
- Carrier workspace Carrier scope for operational records
- Dispatcher web + driver mobile Role-specific application surfaces
- Role and tenant controls Scoped access and permissions
- Job, document, and notification services Workflow and generation logic
- Operational data and records Durable job history
- Dispatcher web experience
- Mobile driver experience
- Supabase-backed platform services
- Edge functions
- Automated document generation
- Notification and intake workflows
Production proof
From operating problem to live platform.
Active carrier use
Vigil is functioning software running in production, in active use by an Atlanta carrier.
Deployed workflows
Dispatcher and driver workflows are deployed and support real freight execution.
Generated documents
The platform produces the operational documents a load requires, from the job record.
Vigil was designed beyond a single-customer implementation and continues to expand through controlled product releases. It is moving toward richer driver-location visibility, with production activation remaining subject to controlled device validation.
How it was built
Gabriel’s role, end to end.
Product strategy
Translated a carrier's operating problem into a defined product, a capability roadmap, and a sequence of releases that could be validated against real work.
Operating model
Mapped the job lifecycle, the dispatcher and driver roles, exception paths, document requirements, and the information flow between office and road.
Technical delivery
Built the application, data model, tenant and role controls, workflow automation, document generation, and the two role-specific experiences.
Production execution
Moved the platform into real carrier use. Developed the initial provisioning, training, and operating controls intended to support future carrier onboarding.