Section 01 of 05
Problem Framing
Design exercise
Reduce the yard-to-counter gap
that delays billing close
Core problem
GroundLevel's bottleneck is not inspection alone. It is the delay and uncertainty created when field inspection data reaches the counter too late and in inconsistent formats. Today, yard crew inspect on paper, photos live on personal phones, and counter staff manually reconcile everything before billing can close.
Time impact
The current return process averages 35–55 minutes from arrival to billing close. The industry benchmark for well-run shops is under 15. Nearly all of that gap is the 20–40 minute handoff lag between yard and counter. Progressive sync (streaming inspection steps to the counter in real time) eliminates that lag and is the single highest-leverage design decision in this exercise.
Two users, two contexts
Counter staff
Need visibility before certainty
They are at a desktop, with a customer standing there, and cannot close billing until inspection is complete.
Yard crew
Need speed before structure
They work outside, often in sunlight, may have gloves on, and will reject digital workflows that feel slower than paper.
Scope decisions
What I focused on
- Reducing the yard-to-counter handoff delay
- Giving counter staff live progress signals before billing is ready
- Making the common inspection path faster and simpler than paper
- Making damage documentation stronger and more defensible
- Converting inspection output into charge-ready billing decisions
What I intentionally left out
- Checkout-side photo capture workflow
- Maintenance follow-up workflow
- Customer-facing return communication
- Admin reporting
- Cross-location asset history
Design principle
Keep the routine return lightweight. Make the risky return auditable.
The goal is to reduce the handoff delay for routine returns while creating a stronger evidence chain for disputed ones.
Edge case rationale
I chose disputed damage not because it is the most frequent edge case, but because it is the highest-leverage one within four screens. It combines revenue recovery, customer tension, and weak documentation, which is the same gap that causes shops to lose disputes when they cannot prove when damage occurred or what the equipment looked like at checkout. Designing for the dispute meant designing the evidence chain backward from the billing conversation.
What I considered but scoped out
I explored a pre-checkout photo capture workflow that would require photos of every piece of equipment before it leaves the yard, creating automatic before/after comparisons. I scoped it out because it adds friction to the checkout flow, which is a different product surface, and risks low adoption without a separate design effort. The return-side evidence chain solves the most urgent documentation gap without touching checkout.