Member Reporting for Trust + Attribution

I redesigned Zipcar’s trip reporting experience to reduce friction during check-in and end trip, while improving photo capture, condition reporting, and the data teams needed to better attribute cleanliness and damage issues. The work supported a broader company goal to improve car conditions and reduce costly ambiguity in member reports.

Business Impact

$8M

Reduction in PLPD costs

81%

Cleanliness attribution (1st year)

22%

Decline in total accidents

This work supported a broader operational effort to improve vehicle condition reporting, attribution, and accountability across the member experience.

Overview

Project Snapshot

My role
UX design, interaction design, systems thinking, workshop facilitation, prototyping, cross-functional alignment

Partners
Product, mobile engineering, Trust & Safety, Community Management, Fleet, Member Services

Timeline
2023 Q2 concepting and design, phased rollout planning into Q4

Scope
Check-in and end-trip reporting on mobile

Problems to solve

Member reporting was important to the business, but painful for members. The existing experience asked people to rate vehicle condition and capture start- and end-of-trip photos, yet the flow had been repurposed from an older damage-reporting pattern and created friction at the exact moment members were trying to begin or finish a trip.

Members described the experience as time-consuming, unintuitive, and sometimes unsafe, especially when taking multiple exterior photos on busy streets or while dealing with unlock issues.

My Approach

Let Members Start When They’re Ready

The original flow forced inspection at the wrong moment. Members were asked to report while they were still finding the car, unlocking it, or getting situated. I shifted inspection out of that brittle moment by decoupling it from unlock and giving members a defined window to complete it when they were ready.

This made reporting feel more flexible without weakening accountability. Incremental save and partial submission logic also made the flow more forgiving if members were interrupted or timed out.

Make Photo Capture Feel More Fluid

I turned photo capture into a more guided, linear flow that reduced cognitive load and made inspection easier to complete. Sequential capture, contextual overlays, and gallery review helped members move through required photos with more confidence and less back-and-forth.

I then shifted condition rating to follow photo capture, so members could evaluate the car with more context. That improved both the reporting experience and the structure of the information collected, while keeping low-value tasks out of the flow.

Key Decisions

This work required product decisions, not just UI cleanup. I had to determine where inspection fit in the trip, how much flexibility members needed, and what information was actually worth collecting. Key decisions included:

  • Letting members finish or update inspection within a defined window, so the flow felt more forgiving and realistic

  • Using a 10-minute reporting window to reduce rush without creating ambiguity

  • Removing low-value tasks that added effort without improving review quality

What’s Next

Exploring More Visual Reporting

Although I did not get to continue this work, I had started exploring a more visual reporting model. For damage, imagery could help reduce subjective interpretation and create better alignment around what counts as light versus moderate damage, making reports more consistent and easier to trust.

For interior issues, a more visual selection model could help members identify problems at a glance instead of working through a text-heavy flow. The broader opportunity was to make reporting feel faster and more intuitive, while improving the clarity and usefulness of what was submitted.