Minecart · Entity Lists · Today screen

Three item-flat takes on the rep's day.

All three concepts treat the items — not the lists — as the unit of attention. Same shell, same data, three points of view on how list lineage shows up in the rep's working surface. Worklist hides lists behind quiet section headers; Stack keeps each list as a soft-bordered container; Route Queue dissolves lists into a single drive-ordered queue with source chips. Reviewing on desktop; mobile is where this ships.

Sample · Tue Mar 5 · 26 items · 2 done · 3 source lists

Also in this set

Low-fidelity interaction storyboards — 10 flows covering mark-done, drill-to-account, map, record-note, swipe, carry-over, reorder, and per-list_type behavior comparison.

View 10 flows →

A · Worklist

Disappear into the work.

Sober, dense, near-black. Sticky list-name section headers act as quiet tertiary anchors — the eye reaches for tasks, not containers. One primary CTA on the day list. Best when the rep's first move is to start moving.

View standalone →

B · Stack

Keep the list anchor.

Each list is a soft-bordered section: type glyph, count, color stripe by list_type. Per-list "Route ↗" action lives in the day-list header. Manager-curated steady list shows its parent-list lineage as a chip. Follow-ups collapsed by default to demo the affordance.

View standalone →

C · Route Queue

Route is the axis.

One ordered queue across all geographic lists. Cartographic strip up top — the day shape becomes a paper-map artifact, not a chart. Source list becomes a small chip on each row. Off-route follow-ups tail below the route. Best when the rep is driving.

View standalone →

Where I'd push back on this brief.

"Item-flat" is a constraint, not a conclusion. It's the right call only if the day's work fits roughly on one screen of attention. With 26 items the worklist is already long; at 50+ this falls apart. Consider a per-list summary mode for managers reviewing rep capacity — that surface is not item-flat.
The "Off-route" tail in Route Queue (C) is a content lie. Today, follow-ups don't have geo info — fine. But the moment a follow-up has a location ("send quote via in-person drop"), the model needs a way to say "this fits in the route between stops 4 and 5," not "off-route forever."
Sticky list headers in Worklist (A) compete with the status bar. On a real iOS device the status bar overlay plus the sticky header creates a 100px+ chrome zone — eats the dense advantage. Either drop the sticky behavior or make the section headers ultra-thin (one line, no padding).
Stack (B)'s color stripes look great in a mock with three list types and lose meaning the moment a rep has two day lists or three steadies. Color-by-list-type is a teaching device, not a navigation device — once reps know what list they're in, the stripe is decorative. Prepared to drop it after a sprint.
None of these answer "what about Wednesday." The Today screen is the easy half. The hard half is "tomorrow, this week, planned but not yet day-typed." Lists with a future scheduled_for have to live somewhere accessible without crowding Today — likely a separate "Coming up" surface that none of these mocks tackle.