Skip to main content
Back to Portfolio
Logistics / Fleet Management SaaS

Kudra

"Transforming Fleet Operations Through Structured Trip Management"

A logistics operations platform that evolved from simple GPS tracking into a centralized trip management ecosystem — bringing visibility, structure, and accountability to fleet operations.

Role
Product Designer
Timeline
2025 – 2026
Platform
Web Application
Domain
Fleet Management
Tools
Figma · Miro · FigJam · Notion
84
Vehicles Tracked
40%
Less Manual Coordination
7
Core Workflow Steps
2025–26
Design Timeline
Kudra fleet operations dashboard
Case Study

The Overview

Kudra was designed to transform fragmented logistics operations into a centralized trip management ecosystem. The platform evolved beyond simple vehicle tracking and introduced structured workflows for fleet managers, branch operators, and logistics teams.

The goal was to reduce operational dependency on calls and spreadsheets while improving visibility across trips, drivers, fuel usage, and fleet analytics. The product focused on building a scalable enterprise workflow where every vehicle movement was tied to a structured operational trip.

Problem Statement

The Operational Reality

How logistics teams coordinated

  • Phone calls
  • WhatsApp communication
  • Spreadsheets
  • Paper-based tracking

What this created

  • No structured trip lifecycle
  • Lack of trip visibility
  • Poor coordination between branches
  • No centralized fuel tracking
  • Limited driver accountability
  • No operational analytics

Vehicles were moving without operational context.

Teams could not easily identify:

Why a vehicle was moving
Which trip it belonged to
Who the assigned driver was
Fuel usage during trips
Trip completion status
Branch coordination status
Product Vision

The North Star

To create a centralized operational control system for logistics fleets that provides complete visibility into trip planning, dispatch, monitoring, and analytics.

Kudra aimed to establish a workflow-first ecosystem where operations teams could manage logistics through structured trip lifecycles rather than fragmented communication.

Streamline fleet operations
Improve trip visibility
Reduce operational chaos
Generate actionable analytics
Improve branch coordination
Target Audience

Who Uses Kudra?

Fleet Managers

Responsibilities

  • Trip creation
  • Vehicle assignment
  • Driver assignment
  • Monitoring active trips
  • Reviewing fleet analytics

Pain Points

  • Difficulty tracking multiple ongoing trips
  • Excessive operational calls
  • Lack of fuel visibility
  • No centralized operational dashboard

Branch Managers

Responsibilities

  • Monitoring incoming and outgoing vehicles
  • Updating operational statuses
  • Coordinating dispatch communication

Pain Points

  • No visibility into incoming trips
  • Delayed operational updates
  • Dependency on manual communication

Accounts Teams

Responsibilities

  • Fuel expense tracking
  • Driver halt payments
  • Trip reconciliation

Pain Points

  • Missing operational records
  • Manual expense verification
  • Lack of trip-level financial tracking
Research & Discovery

Understanding the Operations

To better understand operational workflows, interviews and observational research were conducted with logistics operators, dispatch teams, and fleet managers. Research focused on:

Dispatch coordination workflows
How trips were verbally coordinated between fleet and branches
Trip tracking processes
How teams monitored vehicle movement and status
Fuel logging systems
Paper-based fuel records and their accuracy gaps
Driver communication patterns
Call frequency and information loss in verbal updates
Branch coordination methods
How branches learned about incoming deliveries
Reporting inefficiencies
Manual effort required to compile operational data

Research Approach

Structured interviews and contextual observation sessions with logistics operators across multiple branches. Focus was on shadowing real operational workflows — not just asking about them.

3
Logistics Operators
6wk
Research Duration
4
User Groups
16+
Sessions Conducted
Key Insights

What We Discovered

01

Trips Needed to Become the Core Operational Unit

Operations teams naturally thought in terms of trips rather than vehicles. Fleet managers talked about "the Chennai trip" — not "truck KA-01-AB-1234". This insight became the foundation of the entire product strategy.

02

Operational Data Was Fragmented

Critical trip information existed across calls, WhatsApp messages, spreadsheets, and human memory. There was no centralized operational visibility — every status update required a phone call.

03

Managers Needed Real-Time Operational Visibility

Fleet managers wanted to instantly understand active trips, delayed vehicles, driver activity, fuel usage, and trip completion status — without making a single call.

04

Branches Required Automatic Operational Updates

Destination branches were often completely unaware of incoming vehicles. This created coordination delays, dock planning failures, and operational inefficiencies at every hub.

UX Goals

What We Were Designing For

Simplify operational workflows

Reduce the number of steps required to complete core fleet operations

Reduce coordination dependency

Embed visibility that eliminates the need for manual status calls

Improve active trip visibility

Give all stakeholders real-time context on every moving vehicle

Reduce cognitive overload

Surface the right information at the right moment — not everything at once

Enable faster trip creation

Reduce trip creation time from 15+ minutes to under 2 minutes

Create scalable enterprise workflows

Build a system that works for 10 vehicles today and 1,000 tomorrow

Information Architecture

Platform Structure

The platform architecture was designed around operational efficiency — ensuring quick access to the most-used workflows while reducing navigation complexity.

Dashboard

Real-time fleet status, active trips, vehicle states, and operational KPIs.

Trip Management

Create, dispatch, monitor, and close trips through a structured lifecycle.

Vehicle Management

Vehicle profiles, maintenance records, performance analytics, and status.

Driver Management

Driver profiles, trip history, halt logs, and efficiency tracking.

Reports & Analytics

Fleet-wide reports on fuel, trips, vehicles, and drivers with export.

Notifications

Automatic branch alerts and operational announcements across hubs.

Frequent Routes

Route suggestions based on historical trip data to speed up creation.

Locations

Manage branches, hubs, and delivery points used in trip planning.

Core Workflow

The Trip Lifecycle

01

Trip Creation

  • Select origin and destination
  • Assign driver and vehicle
  • Select route from frequent route suggestions
  • Add freight and planned trip details
02

Trip Dispatch

  • Capture starting odometer
  • Record starting fuel level
  • Confirm dispatch — status changes to Dispatched
  • Automatic notifications sent to destination branch
03

Ongoing Monitoring

  • Track vehicle movement on live map
  • Monitor trip progress and checkpoints
  • View refueling updates in real-time
  • Track driver halt activity and delays
04

Fuel Tracking

  • Operators record refueling amount and cost
  • Fuel quantity and location captured per stop
  • Enables mileage and efficiency reporting
  • Data tied directly to the active trip record
05

Driver Halt Tracking

  • System records halt locations and durations
  • Halt reasons and waiting times captured
  • Improves operational accountability
  • Supports driver payment calculations
06

Trip Completion

  • Capture ending odometer and fuel level
  • Platform auto-calculates distance, mileage, and fuel efficiency
  • Trip duration and completion time recorded
  • Status moves to Completed → Closed
07

Reports & Analytics

  • Vehicle reports — mileage, fuel efficiency, utilization
  • Driver reports — halt duration, trip completion history
  • Operational reports — route performance, fleet utilization trends
User Flow

Trip Lifecycle States

The lifecycle was intentionally simplified to improve operational clarity and reduce process confusion across all stakeholder groups.

CreatedTrip defined with all operational details
DispatchedVehicle and driver confirmed, branch notified
OngoingTrip in motion, live tracking active
CompletedDestination reached, metrics captured
ClosedFinancial reconciliation complete
Wireframing & Exploration

From Concept to Structure

Early explorations focused on establishing the right operational hierarchy before touching visual design.

Dashboard hierarchy
Prioritizing real-time trip status and vehicle states above all other data
Operational visibility
Making trip progress scannable within 3 seconds for fleet managers
Data-heavy layouts
Structuring dense operational tables without creating cognitive overload
Trip status visibility
Designing status indicators that communicated state at a glance
Fleet monitoring efficiency
Placing the most-used actions at minimum click depth

The Balancing Act

Low-fidelity wireframes went through 5 rounds of iteration. The central challenge was balancing three competing forces across every screen:

Information densityShow everything that matters
ReadabilityStill be scannable under pressure
Operational speedReach any action in two clicks
Enterprise scalabilityWork for 10 vehicles or 10,000

Low-fidelity wireframes established:

  • Status prioritization hierarchy
  • KPI card placement
  • Navigation structure
  • Workflow step sequencing
Design System

Visual Language

Design Principles

High readability
Operators read dashboards in seconds — typography and contrast must work at a glance
Minimal cognitive load
Show only what's needed for the current task; everything else one click away
Status-first hierarchy
Trip and vehicle states always take visual precedence over secondary data
Data clarity
Numbers and operational metrics are the product — they must be immediately parseable
Scannable interfaces
Tables, cards, and lists designed for rapid vertical scanning under pressure

UI Decisions

  • Color-coded trip states (Created / Dispatched / Ongoing / Completed / Closed)
  • Structured dashboard cards with consistent header, filter, and data zones
  • Clear typography hierarchy — metrics large, labels small, metadata smallest
  • Modular analytics widgets that can be added/removed per user role
  • Simplified operational tables with status-first column ordering

Status Color Semantics

Moving
Green
Halted
Amber
Stopped
Red
Inactive
Grey
High Fidelity Design

The Final Platform

The final UI adopted a clean enterprise SaaS aesthetic — dark layouts, structured cards, clear status indicators, and analytics-first interfaces prioritizing active trips, vehicle statuses, and fleet performance metrics.

Kudra live fleet operations dashboard

Live Fleet Operations Dashboard — 84 vehicles, real-time status tiles, active trip monitoring

Kudra — Live Tracking
Live Tracking Module

Live Tracking

Real-time vehicle route visualization on an interactive map, with halt-point timeline, duration markers, and 48-hour playback. Operators can trace a vehicle's exact path and pinpoint every stop.

Kudra — Fleet Management
Fleet Management Module

Fleet Management

A structured vehicle registry showing GPS device IDs, vehicle numbers, last known location, operational status (In Transit / Idle / Inactive), and inline action controls for live tracking and editing.

Kudra — Vehicle Reports
Reports Module

Vehicle Reports

Per-vehicle analytics covering total distance, average and maximum speed, running hours, idle time, and halt points — filterable by date range. Enables managers to measure efficiency and identify underperforming assets.

Kudra — Add New Device
Fleet Management · Add Device

Add New Device

A structured onboarding form for registering fleet vehicles — capturing vehicle number, GPS device ID, vehicle type, capacity, service number, body type, FastTag ID, and driver assignment in a single workflow.

Key Features

Core Capabilities

🗺️

Trip Lifecycle Management

A structured state machine — Created → Dispatched → Ongoing → Completed → Closed — gives every stakeholder clear visibility into where a trip stands without any manual communication.

📍

Frequent Route Suggestions

The system analyzed historical trips to recommend frequently used routes. Benefits: faster trip creation, reduced manual effort, and standardized operational workflows across branches.

Fuel Tracking

Fuel logs integrated directly into trip workflows — enabling mileage tracking, fuel efficiency reporting, and cost visibility per trip tied to the live operational record.

⏸️

Driver Halt Tracking

Operators could track halt duration and delays during trips — improving operational accountability, driver payment workflows, and delay visibility for fleet managers.

📣

Branch Notifications

Automatic announcements triggered when trips were created or dispatched. Replaced WhatsApp chains with context-aware, timestamped notifications across hubs.

📊

Fleet Analytics

Integrated analytics enabling vehicle performance tracking, driver efficiency monitoring, operational optimization, and fleet utilization analysis — all from live trip data.

Challenges

What Made This Hard

Designing for Complex Logistics Workflows

Fleet operations involved multiple stakeholders and edge-case scenarios — vehicles rerouted mid-trip, drivers swapping, branches changing plans. Balancing simplicity with operational depth became a central design challenge.

Resolution

Built flexible trip states with override capabilities and designed exception handling directly into the workflow — not as an afterthought.

Managing Data-Heavy Interfaces

The platform required displaying large amounts of operational information without overwhelming users. A single dashboard could surface hundreds of data points simultaneously.

Resolution

Careful prioritization of visual hierarchy, information grouping, and dashboard readability — with progressive disclosure to keep the primary view clean.

Multiple Stakeholder Needs

Fleet managers, branch managers, and accounts teams required different workflows and levels of visibility from the same underlying data. One screen could not serve all roles equally.

Resolution

Role-based views with shared data — same trip record, different UI surfaces depending on who's looking. The product supported fleet ops, branch coordination, financial reconciliation, and driver monitoring.

Outcomes & Impact

Measurable Results

40%
Reduced manual operational coordination
Fleet managers reported a significant drop in daily coordination call volume.
78%
Faster trip creation
Average trip creation time dropped from ~15 minutes to under 3 minutes using frequent route suggestions.
100%
Trip cost visibility
All trips now have a complete cost record — fuel, driver allowances, tolls — without manual data consolidation.
60%
Reduction in reporting effort
Monthly fleet reports now generate automatically. What took 2–3 days of manual work now takes minutes.
Increase in fleet accountability
Driver halt tracking and fuel analytics created a measurable accountability framework.
84
Vehicles actively tracked
Full fleet across multiple branches now tracked under a single operational system.

Product Impact Summary

Reduced manual operational coordination by 40%
Improved active trip visibility across branches
Faster trip creation workflows
Better fleet accountability
Improved operational reporting accuracy
Reduced dependency on calls and spreadsheets
Learnings

What This Project Taught Me

Workflow-first UX thinking
The best interface decisions came from mapping the operational reality first — not from UI patterns. Understanding what fleet managers actually do before designing how they do it was essential.
Enterprise dashboard hierarchy
In high-pressure operational environments, visual hierarchy isn't aesthetic — it's functional. Wrong prioritization means missed alerts and operational failures.
Operational visibility design
Visibility is a feature, not a side effect. Every screen had to answer 'what does the user need to know right now?' before 'what can we show them?'
Human-centered logistics systems
Behind every data point is a driver, a fleet manager, a branch coordinator. Designing for the human context — not just the data model — was what made the system usable under pressure.
Designing for real-world operational environments
This is a tool used during crisis — a delayed vehicle, a missed delivery, a fuel discrepancy. It must be calm, clear, and fast when the user is not.

Final Reflection

Kudra was more than a fleet management dashboard.

It was an operational transformation project that introduced structure, visibility, and accountability into logistics workflows.

By shifting operations from fragmented communication into a centralized trip management ecosystem, the platform helped logistics teams operate with greater efficiency, transparency, and control.

"The project also highlighted how strong UX can reduce operational chaos in enterprise systems."

Future Scope

What Comes Next

Multi-Stop Trip Workflows

Support complex trips with multiple waypoints, intermediate pickups, and sequential delivery confirmations.

AI-Powered Route Optimization

AI-powered routing that suggests optimal paths based on traffic, distance, fuel efficiency, and historical trip data.

Predictive Fuel Analytics

ML-driven fuel consumption forecasting based on route, vehicle age, load weight, and driver behavior patterns.

Driver Mobile Application

Companion app for drivers enabling trip confirmation, halt logging, fuel entry, and delivery confirmation from the field.

Automated Dispatch Planning

AI-assisted dispatch that matches available vehicles and drivers to incoming trip requests based on capacity and location.

Fleet Intelligence Systems

Executive-level fleet intelligence dashboards with trend analysis, predictive maintenance alerts, and cost optimization.

Deliverables

What Was Produced

UX Research
User Personas
Workflow Mapping
User Flows
Wireframes
Dashboard UX
High-Fidelity UI
Design System
Operational Workflows
Analytics Experience

Want to work together?

Let's build something operationally transformative.