Lookup
Enter data to find and confirm details from a trusted source.
Published: Last updated:
Overview
The lookup pattern allows users to enter a known piece of information and retrieve related data from a system or service. Unlike search, which is exploratory, lookup is used when the user already has a specific value, such as a postcode or vehicle registration, and wants to confirm or expand on it.
Common examples include address lookup using a postcode or vehicle lookup using a registration number. These patterns reduce the need for manual entry and help improve accuracy by returning validated data. Address lookup, for example, allows users to find a full address from partial information such as a postcode.
When to use
- When a user can provide a known identifier (e.g. postcode, ID, reference number)
- To reduce manual data entry and improve accuracy
- When data can be retrieved from a reliable external or internal source
- When the system can confidently return a small set of relevant results
When to not use
- When users are exploring or unsure of what they’re looking for (use search instead)
- When no reliable data source exists to return results
- When the result set would be too large or unclear to select from
- When all required data must still be entered manually
- Labels – Clearly describe what information the user needs to enter and set expectations for the lookup.
- Input field – Captures the required data for the lookup. This is typically a text input but may include grouped elements where additional context is needed (e.g. prefixes or formatted inputs).
- Lookup actions – Provide the possible next steps based on the input, such as triggering the lookup or offering an alternative path like manual entry.
Lookup phases
The lookup pattern is made up of a small number of distinct phases that guide the user from input to confirmation. Each phase builds on the previous step, helping users provide, refine, and verify information.
Phase 1: Data input
The user enters a known value, such as a postcode, reference number, or identifier, to initiate the lookup.
Phase 1b: Selection (optional)
If multiple results can be returned, the user selects the correct option from a list of matches. This step is commonly used in scenarios like address lookup, where several results may exist.
Phase 2: Summary
The system presents the retrieved data in a structured format, allowing the user to review and confirm the information before continuing.
Input phase
The lookup input phase is where users enter a known value to retrieve related information. It should be simple, focused, and clearly guide the user toward completing the lookup. This stage typically combines a labelled input with supporting context and clear actions, helping users understand what to enter and how to proceed.
The layout should prioritise clarity and minimise friction, ensuring users can quickly provide the required data and trigger the lookup with confidence.
Summary phase
The summary phase presents the data retrieved from the lookup in a clear and structured format. It allows users to review and confirm that the information is correct before continuing, helping to build confidence in the result.
This stage should prioritise readability and clarity, making it easy to scan key details at a glance. Where appropriate, users should be able to edit or retry the lookup if the information is incorrect, ensuring the flow remains flexible and user-controlled.
When this type of lookup summary is used it replaces the lookup component used for entering known data.
- This car:
- is right hand drive (UK standard)
- has 5 seats
- has no tracking device
- has a manufactirer-fitted immobiliser/alarm
- is not imported
- estimated market value is £3,470