Engagement snapshot
- Mandate
- Convert branch-level turnaround work into a visible, reliable product system.
- Timeline
- 16 weeks from process design to network rollout.
- Team shape
- COO, fleet manager, 3 engineers, and 5 branch supervisors.
The problem
Branch teams lacked a shared view of inspection, cleaning, repair, and dispatch status, so assets sat idle or were promised to customers before they were actually ready.
What we built
Launched a platform that tracked turnaround states, repair queues, and availability commitments across branches and dispatch teams.
Operating context
The company had asset demand but not enough operational reliability around turnaround. Availability promises were often made from incomplete local information, which hurt customer trust and fleet utilization.
Key constraints
- Branches had slightly different repair and prep processes but needed one system view.
- Dispatch teams needed reliable availability without waiting for phone or email confirmation.
- The rollout had to coexist with existing ERP and fleet data without a full replacement project.
What we built
Asset state machine
Represented inspection, repair, prep, and readiness as explicit product states with ownership and timestamps.
Branch and network visibility
Showed local work queues and network-level availability from the same underlying operational model.
Availability commitment controls
Separated tentative availability from confirmed readiness so sales and dispatch saw cleaner signals.
Delivery path
Turnaround flow redesign
Defined the true ready-to-rent logic first so the software reflected operational reality instead of branch folklore.
Branch pilot
Started with high-volume branches where readiness errors were most expensive.
Fleet-wide adoption
Expanded state handling, transfer workflows, and reporting across the network.
Why it mattered
The platform improved reliability because asset readiness stopped being a local guess. Branches and dispatch worked from the same state model, which reduced premature commitments and unnecessary idle time.
Implementation notes
- Turnaround software must define readiness clearly before any UI work starts.
- Branch managers adopted faster when the system helped them prioritize work, not just report on it.
- Fleet visibility is only valuable if sales and dispatch trust the readiness signal.