Brief #4, fluent-2. A ward team inside Teams. The night team hands Ward 7 to the day team at 07:00, and this is the screen both of them stand at while it happens.
The four direction lines
- Archetype: shell. A persistent rail, a top bar and one content well, for a team that returns to the same place every twelve hours.
- Data stance: tile-first. Four tiles, and each one states its change since the 19:00 handover. A number with nothing to compare it against does not go up there.
- Density: compact. 32px controls, 24px controls inside a thread entry, the 4px spacing grid,
body1at 14px. - The one bold thing: the handover thread holds the primary column and the tiles are the secondary surface. The words a nurse writes at 06:52 outrank every count on the screen.
What the critique round changed
The inversion was asserted and not composed. h1 and .metric-value were both fontSizeHero700, so four 28px figures stood against one 28px heading while the primary column's own h2 sat at 16px: the tiles were the headline. The figure came down to fontSizeBase600, the thread's heading went up to fontSizeBase500, and below 640px, where the title itself drops to 24px, the figure drops again to 20px so the heading is the largest thing on the screen at every width. On a phone the four tiles had also stacked into 474px of numbers between the title and the first word anybody wrote; they are two columns there now and the thread starts on the first screen.
Five behaviours were wrong rather than missing. Sign off as read, the only control drawn as primary and the act the screen exists for, did nothing. A posted entry took its time from the reader's clock, so it landed at 02:21 under an entry timed 07:02 in a column whose whole meaning is the order. 14 entries since 19:00 never moved: not when the filter hid twelve of them, not when somebody posted a fifteenth. Posting under Escalations only left the new routine entry on screen with the filter still pressed. And the ward and category menus carry role="menu", which is a promise about the arrow keys that only Escape was keeping.
The second state
The entry that did not send. A day charge nurse types the one thing with a clock on it, a repeat sample the theatre slot depends on, and the post fails. It sits in the thread where she wrote it, marked as reaching nobody, with two ways out: send it again, or move it back to the box she wrote it in. Both are live on the page. The composer's empty-submit validation is live too.
Generator
fluent_theme.py --mode both
tokens.css is that output, unedited. The audit acted on:
fluent_theme.py --contrast --mode dark
which passes every required pair and reports colorNeutralStroke1 at 2.53:1 as a decorative divider. The page draws no hairline at all: the composer separates from the thread by receding one neutral layer instead. Every control boundary reads colorNeutralStrokeAccessible.
Measured contrast
Read out of the rendered page with getComputedStyle, and confirmed with contrast.py:
colorNeutralForeground1oncolorNeutralBackground1, the thread body at 14px: 15.52:1 light, 14.55:1 dark, against a 4.5:1 minimum.colorNeutralForeground3oncolorNeutralBackground1, times and roles at 12px: 6.19:1 light, 6.48:1 dark, against a 4.5:1 minimum.colorPaletteRedForeground1oncolorNeutralBackground1, the adverse comparison: 5.85:1 light, 5.20:1 dark, against a 4.5:1 minimum.colorPaletteDarkOrangeForeground1oncolorNeutralBackground1, the warning comparison: 5.45:1 light, 5.45:1 dark, against a 4.5:1 minimum.colorNeutralForeground1oncolorNeutralBackground1Selected, the selected rail item and its count: 13.02:1 light, 11.73:1 dark, against a 4.5:1 minimum.colorNeutralForeground2BrandSelectedsat here first and measured 4.18:1 in dark at both 14px and 12px. The filled icon, thecolorBrandStroke1indicator and the selected background already mark the selection, which is what Fluent asks for, so the brand did not need to sit in the text as well.
The lever spent against the neighbouring index
direction_check.py --compare put Rota and Carbon's Grid North at 0.83 against a 0.75 ceiling. The lever is elevation, which is the one structural language Carbon has no word for: it rules its regions and forbids shadows, while Fluent layers colorNeutralBackground1 through 6 and lifts what floats. So the thread surface lifts off the canvas on shadow2 and borderRadiusLarge, the four tiles stay flat on the canvas, and the composer recedes to colorNeutralBackground2 inside the lifted surface, which is what let the last decorative hairline go. The elevation now carries the bold thing: the primary column is the only region on the page that lifts. The pair reports 0.67, distinct, and Rota's highest similarity against any of the other eighteen pages is 0.59.
Deviations
- The page authors three widths rather than reading them from a token: a 208px rail, a 320px side column and a 1300px cap on the well. Fluent tokenizes no layout grid, since a Fluent surface lives inside a host whose width it does not control. Without the cap a 1920px screen gave the thread surface 1324px to carry a 68ch measure, so two thirds of the primary column was empty on every entry.
- The composer sits at
fontSizeBase400(16px) where the rest of the page is compact at 14px. Fluent gives 16px to text somebody writes rather than scans, and it keeps iOS from zooming the field on focus.
The uplift round (2026-10-29)
What changed, in the order a visitor meets it:
- Each tile draws its change. A step line from 19:00 to 07:02 with the shift's starting value as a dashed reference, so the gap between the dashed line and the end dot is the delta printed under it. One table in the script drives the number, the line, the sentence and the screen-reader label.
- The figures now add up. The old page said 3 more patients and 4 fewer free beds. It is now 23 to 26 patients and 5 to 2 free beds, always 28 in all, with the admissions at 22:10, 01:30 and 04:45 being entries in the thread. Escalations open is 3 (one carried from before 19:00, bed 14 raised 03:50, bed 12 raised 05:40); the unsent bed 17 entry is the fourth and is not counted until it reaches the ward.
- The ten earlier entries exist. "14 entries since 19:00" is counted from the thread (10 earlier, 4 shown, the unsent one excluded), behind one disclosure. The Escalations filter opens them, because it has to count them.
- The interaction. What is owed by a clock is a line down the morning, now at the top, each row a button that goes to the note that explains it. The 08:15 sample for bed 17 is flagged at risk because the 07:02 entry has not been sent. Sending it clears the flag, ticks escalations open from 3 to 4 in the tile, the rail and the tab bar, and extends the line. Posting an escalation from the box does the same. The rail items are real: Escalations is the filter, Tasks, Bed board and Staffing go to their lists.
- The phone is a bottom bar (Handover, Escalations, Tasks, Beds with counts) and a compose button that raises the box as a modal sheet with its own Tab loop and Escape. The sheet exits in 200ms on the accelerate curve.
- Real names and units. Colourful avatars from Fluent's named palette instead of brand blue on every face, bay-grouped beds (seven bays of four, matching "Bay 1, beds 1 to 4"), a name with diacritics, narrow no-break spaces before units, the year in the date. Leaving-today beds are the discharge green, not brand.
- Design notes sit open on the canvas with the bold decision set as the pull statement, and the two measured pairs shown as live swatches with a bar per ratio and the 4.5 floor marked. Ratios are unchanged from the audit above.
- The rail is a full-height column with a sticky inner, so it no longer stops at the first screen on a long page.
Not done on purpose: no Mica or acrylic. Fluent puts Mica on a native window's base layer and acrylic on transient surfaces over content; a web page has no window base layer, and the menus are opaque. Generator command unchanged.
Round two: the first screen has one moment
The four equal tiles were the fold and nothing led. What a ward team opens Rota to learn is the one thing owed by a clock that is about to be missed, so that is now the screen's moment: 08:15 at fontSizeHero1000, "Repeat group and save, bed 17" at fontSizeHero800, on the status-danger layer, with a runway drawn to scale from 07:02 through the 08:15 lab cut-off to the 09:30 slot (73 of 148 minutes filled). Fluent spends emphasis through its type ramp and its status layer, not a shadow, so the thread stays the only region that lifts. Brand blue sits on one control, the send that fixes it, so Sign off as read is outline until the screen is signed. The moment reads the same state as the thread, the Escalations tile, the line down the morning and the rail: send the 07:02 entry and the surface turns to the success layer, escalations go from 3 to 4, and the figures still agree (1 h 13 min everywhere). The tiles keep every figure and sparkline at 20px, a level below. The title and h1 no longer compete: the heading is not the largest thing on the screen by design.
Round four
- The four tiles now draw their chart across the tile's full width, in the pixels it is shown at (redrawn when the tile resizes), so the note on the escalations line stays one readable size and the figures read as shapes; each tile's change line sits at its foot so the four end level.
- "Beds at 07:00, by bay" left the side column. It is a band under the four figures: seven bays across, every bed a numbered cell (the numbers the thread uses: bed 8, bed 19, bed 26 leave; beds 15 and 28 are free), with the key on the right. On a phone the bays wrap. The nav's Bed board link still lands on it.
- On a phone the "Add to the handover" button appears once the thread is on screen and is hidden over the figures and the ward map, so it never sits on a tile.
Round eight
- Design notes read as three uneven columns of 16px paragraphs under oversized type (real). Cause:
.spec dlwas a two-column grid of 16px (fontSizeBase400) paragraphs beside a third column for the figure, so the notes were wider and larger than anything the product itself sets. The notes now keep the product's own grid: the same1frand 320px columns and gap as.work, each note a row with its label where an entry's author sits and its sentence at the thread's own 14px body and a 68ch measure. The readability figure sits in the 320px column, directly under the side column. - A large empty area right of the thread, beside the composer (real). Cause: the side column ends at its own height, about 320px short of the thread. At 1081px and wider, on a screen 760px tall or more,
.sideis now sticky below the top bar, so it travels down the page beside the thread and the composer. - The first screen did not spend the bold thing. The brief says the thread outranks every count, but at 1440 by 900 the thread began below the fold, under the four figures and the 170px bed map. The bed map moved to sit under the thread (
#bedsand every link to it are unchanged), so the thread heading and its first entry are on the first screen. The 08:15 moment stays first, since it is the 07:02 entry's consequence. - Declined: no card around the notes. The thread is still the only region that lifts.
Round nine: below the fold, driven states, the real phone
Found by driving every state, by a real-phone context (isMobile, hasTouch, scale 3, at 390 and 360), by a 200% pass at 720px and by a width sweep from 320 to 1920 in 10px steps. No horizontal overflow at any width. Heuristic total 29 before, 30 after (consistency 2 to 3); the moments behind every score under 3: no shortcuts on a screen used twelve-hourly (flexibility, 2), no help beyond the hint under the box (help, 2), and a sign-off that cannot be taken back (control, 3).
- The Handover icon, in the rail and on the tab bar, was a solid black block (real). Cause: the filled Handover glyph drew its two text lines as sub-paths with the default fill rule, so they filled instead of cutting out. It now uses
evenodd, and the lines show in the rail, on the phone bar and in both themes. - Controls were 24 to 40px on a phone (real). Every button in a thread entry was 24px tall, the rest 32 to 40. Wherever the primary pointer is coarse every control is now 44px, measured at 390 and 360 with nothing left under it.
- A new entry or the sign-off was stamped 07:05 and 07:08 under a screen that says Now 07:02 (real). The page is the handover as it stands at 07:02, so a reader's entry and the sign-off are stamped 07:02 too, and "in 58 min", the runway and the four charts stay true to the same minute.
- The kind menu in the phone sheet opened off the bottom of the screen (real). It opens upward inside the sheet.
- At 641 to 1080px the fourth tile stood alone on a second row, the seventh bay stood alone beside a void, and the top bar broke onto two lines. The tiles are four across or two by two, the seven bays always share one row down to 641px and become a row each on a phone (label, then beds 1 to 4, as on the ward), and the shift chip, which repeats the page's own date line, goes below 880px.
- Entries on a phone started differently (name and time on one row, or the time alone on its own). The role now always takes its own line under the name, the time stays beside the name, and the two unsent-entry actions stack at full width instead of wrapping inside their buttons.
- Smaller: the ward menu no longer wraps "Ward 7, acute medicine"; the count beside "Handover thread" sits against the heading rather than floating between it and the filter; "On the ward now" listed a bank nurse who is not due until 07:30, so it is "Who to ask".
Round ten: the heuristics that sat below 3
Scored again from scratch before anything was touched, driving the ward handover at 1440, 390 and 360 (a real-phone context: isMobile, hasTouch, scale 3) in both schemes. Round nine's 30 and this round's opening 25 are two readings of the same page; this one is stricter on the moments, and the cut is where the screen asks a nurse to act with no way back.
Before, with the moment behind each score under 3:
- Visibility 2: on a 390px phone, Post closed the sheet and the new note landed 760px below the viewport. The only sign it had gone was the count under the heading.
- Control 2: sign-off, Mark as read and a post could not be taken back.
- Error prevention 2: one press on Sign off marked five entries read, two of them escalations (bed 14 and bed 12), while the 07:02 entry for bed 17 had not reached the ward and the 08:15 sample was at risk.
- Flexibility 2: 25 Tab stops from the top of the page to Post, no shortcut, and a thread of 14 entries that could only be walked with Tab.
- Help 2: one hint under the box. Nothing said what "Read by 3 of 4" counts, what "has not reached the ward" means, or what an escalation changes.
- Match, consistency, recognition, aesthetic and recovery were 3. Recovery's moment was the unsent note: it said that it had not sent, never why.
What changed, and why:
- A toast after every act that matters (Fluent's Toast: a title, a line of detail, an action, a dismiss). Post, sign-off, the send that reaches the ward and a reopen each say what happened. Post and sign-off carry Undo for ten seconds, held still while the pointer or focus is on the toast. A post taken back returns its words and its kind to the box and takes its escalation off the tile. On a phone the note is also scrolled to the middle of the screen and takes focus, so the person who wrote it sees it on the ward.
- Sign-off asks only when something is open. If entries are unread, an entry is unsent or the box holds an unposted note, a dialog names each in the nurse's own terms (bed 14 at 04:20 and bed 12 at 06:52; the 07:02 entry about bed 17 and the 08:15 sample at risk), each with a link to go there. If nothing is open it signs off in one press, as before. The dialog's focus starts on Go back. A Reopen button stays beside the signed-off state, so the act is reversible after the toast is gone.
- Mark as read is a toggle. Pressing it again takes the mark and the count back. The five identical buttons now carry whose note they belong to ("Mark as read, the 06:52 note from Priya Raman").
- Shortcuts, as Teams has them. With a modifier, anywhere: Ctrl+/ opens the list, Ctrl+Shift+X goes to the box, Ctrl+Enter posts from it, Ctrl+Z undoes the last toast act when not typing. Single letters (J, K, R, E) work only with focus in the thread, so they never catch a key meant for something else. A second skip link, Skip to the thread, puts focus on the first entry. The Ctrl+Enter hint shows beside the box on a fine pointer only.
- Help in three places. A Help button in the top bar (an icon on a phone) opens a dialog with what four phrases on the screen mean and the full shortcut table. Three InfoLabels, Fluent's label-plus-button-plus-popover, sit where a question arises: beside "Owed by a clock", beside "Escalations open" and beside the box's label. Escape, a press elsewhere and a second press close a popover; it keeps clear of the screen edge. The information button is 24px to look at and 44px to touch on a phone.
- The unsent note says why. "The connection dropped when it was sent at 07:02, so it is saved on this device only."
Dialogs are the native element, so Tab, Escape and focus return are the browser's. On a phone they rise from the bottom edge like the box's own sheet. Every new surface has a reduced-motion path that shortens, exits stay under 250ms, and print hides all of it.
After: every heuristic is 3. Nothing is a 4. What keeps flexibility at 3 is that the thread filters on one thing, escalations, and cannot be narrowed by bed or by bay.
Not done on purpose: the toast is not a live region, because the page's one status line already announces each act and a second announcement would say it twice. Generator command unchanged.
Round eleven (2026-11-10)
Two defects from an independent score, both reproduced before any edit.
- The ward switcher relabelled its button and changed nothing (severity 3). At 1440, Ward 7 menu, ArrowDown twice, Enter: the button read "Ward 12, frailty and short stay" over Ward 7's patients, with no announcement, the rail still labelled "Ward 7". The brief gives one ward's handover and no other ward's patients, so the switch cannot be made real without inventing them. Fix: the menu stays, as the one place the other wards are named, but Ward 9, Ward 12 and the Ambulatory unit are
aria-disableditems marked "Not in this view". They stay in the arrow-key order (Fluent's disabled items are focusable). A press or Enter keeps the menu open and says "Ward 12 is not in this view. This page is the Ward 7 handover." in the status line. The header, rail and tab bar can no longer name one ward over another's patients. Related, found while driving it: on a phone the open menu hung from the button, not the bar, so its right edge sat 81px past a 360px screen (the page grew to 441px); it now hangs from the bar (8px to 352px at 360). - The toast sat across the compose sheet on a phone (severity 2). At 390 dark, send the 07:02 entry, open "Add to the handover" inside ten seconds: the toast covered y 628 to 724 over a textarea at 593 to 678, and the lower half of the field returned the toast. While the sheet is open (
has-sheeton the body) the toasts move to the top edge, y 12 to 108, and return to the bottom when it closes. Taps on the top, middle and bottom of the field now land on the textarea at 390 and 360. The toast over the first filtered entry is the same bottom dock; it is dismissible and now leaves sooner (below).
Inventions, each minimal: the words "Not in this view" and the status line above; a toast with no Undo leaves after six seconds instead of ten (the ten are the window to take a post or sign-off back, and the grace after the pointer leaves was already six). No patients, counts or ward facts were added.
Round thirteen (2026-11-10)
One defect from the round-twelve score, reproduced at 1440 light, 1920 dark, 390 dark and 360 light before any edit: the moment card out-ranked the thread the brief says leads. The direction line says "the words a nurse writes at 06:52 outrank every count on the screen"; the card set its time at Hero 1000 (68px) and its title at Hero 800 (32px) against a thread heading at Base 500 (20px) and a 28px page title, so the clock was the largest thing on the screen at every width (40px against a 24px title on the phones), and the card plus the tiles put the thread at y 729 at 1440 and y 1197 at 390.
Round two made the clock the screen's moment. This round keeps the clock as the card's lead and ends its claim on the whole screen. The ramp is now four distinct Fluent steps, each at semibold: page title Hero 800 (32), thread heading Hero 700 (28), card time Base 600 (24), card title Base 500 (20). On phones: title Base 600 (24), thread heading Base 600 (24), time Base 500 (20), card title Base 400 (16). Urgency is carried by what was always carrying it, not by size: the danger layer, the filled alert icon, "in 1 h 13 min" in the danger foreground, the runway and the one brand-blue send. Nothing moved in the DOM, so the focus order is unchanged; on a phone the runway label row is 40px, not 56px, which takes 16px off the card. Measured by computed size and position, and with hierarchy_probe.py driven headless: the largest type on the first screen is the page title, then the thread heading (visible from y 657 at 1440 and 1920, where it was y 729), then the time, and focal-competition is quiet at 1440 and 1920. The thread still starts below the tiles on a phone (y 1119 at 390), because four tiles with sparklines stand between; reordering them would break tab order, so they stay.
Invention: none. No words, figures or states were added; the sent state (card turns to the success layer, "no longer at risk") was driven at all four widths and still works.