Layouts / Record layoutOpen in Figma

Record layout

Ready

For one record: what it is, its details, its history, and any decision on it.

Platforms Phone · TabletUpdated 26 Oct 2026

Two versions

VersionUseHeader
DefaultEvery record screen unless the brief asks otherwiseWhite header with record number, category and priority, date and requester
Navy headerOnly when asked forNavy record header with who the record belongs to

Default

arrow_backRecord titlemore_vert
categoryCategory
Date and timeABRequestercallchat
notes
SectionSection content that can run over two lines of text
group
SectionSection content that can run over two lines of text
currency_rupee
SectionSection content that can run over two lines of text
chatActivityAdd a commentABNameComment
Current status • timeStatus
1
2
3
4
RegionHoldsRequired
1HeaderBack, record number, more menu; category with priority flag; date; requester with call and chatYes
2DetailsSections on a Field fill, each with an icon, a small caption and the content, split by thin linesYes
3ActivityComments and status changes in one log, with a comment box at the topYes
4Current status barCurrent status and how long ago it changed; the decision buttons sit here when someone must actYes
arrow_backRecord titlemore_vert
AB
Name
Detail
date_range
Label
Value
location_on
Label
Value
devices_other
Label
Value
login
EventDate
1
2
3
4
RegionHoldsRequired
1Record headerBack, title, more menu, who it belongs toYes
2DetailsDetail rows grouped by meaningYes
3HistoryEverything that happened, newest firstYes
4Decision barApprove and Reject, or the one main actionWhen the viewer must decide

Rules

  • Start every record screen from the default version; use the navy header only when the brief asks for it.
  • The status shows once: in the current status bar of the default version, in the header area of the navy version.
  • Activity holds both comments and status changes; there is no separate chat or history page. The navy version ends with a History section instead.
  • Approve and Reject are stacked on phone, side by side on tablet. Reject always asks for a reason.