Low Fidelity
Component Notes
Toggle State — Low
ContentLorem / placeholder
StatusOff
FiltersOff
ActivityOff
Reuse
Same component as LegalOps billing dashboard. Matter table rows, status pills, and matter ID formatting are shared across the intranet and the billing attorney product — one component built, consumed in two surfaces.
Fidelity Range
Low: consultants frame the table layout. Mid: real matter names surface client asks about data fields. High: filters, invoice aging, and activity sparklines appear when client asks "how would they sort or search?"
Low Fidelity
Component Notes
Toggle State — Low
AmountsOff
StatusOff
SummaryOff
ActionsOff
Connection to Billing Intelligence
High fidelity surfaces the "Prepare comms" action. This is the same interaction pattern as the LegalOps billing attorney product — invoice aging drives a communication trigger. The component demonstrates continuity between the intranet and the billing product at requirement definition time.
Low Fidelity
M
T
W
T
F
S
S
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Component Notes
Toggle State — Low
ColorOff — neutral gray
StatusOff
AlertOff
LegendOff
Design Decision
Red/green at the day level. No need to open a record to know if time is missing — the calendar surface carries compliance status. Green means complete, red means missing, no color means weekend or future. The pattern is universally legible without a legend.
Fidelity Range
Low: grid layout and interaction model. Mid: real dates with red/green coding — client sees the pattern immediately. High: missing-day alert banner, billing close deadline, hover hours — everything needed to act.
Low Fidelity
Component Notes
Toggle State — Low
NamesPlaceholder
HoursOff
AlertsOff
SummaryOff
Role Separation
Supervision, not surveillance. The managing attorney sees pattern and coverage — which timekeepers are missing entries, total weekly hours, alerts. They don't see the content of the time entries, only the compliance signal. Same principle as the billing dashboard: surface what's needed to act, nothing more.
Fidelity Range
Low: grid structure and row/column model. Mid: real names, hours, and red highlighting for gaps — client immediately sees the value. High: summary stats, alert badges, row-level highlighting, and filter controls.
Low Fidelity
Component Notes
Toggle State — Low
ImageGray block
TextLorem
CategoryOff
Action tagOff
Fidelity Range
Low: image block + text block proportions. Mid: real headlines + category tags — client can validate information hierarchy. High: image gradient header, author, excerpt, and action-required badge for policy items.
Low Fidelity
Component Notes
Toggle State — Low
AvatarGray circle
NamePlaceholder
BodyLorem
ReactionsOff
Social-Style Card
High fidelity adds social engagement signals. View count, reaction counts, and comment thread — clients often didn't anticipate this pattern until they saw it. Surfacing it in the wireframe made the interaction model legible before dev investment.
Low Fidelity
Component Notes
Toggle State — Low
IconsGray block
NamesPlaceholder
FiltersOff
ActionsOff
Version & Read States
High fidelity introduces update and unread signals. "New version available" and "Unread" status badges surfaced a conversation about notification architecture that wouldn't have happened from a static list. The wireframe component generated the requirement.
Low Fidelity
Component Notes
Toggle State — Low
AvatarsGray circles
NamesPlaceholder
ActionsOff
StatusOff
Availability Status
High fidelity adds presence indicators. Green / amber / gray availability dots — Available, In a meeting, Offline. This triggered a client conversation about real-time directory integration that wouldn't have surfaced from the card list alone.
Favorites Filter
The favorites tab is a personalization layer — each attorney sees their own pinned contacts. Mid fidelity doesn't show this; high fidelity makes the personalization model explicit and prompts the client to define the rules.