Drawn only from what the coach mobile app is contractually for: work the task inbox, read the priority ranking, handle risk flags, close the loop with a message. Full builder parity stays on web.
One answer to one question — how does a coach spend four minutes between clients? — committed to a single interaction model rather than hedging. Two other directions (Ward, a full-roster glance grid; Line, tasks-as-messages) were explored alongside it and retired in the July 2026 cleanup; git history holds them.
Update: The screens below are drawn on Priority view, which the scope contract defers to Post-V1 — so they mock a surface that isn't in scope. Rounds has been rebuilt on the coach task inbox with a proper app shell: Rounds, revision B →
A coach who opens a list decides what to do next forty times a day. Rounds removes the choosing. The priority projection already ranks every relationship and names a primary action — so the app plays that ranking as a sequence and asks one question per card: handle it, defer it, or skip it.
You start a run, you finish a run. There's a beginning and an explicit end, which is the thing a list can never give you. The reward is the empty state.
Character: editorial, high-contrast, near-black. Serif display numerals against a mono spine. It feels like a briefing document, not a dashboard.
coach-priority ranked list, top reasons, primary action/viewed, /snooze, resolve with linked messageEverything that needed you this morning has been handled or deferred.
The priority projection already does the ranking work and already names a primary action — Rounds spends that asset instead of re-displaying it, and the finite session is the one thing a coach can actually fit between clients. It's also the cheapest to build: one card component, three actions, no dense grid to make accessible.
One thing worth carrying in from the retired directions: an inline composer. Nearly every coach task resolves in a message — a nudge, a follow-up, a risk check — so replying should close the card without leaving the run.
The density idea that Ward was built on isn't dead either, it's just on the wrong device. A full-roster glance grid belongs on the coach web dashboard, where scrolling costs nothing.