UI / UX Mock Round 1

User stories

Sales manager

• I want to define a named cadence (Weekly / Monthly / a seasonal pattern) once and reuse it across many accounts.
• I want to bulk-apply a template to a filtered set of accounts (by tag, territory, list) so rollout doesn't take a week.
• I want to customize an account's cadence after applying a template, and have it not silently revert when I edit the template later.
• I want the weekly breach report annotated with PTO / holiday context, surfacing patterns rather than single misses.
• I want to see whether a breach was inherited at handover or accumulated under the current rep.
• I want to see, on each account, which template is applied and whether it's been customized.

Sales rep (mobile)

• I want to know at a glance which of my assigned accounts are due, overdue, or off-season.
• I want to start each day with a prioritized list of accounts, organized so the route makes geographic sense.
• I want to see my whole planned week, not just today, so I can adjust for personal commitments.
• I want to manually reorder my day's list and add ad-hoc accounts — the system is a suggestion, not a cage.
• I want to record outcome quickly (substantive / attempted / cancelled) from the parking lot.
• I want unvisited accounts from yesterday to carry forward, so leftover work isn't dropped on the floor.
• I want my "visits done" credit to include legitimate attempts.

Sales rep (account detail)

• I want to see the cadence pattern visually, the template name, the last qualifying visit, and projected next-due date.
• I want to know when an account is in off-season so I don't waste a trip.

Agent (background)

• I maintain last_qualifying_visit_at and the scored pool.
• I draft each rep's upcoming EntityLists from the scored pool, respecting geography and rep prefs.
• I pull each rep's Google Calendar into RepUnavailability with provenance.
• I emit the weekly cadence-breach report with PTO annotations and pattern detection.

Lifecycle

• As a rep newly assigned an account, I want to see who set the cadence and when, so I don't break a contractual pattern.
• As a manager merging two accounts, I want the surviving account's schedule preserved and the other archived.

Scored pool — revised definition

This changes the mental model from "today's list" to "planning horizon with multiple lists." The mobile UI should make the planned week visible, not just today.

Three candidate ranking algorithms

• Tiered + intra-tier sort. Active breach → carryover → approaching → due-soon → rest. Hard ranges, easy to explain, slightly arbitrary at tier boundaries.
• Time-to-breach × priority (normalized urgency). urgency = days_since_visit / max_gap_days; multiply by priority and tightness. Normalizes weekly vs monthly cleanly. Continuous score, harder to explain ad-hoc.
• Cost-of-delay. Each account accrues a per-day cost of being un-visited; rank by cumulative cost. Clean economic framing. Requires assigning cost weights to priority tiers — a values-loaded conversation.

Rescheduling — explicit, not implicit

Trusting breach severity alone fails when a planned account isn't yet overdue. So:

• When an EntityList closes (date passes or rep marks day done), any account without a substantive activity auto-carries to tomorrow's draft list.
• Carryover gets a decaying score boost in the pool: +50% day 1 → +30% day 2 → +15% day 3 → 0% day 4+.
• No-activity carryovers get the full boost; attempted_no_contact gets half boost; cancelled_by_customer gets none.
• One new field on EntityListMember: rescheduled_from FK, so we can render "carryover from Monday" and decay correctly.
• Daily list cap: if rep's target is 12/day and carryovers push it to 18, the surplus surfaces to the manager as "Rep X has too many carryovers" rather than silently bloating the rep's day.

Mocks

Template builder (manager / web)

Three mental models for defining cadence.

Rep daily list (mobile)

Three mental models for the rep's day-and-week. All show the planning horizon, not just today.

Account detail (cadence block)

One approach for now. Visible to both reps and managers on the account.

What we want from this round

• Pick a direction for each surface (one of A/B/C, or a hybrid).
• Identify what's missing or misrepresented in the mocks.
• React to whether the scored pool + reschedule story renders the way it reads.
• Flag mobile interactions that worry you (touch targets, glanceability while driving, offline behavior).