Case Study
Car Care Inc.
Car Repair Work Order Application
Duration
8 weeks
Platform
iPad App
Role
UX Designer
Overview
Digitizing the repair workflow
Car Care Inc. needed a purpose-built iPad app for their auto repair technicians. The goal was to replace paper-based work orders and fragmented desktop tools with a single, touch-optimized application that follows the natural repair workflow — from vehicle check-in to customer sign-off and billing.
I led the UX design over 8 weeks, from user research and competitive analysis through wireframes, visual design, and an interactive prototype. The result: an app that reduced documentation time by 60%.
The Problem
Senior technicians spend 30–45 minutes per work order typing vehicle details, diagnoses, and customer communications — taking them away from actual repair work.
Research & Discovery
Industry pain points & UX opportunities
Pain Points
- Too much manual documentation — technicians spend significant time writing repair notes
- Repeating the same information — common issues documented from scratch every time
- Switching between systems — paper forms, desktop software, and digital tools break flow
- Slow customer approvals — waiting for customers creates idle time
- Parts lookup friction — multiple steps and system switches required
UX Opportunities
- Guided workflows — step-by-step flows that reduce decisions and mental load
- Quick-select inputs — pre-populated options for common repairs and parts
- Visual documentation — photo capture and annotation to minimize typing
- Real-time summaries — auto-generated customer-facing summaries from technician input
- Digital sign-off — in-app approval flow to eliminate delays and paper
Design Goals
Three core principles
Minimize Typing
VIN scan + smart templates to cut manual entry drastically.
Fast Customer Sign-off
Photos + digital signature for fully paperless approval workflows.
Work Offline
Sync automatically when connected. Zero data loss in the workshop.
Competitive Audit
Landscape analysis
Shopmonkey
Mobile technician tools, digital inspections with photos
Tekmetric
VIN scanning, mobile check-in workflows
RepairShopr
Touchscreen signatures on invoices
Mitchell 1
Deep parts catalog integration
Opportunities to Improve
Fewer taps: Quick-select complaint chips vs. open text fields
Voice notes for techs with low typing comfort
Offline-first architecture and plain-language customer summaries
Primary User
Meet Bob — Senior Technician
15 years experience. Values efficiency over features. The interface must feel intuitive from the first tap.
Goals
- Complete work orders fast
- Document with photos
- Easy customer sign-off
Frustrations
- Too much typing
- Offline access failures
- Repeat data entry
Design Implication
Bob needs maximum efficiency with minimal learning curve. Success means completing documentation faster than his current method, without feeling like he's "learning software."
Information Architecture
Technician workflow overview
Breaking down Bob's daily workflow into four key task flows the iPad app must support.
Flow A
Quick Check-in
VIN/Plate Scan → Auto-fill Vehicle Details
Flow B
Diagnosis
Quick-select Faults → Photos + Voice Note
Flow C
Customer Review
Photos + Estimate → Digital Signature
Flow D
Complete Job
Auto-generate Invoice → Payment Signature
Design Direction
UX design principles
Core principles guiding every design decision for the workshop environment.
Minimize Typing
VIN scan, voice input, quick-select over keyboards
Maximize Quick-Select
Pre-populated options for common repairs and parts
Guided Workflow
Step-by-step progression reduces cognitive load
Reduce Cognitive Load
One task per screen, clear hierarchy
Workshop-Ready
High contrast, large touch targets, glove-friendly
Fail-Safe Documentation
Auto-save, offline sync, zero data loss
Speed First
Zero Learning Curve
Workshop-Ready
User Journey Mapping
End-to-end: Check-in to billing
Mapping Bob's complete experience through a typical work order.
Low-Fidelity Wireframes
iPad wireframes — flow-driven UX
Translating user journeys into iPad-optimized screen structures. Canvas: 1024 × 1366 px (iPad Pro 11"), touch-optimized with 44px minimum tap targets.
Home / Active Work Orders
Dashboard showing all active jobs for quick access and status visibility.
Vehicle Intake
Quickly capture vehicle details using VIN scan with auto-fill capabilities.
Customer Complaint Capture
Record initial customer complaint using quick-select or voice input.
Technician Diagnosis & Findings
Document actual problems found using structured fault selection and photo capture.
Repair Actions & Parts
Select repair procedures and required parts with integrated catalog and pricing.
Repair Summary & Estimate
Complete cost breakdown ready for customer review with automatic totals.
Customer Approval
Customer-facing view with digital signature capture for work authorization.
Job Completion & Billing
Final invoice generation and work order closure with automated billing.
Visual Design System
Production-ready iPad experience
Applying the Car Care Inc. visual identity to the validated wireframe structure.
Brand Colors
#0656f6
Primary Actions
#465d8b
Secondary Emphasis
#4698aa
Progress & Highlights
#f7f8fa
App Background
High-Fidelity Designs
Production-ready screens
Fully branded screens with Car Care Inc. colors, large touch targets, and workshop-optimized contrast.
Work Order Dashboard
01 / 04
Interactive Prototype
Try the experience
A walkthrough of the final prototype demonstrating the complete work order flow.
Success Metrics
Measurable impact
60%
Reduction in documentation time
From 45min → 18min per work order
4 taps
From check-in to diagnosis
VIN scan + quick-select complaints
95%
Customer approval rate
Photos + plain language = trust
Reflection
This project taught me that the best enterprise tools feel invisible. Bob doesn't want to "use an app" — he wants to finish his work order and get back under the hood.
The key insight was treating the iPad as a clipboard replacement, not a computer replacement. Every design decision was filtered through one question: "Would Bob use this with greasy hands in a noisy workshop?" If the answer was no, we simplified further.