Layouts / Record layoutOpen in Figma
Record layout
ReadyFor one record: what it is, its details, its history, and any decision on it.
Two types
| Type | Use for | Header |
|---|---|---|
| Owned record | Something that belongs to a person or animal and stays valid over time | Navy record header |
| Request record | A request or ticket that moves through steps and gets comments | White header with category and priority |
Owned record
AB
Name
Detail
date_range
Label
Value
location_on
Label
Value
devices_other
Label
Value
login
Event
| Region | Holds | Required | |
|---|---|---|---|
| 1 | Record header | Back, title, more menu, who it belongs to | Yes |
| 2 | Details | Detail rows grouped by meaning | Yes |
| 3 | History | Everything that happened, newest first | Yes |
| 4 | Decision bar | Approve and Reject, or the one main action | When the viewer must decide |
Request record
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
| Region | Holds | Required | |
|---|---|---|---|
| 1 | Header | Back, record number, more menu; category with priority flag; date; requester with call and chat | Yes |
| 2 | Details | Sections on a Field fill, each with an icon, a small caption and the content, split by thin lines | Yes |
| 3 | Activity | Comments and status changes in one log, with a comment box at the top | Yes |
| 4 | Current status bar | Current status and how long ago it changed; the decision buttons sit here when someone must act | Yes |
Rules
- The record's status shows once: in the header area of an owned record, in the current status bar of a request record.
- A request record's activity holds both comments and status changes; there is no separate chat or history page.
- History is the last section; on mobile it replaces separate audit pages.
- Approve and Reject are stacked on phone, side by side on tablet. Reject always asks for a reason.