Problem, approach, result.
A national ground-transport company had grown to seven cities with 240+ drivers, running on 11 WhatsApp groups, six shared spreadsheets, and tribal knowledge held by senior dispatchers. Shift handovers happened verbally. Driver issues went unrecorded. Affiliate work was tracked in a separate sheet that didn't reconcile with payroll. When a customer complaint came in, it took 30+ minutes to reconstruct the job. Compliance audits were a fire drill.
We mapped every information surface in use and reduced them to one schema: shifts, drivers, vehicles, jobs, incidents. The console was built around the shift as the atomic unit — handovers became a structured workflow with required acknowledgement, not a 'good night' message. We rolled out city-by-city, starting in Sydney with the most resistant ops team, on the principle that if it worked there, it would work everywhere.
Encore now runs all seven cities through one console. The shift-handover workflow is enforced — outgoing supervisors must close out their shift with structured notes; incoming supervisors must acknowledge before going on-shift. Every job, every incident, every driver issue is permanently recorded against the shift it happened in. Compliance audits now take an afternoon instead of a week. The 11 chat groups and six spreadsheets are gone.
The interface in production.
The shift-handover console — where outgoing and incoming supervisors close and open shifts with structured notes, flags, and forced acknowledgement.
FIG. 01 / ENCORE.CONNECT / SYDNEY HQ — SHIFT HANDOVER VIEW
What we built.
The actual surfaces, services, and capabilities that ship.
Shift-handover workflow
The atomic unit. Outgoing shift closes out with structured notes + flags. Incoming acknowledges before going live.
- ›Required structured handover notes
- ›Flag-based escalations carry forward
- ›Audit trail against shift, not user
- ›Cross-city visibility for HQ
Driver & vehicle registry
Single source of truth for drivers, vehicles, certifications, and assignments — with expiry alerts.
- ›License + certification expiry alerts
- ›Vehicle service interval tracking
- ›Affiliate vs. employed driver flags
- ›Per-driver performance roll-up
Job ledger + incident log
Every dispatched job is recorded against a shift. Incidents are first-class objects with required follow-up.
- ›Job → shift → driver linkage
- ›Structured incident categories
- ›Customer complaint → root-cause
- ›Dispute resolution audit trail
Compliance & reporting layer
What used to take a week now takes an afternoon. Searchable, exportable, audit-grade.
- ›Shift-by-shift exports
- ›Compliance audit pack one-click
- ›SLA + driver hours dashboards
- ›Per-affiliate reconciliation
From brief to live.
We used to spend the first hour of every shift figuring out what happened on the last one. Now the shift starts with a one-click acknowledgement and we're already moving. The audit pack alone paid for the build.
Other systems we've shipped.
Tell us
what's broken.
One scoping call, one written proposal. We'll be honest if it's not a fit.
Book an architecture call