Posted jobs directions

Three directions for Posted jobs

The page where Dana keeps the work she has bought from other people, redrawn three ways on the same brand tokens. It is the mirror of My opportunities, which went to the Inbox today. Each direction here organises around a different thing: the next event, the people waiting on her, or the property the work is for.

Saturday, September 19, 2026Demo data, Dana WhitfieldLight theme shown, every direction inherits dark from tokens

What the current page gets right and where it strains

The September rebuild already answers the right question. A posted job is always waiting on somebody, so the sections are who: Needs you, Booked, Out for applications, Done. That order should stay, and so should the rule that a job with three people waiting looks nothing like one nobody has applied to.

The strain is inside the cards. Every one carries a photograph and five links, Review applicants, Add to Google Calendar, Zillow, Cancel job, Edit, so ten jobs is fifty links and ten photographs of houses Dana already owns the listing for. Five cards fill a 1440 screen. The people who are actually waiting on her are three avatars and three first names; what Jordan is asking, and that it is $15 over, is behind a button. And the money story is in the rail, not on the job: $385 committed and not yet paid, but no card says which ones or when that money goes.

Direction A is the mirror of today's My opportunities: one stream, no photos, a next-event column on every row, actions only where there is a decision. Direction B turns Needs you inside out and puts the applicants themselves on the page, with their asks and Book on each. Direction C groups the work under the property it serves, one photo per listing, with the jobs as a timeline underneath. Flat fees throughout; nothing is shown per hour.

Side by side

Question	Current	A · Desk	B · Applicants	C · By property
The unit	A job, as a photo card	A job, as a row	A person waiting on you	A listing, with its jobs
The question the page answers	Who is each job waiting on	What happens next on each job, and what do I do	Who do I book	What has each listing needed, cost, and what is next for it
First thing the eye lands on	A photo of Chapel Hill Road	"7 people waiting on you across 3 jobs"	Nia Caldwell, tinted, Book Nia · $95	45 Chapel Hill Road with "3 waiting on you"
Jobs visible without scrolling at 1440	5	10	7 applicants on 3 jobs, plus 4 in the list	5 jobs on 3 listings, plus a fold
What an applicant asks	"asks $110.00" in a corner; who, behind a button	On the row: "Jordan asks $110 · Nia and Erik at your price"	The column	On the step: "Jordan asks $110"
Links per job	Five	None on the row; in the dialog	Reject and Book per applicant; none on the list	Review or Invite where needed; Zillow once per listing
Photos	One per job	None	None	One per listing
Consistent with My opportunities (Inbox)	Partly	Yes, it is the same component with different bands	No, a different page shape	No, a different page shape
Phone	3,300px of cards	Bands of two-line rows	Job captions over applicant cards	A card per listing
Agent with twelve listings	Twelve photos	Long Needs you band, fine	Fine; the queue is the page	The best fit; quiet listings fold
Data the page does not have today	—	Views per open job ("4 vendors saw it"); everything else is loaded	Nothing; the applications and their asks are loaded for the dialog	Listing-to-property links (Properties has them), views per job
Build cost	—	Low: JobStream from this morning with posted-jobs bands and a next-event function. The cheapest.	Medium: ApplicationsDialog's rows flattened to the page, best-fit pick, a compact list under it.	Medium to high: a grouping by property, a timeline row, cross-listing suggestions.
Biggest risk	—	A next-event line that is wrong reads as a promise; "Rosa arrives at 8:00" is her booking, not her ETA, so the wording stays "booked for".	An agent with no applicants gets a page whose whole point is missing; it needs to fall back to A.	Jobs with no property link (plenty, today) need a "no listing" group, which is A again.

Recommendation

A · DeskShip this

It is the Inbox's mirror, built from the same component that shipped this morning, so the two pages that face each other finally look like they do. It puts the counter-offer on the row, takes forty links off the page, and costs the least. Booked rows get who arrives when; open rows get the two fixes when they are running out of time.

B · ApplicantsTake the row

The applicant row with the ask column and the best-fit pick is the right thing, and it already exists in the Desk dialog. Ship A, then bring B's best-fit tint and "Book Nia · $95" into the Review dialog rather than onto the page.

C · By propertyThe Properties page's job

The per-listing timeline and the "ask Rosa to do this one too" suggestion are genuinely new, but they belong on the property's own page, where the listing already is. Build the timeline there; leave this page as the queue.

Either wayNon-negotiables

Keep the four sections in the order they need her. What each applicant asks, on the job. No photos on rows. Zillow, Calendar, Edit, Cancel in the job, not on every card. One amber at most, and only on a booking. Flat fees, never a rate. Sentence case, Inter, the locked title scale.

Three directions for Posted jobs

What the current page gets right and where it strains

Current · as it ships

Direction A · The Desk

Direction B · The Applicants

Direction C · By property

Side by side

Recommendation