Field collections · Independent redesign · 2024
Planning visits and reviewing accounts in one field app
Field collectors needed access to visit priorities, contracts, contact details, and case history away from the office. I revisited an app I had worked on, using its existing requirements to explore clearer grouping and hierarchy on a small screen.
Self-initiated redesign · Not a shipped release
Names and screen data are illustrative. The interface shown is a redesign based on earlier professional work.
Make the day’s priorities visible
Tasks lead with days overdue, amount, and the visit window. The list, map, and route use the same urgency colors, so their meaning stays consistent across views.
The proposed route uses a numbered timeline to show the order of visits. The displayed stops, distances, and times are sample data.
Group the account details
I kept the existing case-file structure and grouped its information for a phone. Identity, contact details, documents, and attachments are available from the client view.
Contracts begin with a balance summary, with the detailed ledger below. This changes the reading order while keeping the underlying account information available.
Keep visit capture together
The capture view brings recording, photos, video, and files into one place. A consent reminder appears before recording, and recent recordings remain available for review.
This is a proposed interaction. Its use in real visits, including one-handed operation and poor connectivity, would need validation.
What I would test
I would test whether collectors can find the right account information, interpret urgency, and record a visit under field conditions.
The existing contact restrictions and offline requirements would also need to be checked in implementation, including what happens when a connection drops during a visit.