Layout
Composition principles
Keep the application reference and current status in the first viewport. Use a single reading column for explanations and a separate summary list for dates and contact details.
GOV.UK Design System / Published template
Government Application Status Service
A plain-language service for checking an application, understanding its current stage, and responding to required actions.
Prompt reference v1
Preview
Structure blueprint
A restrained service header leads into one prominent status panel, a vertical stage history, and a short list of next actions.
Interaction
Behavior and access
Every status change is expressed in text. Action links use specific labels, validation moves focus to an error summary, and the history remains usable without client-side JavaScript.
Implementation
Engineering boundaries
Render the status and history on the server with semantic headings, description lists, and ordered lists. Do not expose internal caseworker notes or infer eligibility in the UI.
Design system
GOV.UK Design System token ledger
The public design system for consistent and accessible UK government services.
Color roles
- model
- service palette
- requiredRoles
- page, text, link, focus, error, success
Typography
- approach
- plain-language service hierarchy
- requirements
- short line lengths, prominent labels, clear error summaries
Spacing
- approach
- consistent service spacing
- baseUnitPx
- 5
Component rules
- forms
- Ask only for necessary information and place errors next to the field.
- content
- Use plain language and one primary task per page.
Classification