A connected trip-management experience for the people requesting trips, the drivers accepting them, and the administrators keeping the workflow accountable.
My focusProduct direction, UX flows & interface design
Illustrative sample screens recreated for this case study—not live app controls or production screenshots. Names, routes and counts are fictional. No customer records, identity documents or login credentials are shown.
01 / Frame the problem
A trip is a sequence of decisions, not a single booking.
I started with the coordination between three roles: a requester needs a trip fulfilled, a driver needs to understand and accept the work, and an administrator needs visibility into the supporting records. The design challenge is making each handoff understandable without giving everyone the same interface.
The working hypothesis
Clear ownership, visible status and explicit confirmation can make the workflow easier to follow. This is the design intent—not a measured outcome. User research and pilot validation are still ahead.
02 / Map the experience
Different responsibilities. A shared understanding of progress.
I mapped the core journey around the decision each role needs to make next. Driver acceptance and requester confirmation are separate moments; the interface should not imply that one automatically means the other.
Request a tripThe requester supplies the trip details and follows its status.
Driver acceptsAn eligible driver accepts; the requester can review the assignment.
Requester confirmsThe requester confirms the driver before proceeding.
Track the outcomeTrip progress and administrative visibility stay connected.
03 / Design through iteration
Small interactions. Important operational consequences.
I refined the experience through hands-on walkthroughs and implementation feedback. These are concrete decisions from the build, not claims from a completed usability study.
01
Put the action beside the document.
A separate add/renew flow made users choose the document type again. I moved Upload, Take photo and Replace/Renew to each document row, keeping the type selected automatically.Intent: reduce repeated selection and preserve context.
02
Preview without losing your place.
View opens an in-page image or PDF preview rather than taking the user away from the checklist. Close and keyboard controls support returning to the same task.Intent: make checking a file part of the upload workflow.
03
Separate submission from approval.
Uploading a file does not make it verified. Pending review, review reasons, expiry details and renewal states need to communicate different meanings. A replacement goes back for review instead of inheriting approval.Intent: communicate trust through explicit states.
04
Ask each role for what it needs.
Driver documents and requester business documents serve different purposes. GST is optional for requesters, authorization letters are requested only when needed, and individual requesters do not receive business-document requirements.Intent: avoid turning every onboarding flow into the same checklist.
04 / My contribution
Connecting design intent to a working experience.
Product and experience design
I shaped the role-specific journeys, information hierarchy, onboarding requirements and interaction details. I reviewed working flows and used those observations to refine the interface and its states.
AI-assisted implementation
I use AI-assisted development to turn decisions into working interfaces, iterate on behavior and support technical checks. This page describes my design direction; it does not imply that I personally hand-coded every part of the system.
05 / Current state & next questions
A work in progress, with the gaps visible.
Implemented so far
Separate Requester, Driver and Admin experiences with role-based access.
Private document upload, preview and manual review flows.
Document expiry information and replacement/renewal states.
Role-specific requester document requirements.
Next to validate
End-to-end trip handoffs and recovery from interrupted journeys.
Whether users understand acceptance versus confirmation.
Clarity of document requirements, expiry and review feedback.
Mobile usability and isolated demo walkthroughs.
Status: in development. No adoption, conversion, time-saving or revenue results are claimed. A recorded walkthrough can be added after the complete demo flow is verified.