Pratt Industries · 2019–22
Pratt Maintenance — modernizing fleet repair
An app that replaces paper work orders with a guided flow for scanning a trailer, logging an inspection, and getting a repair approved — for the third-party vendors who keep Pratt's fleet running.
Dashboard — open and closed work orders, with the next action always one tap away.
Overview
Third-party maintenance vendors who service Pratt's trailer fleet were still running the process on paper — a work order filled out by hand, a signature chased down in person, days lost waiting on approval. I designed Pratt Maintenance, a mobile app that lets a vendor scan a trailer's license plate, log an inspection or repair against the real vehicle record, and get it approved without a paper trail.
It was one piece of a larger connected system I owned end to end across web and mobile at Pratt — a single set of brand standards held the maintenance app, the driver-facing PrattTrack carrier-tracking app, and Pratt's web tools together, so the interaction patterns felt like one product no matter which surface a vendor or dispatcher was using.
The problem
Maintenance vendors' current process of using paper forms was outdated: information got lost in the paper trail, the forms themselves were generic instead of vehicle-specific, and getting a repair approved could take several days.
Mac is a contract maintenance vendor who needs an app to streamline trailer inspections. Goals: quickly identify trailer repairs, and get same-day approval to complete repairs and inspections. Frustrations: multiple forms, inaccurate components, and an approval process that took several days.
Design decisions
-
1
Replaced the generic paper form with a guided flow that starts by scanning the trailer's license plate — pulling in real vehicle details (make, model, VIN, odometer) instead of asking a vendor to write them out by hand.
-
2
Split "Inspection" and "Repair" into their own guided paths from a single Maintenance Type choice, each walking through vehicle components — front, sides, tank, interior — one at a time instead of one long form.
-
3
Grounded the information architecture in how dispatch and maintenance vendors actually worked day to day, not in an org-chart view of the business — the same principle I carried across Pratt's other logistics products.
-
4
Built one set of brand standards across the maintenance app, PrattTrack, and Pratt's web tools, so switching surfaces never felt like switching products.
From a parked trailer to an approved repair
The guided work-order flow — scan a plate, confirm the trailer, choose a path, and work through it component by component.
Splash — styled to match the fleet's own brand blue.
Scan the trailer's license plate to start a work order — no typing in truck details by hand.
Confirm the plate before pulling in the trailer's full record.
Choose Inspection or Repair — two guided paths instead of one long form.
Work through the trailer component by component, marking each OK or Needs Repair.
Process
I started with pen and paper to iterate through flow options quickly, then mapped the full workflow — from login to dashboard to work-order status — before moving into hi-fi screens.
Paper wireframes for the repair flow — my usual first pass before anything gets built.
Mapping the workflow — login, dashboard, and work-order detail, against real states like open, in progress, on hold and complete.
The app shipped in three stages — license plate scanning, inspections, then repair requests — and testing at each stage surfaced real adjustments: some terminology needed simplifying, the dashboard needed to be less busy, and vendors asked for image uploading and a way to add a repair request straight from an inspection in progress.
Fewer paper forms, faster approvals, and one connected system across Pratt's fleet tools.