Pattern
Shift brief
The same column as the queue, filled with the handover instead of the waiting. A counted claim about the shift, then what waits, what moved and who is on. 7 grey screens of 62, all 7 already in colour.
Picking up and handing off a shift is the second of the three jobs in the MVP core, and it is the one job in this product that is not about a single case. What makes it the same instrument as the queue rather than a separate reading is that it keeps two of the queue's zones: the counted claim at the top and the keyboard strip at the foot.
Anatomy
Live, in both themes. Two of the four blocks, which is enough to show the two shapes the brief uses: a counted line that opens something, and a counted line that opens nothing and says so.
dark, shipped
19:00 to 07:00 UTC R. Idrissi coming on · D. Okonkwo going off
What waits on a decision
18waiting on a decision across 12 of 40 tenants in your scopeOne of the eighteen has been waiting since 11:40Who is on
The rota is a fact about the shift, not a control. Changing it is a rostering job and it has no screen here.
↑ ↓ read the brief is a reading, nothing here rules on a case
light, the pair
19:00 to 07:00 UTC R. Idrissi coming on · D. Okonkwo going off
What waits on a decision
18waiting on a decision across 12 of 40 tenants in your scopeOne of the eighteen has been waiting since 11:40Who is on
The rota is a fact about the shift, not a control. Changing it is a rostering job and it has no screen here.
↑ ↓ read the brief is a reading, nothing here rules on a case
readoutthe counted claim, and here it counts hours rather than cases. One per screen, and it is theh1pagebanneron this pattern it is almost always the narrow only one, because the whole composition is a desk reading pagebriefthe blocks of the handover: what waits, what moved, who is on, and what is not carried pageqfootthe same keyboard strip as the queue, and it says here that nothing on this screen rules on a case page
Behaviour at width
Below 1280, the system's one point (Width), the brief and the keyboard strip are not rendered, and a narrow only line with a margin of --space-4 says so, because the handover is a desk reading and the phone is for a paged case. Two rules, and they are inside the query on purpose: hoisted out of it they hid the whole brief at every width on seven screens, which the comparison against the committed original caught at stage 08. Above the point nothing here fires, and the column takes whatever the pane does not.
Variants
| Axis | Value | The rule |
|---|---|---|
| variants | none | Seven renderings and one form. What changes is the state of the handover: assembling, sealed, unsealed, outgoing, nothing carried, close failed |
| at 360 | not rendered | The brief and the keyboard strip both go and a narrow only line says why. The handover is a desk reading and the phone has one scenario, a paged case read and escalated |
| verdict controls | forbidden | Nothing on this screen rules on a case. The lines open cases, and the ruling happens in the pane beside it |
When to use it
The four screens of coming on and going off shift, and the three of their failures. It is the second job of the MVP core and it has no other home.
Where she meets it. Twice a shift, at the two moments when she has the least context and needs the most. Everything on it is a count with its scope and its window, because a handover read in a hurry is where a bare percentage does the most damage.
Rule and anti-rule
Do
Fill it with counts that open something. Every line in the brief is a decision about where to start, and a line that opens nothing has to say so out loud: the six Clerk closed alone are named precisely because there is nowhere to review them.
Do not
Put a verdict control in it. This column has no primary action at all, and the one screen that seems to want one, sealing the shift, puts it in the pane beside the brief rather than in the brief. A footer that competes with the main action is what the stage 04 convention forbids in as many words.
Limits
Rules of composition and context that reach this pattern. Full table with sources on Architecture, and every one of them is a function in design/kit/checks/rules.mjs.
- R1. Not more than one
.btn--primaryper layer, and a foot does not compete with it. This column carries none. - R6. One
readoutper screen, and on this pattern it counts hours rather than cases. - R8. A
.only-deskelement never renders at 360 and a.only-narrownever at the desk. This pattern has more riding on that rule than any other, because at 360 it is nothing but its narrow only line.
Where it stands
All 7 grey screens, and there are no others: the handover has one composition and seven states.
All 7 are already in colour. Live, in colour: the shift brief, a shift with nothing carried.
What it is made of, and what moved into it
File: design/system/patterns/shift-brief.css. Imported in index.css after every component and before the places, because a pattern is built from components and has to be able to reach past their own declarations.
Built from readout, banner, brief and qfoot, standing in z4, and through the brief: block, bline, rows-moved and rota. Nothing new was written for it.
Two rules moved in, out of z4.css, and the class moved with them: the product wrote this filling as .z4--shift, which named the host rather than the thing. It is .shift-brief now on all seven coloured screens, and no pixel moves.
One page type in the block bank had no reference anywhere, and it is this one. For every other page type the composition came from product screenshots opened in session; for the shift digest ia/docs/blocks.md records that the comparison column carries the barrier instead. That is worth knowing before anybody copies this composition somewhere it does not belong.