End-to-end orchestration
Work orders trigger dispatch. Dispatch triggers time-keeping. Time-keeping feeds payroll. No handoffs lost, no re-keying, no gaps.
Pillar 04 · Ports Pillar
One order. One lifecycle. No re-keying between systems.
End-to-end orchestration that connects work orders → auto-dispatch → time keeping → payroll feed. Exceptions route to the right person. Audit trails are complete by default.
What this pillar does
The specific work this pillar automates.
Cross-pillar visibility
Every supervisor, dispatcher, and payroll clerk sees the same state of the same order in real time — no reconciliation calls.
Automated escalations
When the orchestration hits an exception — a missed acknowledgement, a rule violation, a payroll mismatch — the right person is paged with the context.
Full-lifecycle audit trail
One record per order carries the full history from intake through payroll. Grievances, HOS challenges, and audits resolve in one place.
Rollback and correction flows
When data changes downstream, the system recalculates upstream impacts and surfaces the deltas for supervisor approval.
KPI dashboards
Cycle time, SLA breach rate, exception volume, and labor cost per order — tracked per crew, per shift, per customer.
How the workflow runs
From trigger to completion.
- Stage 01
Work order intake
Order arrives via any channel, classified and enriched (see Work Orders pillar).
- Stage 02
Dispatch applied
Auto-dispatch or supervisor review assigns the right driver or crew under the right rules (see AI Dispatching pillar).
- Stage 03
Field execution
Driver or crew works the order. Time is recorded via geofenced clock events (see Time Keeping pillar).
- Stage 04
Completion evidence
Photos, signatures, and forms close the order with a full evidence chain.
- Stage 05
Payroll feed
Time records, interpreted against union and HOS rules, stream to payroll ready to process.
- Stage 06
Reporting and billing
Completed orders feed reporting, dashboards, and external billing with full traceability.
Integrations
Systems we already speak.
TMS systemsTerminal Operating SystemsPayroll systemsHRISTime clocksELD devicesCMMSCustomer portals
Modeled · pilot simulation
68% fewer
Modeled reduction in supervisor-hours spent reconciling across dispatch, time, and payroll systems.
FAQ
Questions buyers ask us first.
The honest answers. If your question is missing, book a fit call and we will answer it live.
Can we adopt dispatch automation without adopting all four pillars?
Dispatch automation requires at least Work Orders and AI Dispatching to be running. Time Keeping can be deferred, but you lose the closed-loop payroll benefits.
How are errors across the pipeline handled?
Every stage has its own exception handler with supervisor queues. Cross-stage errors (e.g., time recorded for an unassigned crew) raise alerts with cross-pillar context.
Does this replace our payroll, TMS, or TOS?
No. Dispatch automation orchestrates between your existing systems of record. Payroll, TMS, and TOS stay in place.
How are changes propagated?
When a work-order change impacts dispatch or time records, the system computes downstream deltas and surfaces them for supervisor approval before committing.
What reporting is available?
KPI dashboards for cycle time, SLA breach rate, exception volume, labor cost per order, and crew utilization. All exportable.