| The axis | Place and day | Time: one day on a clock strip | Money: a sortable table | The decision: a proposed week |
| The question the page answers | Which fit, where they are, what the week pays | What does my Friday look like if I take these | Which of these pays best for the hour and the drive | What should I take this week |
| First thing the eye lands on | "6 fit around your stops" beside priced pins | Her 9:00 showing as a block with four open jobs under it | An ink card: best per hour, $138/h | "Take these four and Friday pays $285" |
| Jobs visible without scrolling at 1440 | 9 rows with 2 of her stops, 11 on the map | One day: 5 open jobs on the strip, 3 on the route, 3 under | 10 rows, every column | 4 in the plan, 1 near miss, 3 cards, 5 of the list |
| Knows her calendar | Yes, fits and clashes on rows and pins | Yes, it is the strip; clashes sit inside her blocks | Yes, as a column; clashes dim or hide | Yes, the plan is built from it |
| Where the week's total lives | A stats strip above the list | Under the route, per day, with the fee taken off | The table footer, over the fits | The right pane of the plan, with hours, miles, per hour |
| Applying | Outline Apply on each row | Outline Apply on each route stop; "Apply to 2" on the phone | Outline Apply on each row; Apply anyway as a ghost on a clash | One amber "Apply to all four", or one at a time |
| Amber | Get coverage only | Get coverage, and "Apply to N" on the phone when a route exists | Get coverage only | Get coverage and Apply to all; the page has its own action |
| Map | Full height, priced pins, dashed clashes, dotted route | A strip map of the day's route, the full map behind a tap | None on the page; a link to C's map | None on the page; a link to C's map or E's table |
| Phone | Map with a sheet headed by the day | Day chips, the strip with prices on blocks, the route as rows | A sort switch, the picks as a swipe row, two-line rows | The plan above the fold with the button, then the list |
| Vendor account | Trade replaces the type menu; pins read Quote | Same strip; their booked jobs are the tinted blocks | The best fit: forty rows across three counties want a table | Same plan, built from their booked jobs and service radius |
| Data the page does not have today | Her booked jobs and straight-line miles, both on the dashboard | Same as C, plus drive minutes between stops if the "6 min" is to be honest; miles otherwise | Same as C; the per-hour figure is pay over duration | Same as D, plus the chain picker: best-paying set of fits with no clash, run over the week |
| Build cost | Medium, the most of the first three | New: the clock strip and block layout, the route panel, a strip map. Medium to high; the strip is the work. | Low to medium: a table on the existing rows, a sort, three derived picks, the footer sum. The cheapest of the six. | C's fit function plus a week-long chain picker, the plan panel, a batch apply that sends N applications. Medium; the picker is the work. |
| Biggest risk | Pin labels crowd at 10 mi | A day with nothing booked is an empty strip with jobs floating on it; needs a "free all day" state that still reads as a plan | It looks like work. A new agent with two jobs nearby gets a spreadsheet for two rows; the picks carry it below five rows, the table should collapse to cards under that | A wrong plan reads as advice. The reasons on each row and the "rules, not a model" line keep it honest, and the near-miss row shows its working |
