WORK  /  ENCORE CONNECT
CASE / 02 · 2025
Internal OpsAU · 7 cities14 weeks · phased
CLIENT
Encore Connect

Shift-handover chaos → structured operations console.

A 24/7 ground-transport network was running on WhatsApp threads and a stack of spreadsheets. Encore Connect replaced the patchwork with a single shift-aware console for handovers, affiliates, vehicles, and compliance.

PROJECT META
TYPEInternal operations console
SCOPEWeb · multi-tenant
USERS~80 ops · 240 drivers
CITIESSydney, Melbourne, Brisbane, Perth +3
LIVE SINCEJanuary 2025
STATUSActive · expanding
SURFACES COLLAPSED
11 → 1
Chat groups + sheets retired
CITIES SUPPORTED
7
Multi-tenant from day one
COVERAGE
24/7
Shift-aware handovers
COMPLIANCE AUDIT
100%
Searchable record of every job
[02]The shape of it

Problem, approach, result.

I · PROBLEM

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.

II · APPROACH

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.

III · RESULT

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.

[03]What we shipped

The interface in production.

The shift-handover console — where outgoing and incoming supervisors close and open shifts with structured notes, flags, and forced acknowledgement.

encore.connect / Sydney HQ / Shift Handover · Tue 22:00 → Wed 06:00
SYD ● 14MEL ● 9BNE ● 6PER ● 4
OUTGOING SHIFT · 14 DRIVERS
DRIVER
VEHICLE
JOBS
INC
STATUS
Marsh, J · SYDVAN-1280OFF
Patel, S · SYDSUV-04111OFF
Rao, A · MELVAN-0960ON
Wu, K · BNESUV-2290BREAK
Allen, T · MELVAN-0370ON
Cox, R · BNESUV-18102OFF
Singh, P · PERVAN-0750ON
Lee, M · SYDVAN-1590ON
HANDOVER NOTES · 4
22:14VAN-12 idle warning light — flag service
22:18Affiliate AAR — 2x school runs assigned 06:30
22:22Customer #4119 escalation — credit applied
22:31PER · weather alert — adjust SLA window
HANDOVER STATUS
Awaiting acknowledgement
Incoming: M. Daoud · ETA 21:55

FIG. 01 / ENCORE.CONNECT / SYDNEY HQ — SHIFT HANDOVER VIEW

[04]System build

What we built.

The actual surfaces, services, and capabilities that ship.

MODULE / 01
OPS

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
MODULE / 02
FLEET

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
MODULE / 03
JOBS

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
MODULE / 04
REPORT

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
[05]Timeline

From brief to live.

Wk 0–201/06
Discovery · 7 cities
On-site shadowing of dispatchers. Mapped every surface, every workaround, every spreadsheet.
Wk 3–502/06
Schema + shift model
Designed the shift as atomic unit. Validated workflow with Sydney + Melbourne supervisors.
Wk 6–903/06
Console build · alpha
Handover workflow, driver/vehicle registry, job ledger. Sydney pilot.
Wk 10–1104/06
Sydney live
Full cutover. Old chat groups frozen. Two weeks of close support.
Wk 12–1305/06
Roll-out · MEL/BNE/PER
Phased city-by-city with on-site lead per launch.
Wk 1406/06
Reporting + audit pack
Compliance exports + per-affiliate reconciliation live across all cities.
WORDS / 06 · CLIENT
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.
Head of Operations
ENCORE CONNECT · SYDNEY
STACK / 07
FRONTEND
ReactTanStack TableTailwindRecharts
BACKEND
Node.jsPostgresPrismaBackground workers
INFRA
AWS SydneyRDSS3Datadog
INTEGRATIONS
Xero (payroll)SlackEmail/SMS alerts
[]Have a similar system to build?

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