01
Request and quote
Public requests enter an intake queue first. Operators can review the request and promote it into the commercial quote workflow without pretending an inquiry is already a shipment.
Transportation operations, connected end to end
Run the move from first request to final record without losing the operating truth.
Lucas Dispatch connects intake, quoting, carrier sourcing, assignment, driver execution, tracking, evidence, documents, and settlement in one organization-scoped operating model.
Dispatch control
Cargo visibility
Scoped access
Public control surface
Track a shipment
One connected operating path
1
Request
Quote and activation
2
Execution
Carrier, driver, route and tracking
3
Closeout
Evidence, documents and settlement
Operating lifecycle
The interface follows the move, not a collection of disconnected modules.
The same record moves through commercial activation, sourcing, dispatch, driver execution, tracking, evidence, and closeout. Each surface shows the part of that lifecycle the current role is allowed to work.
Lucas does not treat a quote as a shipment, a shipment status as a carrier assignment, or a navigation link as permission. Those boundaries stay explicit in the product and in the interface.
02
Commercial activation
A transport order crosses an explicit commercial activation boundary before shipment execution becomes available.
03
Source the move
Carrier eligibility, equipment, service areas, offers, and driver records stay connected to the shipment that needs capacity.
04
Assign and dispatch
Dispatch assignment and shipment-state controls operate through server-checked rules, with a phone-friendly driver workspace for assigned work.
05
Move and verify
Tracking, inspections, evidence, status history, and exceptions stay visible as the move progresses from pickup toward delivery.
06
Close the record
Documents, receivables, settlement stages, lifecycle status, and audit history remain attached to the same operational record.
Service intake
Start with the move you actually need priced.
Lucas keeps different transportation and moving service lines on their correct pricing paths instead of forcing unlike work into one formula.
Local Moving
Start a local moving request with pickup, delivery, timing, and move details in one intake flow.
Long Distance Moving
Start a long-distance moving request and give the pricing team the details needed for the correct tariff basis.
International
Start an international moving request and hand the move details to a coordinator for the appropriate pricing path.
Auto Transport
Request pricing for vehicle transport with the vehicle and lane details a coordinator needs to prepare the estimate.
Trust by architecture
The interface shows the boundaries the system actually enforces.
Operational clarity comes from making scope, state, next action, and handoff visible—not from hiding them behind a generic dashboard.
Authorization stays load-bearing
Internal workspaces are organization-scoped and protected by server-side role checks at the destination, not by navigation visibility alone.
State has operating meaning
Shipment status changes are constrained by the domain state machine and recorded as history instead of being treated as decorative labels.
Public and internal surfaces connect safely
Public tracking and intake stay separate from internal dispatch controls, while still handing users into the same transportation record lifecycle.
Start the right workflow