• Transportation
  • Compliance
  • ELD
  • Mobile Native

2025Driver app · Compliance · ELD

HOS Driver AppHours of Service, logs and inspections in one compliance hub a driver can read at a glance

Screens
+60
Compliance tools
4
iOS & Android
2
Logbook with the current duty status, the status buttons and the day graphHOS tab with the Break, Drive, Shift and Cycle clocks and the time to violationHome dashboard with the HOS and DVIR tiles and the connected truck
My role
Product DesignerInformation architecture, UX flows, interaction and visual design for the compliance tools of the new driver app.
Platform
Mobile NativeAndroid and iOS phones, connected to the truck’s ELD
Tools
Figma, FigJam, JiraBuilt on the driver app’s shared templates and components
  • 02 · The challenge
  • Context

Understanding the problem

A phone in the cab that is also a legal record

  • 01

    The background

    Commercial drivers in the US work under FMCSA Hours of Service rules: 11 hours of driving inside a 14‑hour on‑duty window, a 30‑minute break after 8 hours of driving, and a 60/70‑hour weekly cycle. An Electronic Logging Device records every minute, and an inspector can ask to see the log at any roadside stop.

  • 02

    The problem

    Compliance lived in separate legacy apps. Duty status, clocks, logs, unassigned driving and vehicle inspections each had their own entry point, and several tools were missing from the new app’s structure altogether. Drivers had to hunt for the one number they care about: how long they can still drive.

  • 03

    The opportunity

    Bring Log, HOS, DVIR and the compliance settings into one Compliance hub in the new driver app, and put the live duty status and vehicle connection on the home dashboard, so the most frequent actions take one tap.

How might we

How might we let a driver see how much time they have left, change their duty status and fix their log in a few taps, without ever putting their compliance at risk?

  • 03 · Discovery & research
  • Requirements
  • IA

Understanding drivers and the rules

Turning regulations into product behavior

Research approach

  • Mapped the legacy driver apps and the fleet product catalog to find the compliance tools missing from the new IA.
  • Walked the HOS requirements with product: duty statuses, the four clocks, personal conveyance, yard moves and the short‑haul exemption.
  • Reviewed the ELD rules for unidentified driving, log edits and daily log certification.
  • Built the app IA flow and Android screen templates before designing any compliance screen.

Key insights

  • 1 · “How long can I still drive?” is the question

    Drivers open the app for time left, so the clocks lead and every clock names the rule it counts against.

  • 2 · The truck changes what the app can do

    Duty status and clocks only make sense once the phone is paired with the vehicle’s ELD, so the connection state comes first.

  • 3 · Unassigned driving can’t be ignored

    Trips the ELD recorded without a driver must be claimed or rejected; whatever is left goes to the back office for review.

  • 4 · Inspections are part of the shift

    A pre‑ or post‑trip DVIR belongs to the unit and trailer in use, lists defects and ends with the driver’s signature.

App IA flow: sign in, the dashboard with apps, the main driver navigation and the route to inspection
The app IA flow: sign in, a dashboard of apps, the main driver navigation (Route / Load, Dashboard, Activity, Messages) and the path from a route to an inspection. Compliance was the missing branch.
  • 04 · Design strategy
  • User flows
  • Architecture

Defining the experience

One hub, four tabs, the clock always in reach

Instead of separate apps, compliance becomes one hub with four tabs: Log, HOS, DVIR and General. The home dashboard carries the live duty status and the vehicle connection, so the actions a driver repeats all day never need the hub at all.

Primary journey · start of a shift

  1. Sign in
  2. Home dashboard
  3. Connect vehicle
  4. Change duty status
  5. HOS clocks
  6. Review log
  7. Certify log

Branches designed for each step

  1. Vehicle not connected
  2. Unidentified trips
  3. Unassigned activity
  4. Personal conveyance
  5. Yard move
  6. Pre‑trip / post‑trip DVIR
  7. Defects found
  8. Drop / hook trailer
  • Compliance Log tab with the unidentified trips banner above the week graph
  • Compliance HOS tab with the clock cards and the status buttons
The Compliance hub: the same header, tabs and list rows for every tool. Warnings sit at the top of the tab they belong to, and the status buttons stay at the bottom of HOS.

Principles & constraints

  • Glanceable first

    Large numbers, one color per clock and the rule written under it, readable at arm’s length in a cab.

  • One status everywhere

    OFF, SB, D and ON keep the same colors and labels on the home dashboard, the logbook and the HOS tab.

  • No dead ends

    Every warning, from unidentified trips to unassigned activity, opens the screen that resolves it.

  • System first

    The Log, HOS, DVIR and General tabs share the same header, tab bar, list rows and bottom action, on Android and iOS.

  • 05 · The solution
  • Key decisions
  • Architecture

Key design features and decisions

Five moments that carry a driver’s day

FEATURE 01

Duty status, one tap from home

User need
A driver changes duty status many times a shift, often standing at a dock or a fuel pump.
Design approach
Home shows the current status and how long it has run. Tapping it opens the Logbook: four large status buttons, today’s graph and the history right below, so the driver sees the change land in the log.
  1. Four status buttons with an icon, a color and a full label
  2. Personal conveyance and yard move as options of a status, not new statuses
  3. Today’s graph and history on the same screen
  • Home with the duty status bar showing OFF and 00h 00m above the app tiles
  • Logbook with the ON duty bar, the OFF, SB, DR and ON buttons, today’s graph and history
  • HOS tab: Break 08:59, Drive 04:27, Shift 05:30, Cycle 51:15 and 00:15 to violation

FEATURE 02

Four clocks, each with its rule

User need
A driver needs the time left before a violation, not a log to calculate it from.
Design approach
The HOS tab shows Break, Drive, Shift and Cycle as cards that fill as time runs out, each with the rule it counts against underneath (8 Hr Rest Break, 11 Hr Driving, 4 Hr On Duty), and the time to the next violation in red.
The result
The answer to “how long can I still drive?” is the first thing on the screen.

FEATURE 03

Unidentified trips, resolved from the log

When the truck drove without a driver logged in, the Log tab opens with a banner: “3 Trip, 2 days 12 hours 57 min in the past week”. The list groups trips by day with time, place and duration; the driver selects the ones that were theirs and claims them, or marks the rest “Not mine”.

  • Log tab with the Unidentified trips banner: 3 Trip, 2 days 12 hours 57 min in the past week

    Log

  • Unidentified Trips grouped by trip with dates, places and durations

    Unidentified trips

  • Unassigned Activity with three trips selected and the Claim button active

    Select & claim

  • Dialog asking which driving status to claim

    Claim as

FEATURE 04

A DVIR that starts from the truck

Pre‑trip or post‑trip, the inspection fills in the region, unit, trailer, time and odometer from the connected vehicle. The driver walks around the truck, adds photos and picks defects by system for the unit and the trailer, each with a note.

  • Create DVIR, post-trip: region, unit, trailer, time, odometer, walk-around photos and two defects
  • Defects for the unit: Lights, Tires and Driver Seat checked with notes

FEATURE 05

Trucks and trailers in two taps

Manage Equipment shows the units the driver can use with a Connect or Disconnect action next to each. Trailers are dropped and hooked from the same list, with the progress shown in place.

  • Manage Equipment: two units, one connected, with Connect & Continue
  • Manage Trailers: trailer 112 dropping, with Add Trailer
  • 06 · Validation & iteration
  • Requirements
  • Edge cases

Testing and refinement

Designing for the trips nobody logged

Every flow was reviewed with product, compliance and engineering on the working board, with open questions kept as notes next to the screens: “Prompt the user to go On‑Duty?”, “Does the user need to annotate at this stage?”, “Should Duty Status and General settings be relocated?”. Each answer became a state in the flow, and the unassigned driving flow got the most of them.

  • Nothing slips through. Leaving with an activity still unaccounted for says so, and sends it to the back office for review.

    Unassigned Activity dialog: 1 activity not accounted for, with a Review & certify button
  • Claim with intent. Claiming a trip asks what it was: driving, a yard move or personal conveyance.

    Dialog asking for the type of driving status to claim, with Driving Yard Move selected
  • A clear finish. Once every trip is claimed or rejected, the list ends on a resolved state instead of an empty screen.

    Unidentified Trips tab with the message All unassigned vehicle activities are resolved

Iteration log

Before: The clocks were progress rings. They looked good, but the rings read as charts, the time sat inside small circles and the five rings didn’t fit a row of status buttons below.

After: Cards that fill as time runs out, in the same colors as the duty statuses, with larger numbers and the rule under each card. The time to violation got its own red card, so it can’t be missed.

  • Earlier HOS screen with the clocks as progress rings

    Before: rings

  • Final HOS screen with the clocks as cards

    After: cards

  • 07 · Final experience
  • Mobile app
  • Flows

Bringing everything together

From the home dashboard to a signed inspection

Driver app

  • Home dashboard with safety, routes, HOS, DVIR, documents and the connected truck widget

    Home

  • Logbook with the ON duty bar, the four status buttons, the day graph and history

    Logbook

  • DVIR tab with the Create New DVIR prompt and the Add Adhoc Task button

    DVIR

  • General tab with driver name, distance, shipping docs, vehicles and trailers

    General

The DVIR flow from My Routes to a signed inspection, and the advanced DVIR view with equipment and inspection type
The DVIR flow end to end: from a route to the inspection, defects, photos and notes, and the signature. Below it, the advanced view that adds equipment selection and the inspection type.
  • 08 · Outcome & learnings
  • Impact

Impact and reflection

What shipped, and what I’d take forward

  • The outcome

    One compliance hub

    Log, HOS, DVIR and General designed end to end, with the duty status and vehicle widgets on home, unidentified and unassigned driving flows, and truck and trailer management, in connected and not‑connected states.

  • The impact

    Metric

    How success would be measured: fewer HOS violations, fewer unassigned driving minutes sent to the back office, faster duty status changes and more DVIRs completed in the app.

  • What I learned

    Rules first, then screens

    Every screen in this app is a regulation in disguise. Writing the rule under each clock and naming each status the same way everywhere did more for clarity than any layout change.

With more time I would…

I’d test the flows in the cab with drivers at real docks and fuel stops, measure how long a duty status change takes, and check the tap targets with gloves and at night. I’d also design the roadside inspection mode, where the driver hands the phone to an officer.