One shell, four structures

Each of the four variants answered a different kind of question, so none of them replaces the others — they get assigned. An area takes the structure that matches the shape of its work, then declares the one summary that never leaves the screen.

AreaStructureAlways on screenTool = drawerMobile
Enquiries inbox C · queue + command 42 open · 6 need action · saved views search, bulk actions, saved filters list → push to desk
Enquiry D · focus desk ✓ quote strip, money line, email chip, next action dock: email / quote / payment / photos peek tiles → full sheet
Quote builder B · document total, version, sent/opened state line editor inline; history + templates full-screen sheet, sticky total
Calendar matrix + queue unbooked 6 · conflicts 2 · today job drawer, fitter swap, travel time week list → day sheet
Money C · ledger outstanding, paid this month, cash due record payment, refund, statement filtered list, sticky totals
Comms C · queue + thread waiting on customer · needs reply thread with tracking, templates list → thread sheet
Fitters C · roster + detail free today, utilisation, ratings fitter drawer: availability, rate, docs roster cards
Fitter portal A · stages today's job, one next step photos, complete, report an issue phone-first, thumbs only
Customer portal B · document total, deposit paid, the date accept · change · pay single column, no nav
Templates & settings B · document admin only badge, token warnings editor, stage filter, version history list → editor

The shell is shared, or you get five apps

One of each, everywhere

Every area must answer three questions

  1. Which structure does the work have?
  2. What single summary never leaves the screen?
  3. What is the one action on the row?

If an area can't name its summary, it will grow tabs and folds again — that is the failure mode this whole exercise is about.

What carries over unchanged

Order of work I'd propose

  1. Inbox — it's the entry point to everything else, and it reuses the queue machinery from D.
  2. Quote builder — the document treatment you picked; it's where money is actually made.
  3. Calendar — bookings currently live in the enquiry panel; a real calendar is the first thing that needs cross-enquiry data.
  4. Money — a ledger over the same rows, cheap once the inbox exists.
  5. Comms — mostly done already, as the dock's email panel lifted to a queue.
  6. Fitter portal, customer portal — separate shells, one screen each.

Fixture notes: counts are the prototype's. Structure tags name the variant each treatment comes from: A stage workspaces, B document, C queue + command, D focus desk.