Fragmented dispatch communication
Work gets coordinated across calls, texts, and spreadsheets instead of one shared system.
Project · Operating-system prototype
Vigil
A logistics operations platform for dispatch coordination, driver workflows, shipment visibility, and document generation.
The operating problem
Small logistics teams run on calls, texts, and spreadsheets.
The challenge is not just tracking shipments. It is coordinating people, documents, assignments, exceptions, and customer-facing updates through a repeatable system.
Manual document creation
Bills of lading, rate confirmations, and delivery orders get rebuilt by hand for every job.
Weak shipment status visibility
Knowing where a load actually stands takes a phone call instead of a glance at a dashboard.
Driver coordination gaps
Assignments, pickup details, and delivery instructions travel informally instead of through a structured workflow.
Repeated customer-update work
The same status information gets retyped and re-sent to customers, job after job.
Too much operational knowledge trapped in people's heads
When the process only lives in someone's memory, it cannot scale or transfer to a new hire.
System overview
Vigil as an operating workflow.
01
Intake or create a job
Start a new job with the shipment details dispatch needs to act on.
02
Assign driver and shipment details
Match the job to a driver and attach the specifics of the load.
03
Coordinate pickup and delivery
Move the job through pickup and delivery as a structured workflow, not a string of calls.
04
Notify dispatcher and driver
Keep both sides of the job informed as status changes, without manual follow-up.
05
Generate required documents
Produce the paperwork a job needs directly from the data already in the system.
06
Track status and exceptions
Surface where a job stands and flag what needs attention.
07
Preserve an operational record
Keep a durable record of the job, from intake through delivery and documentation.
Capabilities
What the platform actually does.
Job and shipment management
Create and track jobs and the shipment details attached to them.
Dispatcher workflow support
Give dispatchers a working surface for assignment, coordination, and exceptions.
Driver workflow support
Give drivers a focused view of assignments, pickups, and deliveries.
Pickup and delivery coordination
Move a job through pickup and delivery as connected steps rather than isolated updates.
Notification workflows
Keep dispatchers and drivers current on job status without manual chasing.
Document generation
Produce the logistics documents a job requires from the underlying job data.
Operational status tracking
Track where each job stands across its lifecycle.
Role-based access and execution
Give dispatchers and drivers the workflow and permissions relevant to their role.
Documents & workflow artifacts
Paperwork generated from the job, not rebuilt by hand.
Each of these is a workflow artifact Vigil can generate or route, reducing manual admin burden and improving consistency across jobs.
Bill of lading
The core shipment record documenting what is being carried and its handling terms.
Customer rate confirmation
Confirms agreed pricing and terms with the customer for a given job.
Driver rate confirmation
Confirms agreed pay and terms with the driver for a given job.
Delivery order
Directs the delivery leg of a job with the details the driver needs to execute it.
Invoice
Bills the completed job based on the job's recorded details.
Architecture
Job intake to operational record, in one path.
Job intake
→
Assignment
→
Driver coordination
→
Pickup workflow
→
Delivery workflow
→
Document generation
→
Status tracking
→
Operational record
At a high level
Web applicationSupabase-backed data and edge functionsRole-specific dispatcher and driver experiencesDocument-generation functionsNotification workflows
What it demonstrates
The same thinking behind the consulting practice.
Workflow automation
Converting a manual, call-and-spreadsheet process into a structured, repeatable system.
Product thinking
Designing for the two different people who actually use the system: dispatchers and drivers.
Operations design
Shaping the job lifecycle itself, not just the software wrapped around it.
Role-based systems
Giving each role the access and workflow relevant to what they need to do.
Logistics process understanding
Reflecting how dispatch, pickup, delivery, and documentation actually work in practice.
Document automation
Generating the paperwork a job requires directly from its underlying data.
Strategy-to-execution delivery
Carrying an operating-model idea all the way through to working software.
Building usable systems, not just slideware
A real, working platform, not a deck describing what a platform could do.
Current state
Where the project stands today.
- Built as a logistics workflow platform/prototype
- Covers dispatch, driver, shipment, notification, and document workflows
- Demonstrates how operational complexity can be converted into structured software workflows
- Supports Gabriel's AI strategy and operations positioning by showing the ability to design and build real workflow systems
Continue exploring