Designing across a construction fleet management platform — from role-scoped web dashboards to a mobile app built for one-handed field use.
Context
i11Fleet runs construction trucking operations — the kind of work where a contractor needs a truck moving material from a quarry to a job site, today.
The platform needed to serve an admin dispatching jobs, a driver hauling them, a carrier managing a fleet, and a client just waiting to see it done — four very different needs on one shared system.
4
Roles designed for — Admin, Driver, Carrier, Client
2
Platforms — Web (all roles) + Mobile (Driver only)
6
Work order states, each a real gate
1
Verification gate before any report unlocks
Adapted from admin and driver feedback.
GOALS
Three goals shaped the direction from the start. Not all of them were equally visible to users. All of them mattered to the product.
"How can we speed up the
truck and load creation
work ?"
"How do you design one interface for four different jobs?"
Replace the call list with a broadcast
Push a job to every available driver at once — first to accept gets it.
A workorder, ticket, truck anything that needs a full length form to fill can filled easily through voice to text feature.
Give each role its own scoped experience
Admin gets full control; carrier and client get narrower views; driver gets a separate mobile-only app.
APPROACH
Before designing screens, I worked through the decisions that would shape the whole system. Each came with a tradeoff.
01
Broadcast instead of a queue
Push to all active drivers at once, auto-close when slots fill or time runs out.
02
Status as a gate, not a display
A work order literally cannot close with incomplete tickets, protecting billing accuracy.
03
Scope each role's view instead of hiding fields
Each role gets its own interface shaped around what it actually needs.
04
Design the driver app backwards from the worst moment
Built for a driver mid-shift who won't read a tooltip — one glance, one tap.
The New i11Fleet
No screens shown here due to confidentiality — the walkthrough below describes what each part of the system does.
Work orders, tickets, live tracking, users, assets, finance modules.
Work Orders & Tickets
Status-gated lifecycle from Open through
Closed.
Broadcast Dispatch
Configurable slots, duration, and driver percentage — pushes to all active drivers at once.
Driver Mobile App
Home/ticket queue, broadcast alerts, active trip flow, document upload, profile.
Live GPS Tracking
Finance Modules
Receivable, driver payable, carrier payable — auto-populated from verified closed work orders.
Broadcast Dispatch
A job goes out to every available driver simultaneously; the broadcast closes the moment all slots fill or the time window expires.
Why this matters. Replaces fifteen minutes of phone calls with a decision that takes as long as it takes someone to tap Accept.
Status as a Gate
A work order can't move to Closed until every ticket inside it is verified complete, and reports can't generate until it's closed.
Why this matters. Making sure the system physically couldn't skip a step that mattered, instead of just displaying where things stood.
Designing for One Hand
Starting a trip turns on GPS with no separate step; the camera is already open for the delivery photo; tonnage entry uses the fewest taps possible.
The decision. A driver pulled over to use an app is a driver losing time and money — every unnecessary tap had to earn its place.
Outcome
Specific usage metrics are confidential and withheld here — this reflects what the design changed structurally.
From one-by-one calls to a broadcast that fills in seconds.
From a status label to a status gate — no incomplete job reaches billing.
From one shared interface to four role-scoped experiences.
Reflections & Learnings
01
The hardest part wasn't any single screen — it was keeping four different roles reliable on the same underlying data.
02
Status and permissions are part of the actual design, not backend rules layered in afterward.
03
Designing backwards from the worst-case moment produces a simpler screen than designing from the best case.
04
The smallest interaction detail — GPS turning on automatically — can remove more friction than an entire extra screen would.