Skip to content
Interface language: English
Design / Signal

A suggestion is not yet a choice: a field for selecting a specific record

Separate typed text, highlighted suggestions and confirmed records in autocomplete fields.

Article language: English

A person beside a partition and a patterned surface in an interior.
In this article

The “Branch” field displays “Rzeka Studio”. The form looks complete, so the user continues. Only the summary reveals a warehouse on the edge of town instead of a service point in the centre. The suggestion was meant to save typing. It also chose, on its own, the place to which someone will travel with a tube of drawings.

In this hypothetical form, similar names represent different entries in the data. Typed words, the item highlighted in the list and the finally confirmed branch need not be the same thing. The design should show those differences rather than leave them as an invisible component setting.

A field with suggestions helps choose one record, a specific entry in a defined set of data. It may concern a location, product, organisation or contact person. Its result must identify a particular object. A neatly completed label is only part of that task.

First decide whether the user is searching or selecting

An ordinary search field accepts a query. “Rzeka” may lead to results containing that word. A branch-selection field must end with one entry that the form can use later. If the list serves the second purpose, say so in the instruction: “Type a name and select a branch from the list”.

Decide whether a value outside the catalogue is allowed. That is a process decision, not a visual detail. If an order must reach an existing branch, a freely typed new name is not enough. If a customer may name another organisation, provide an explicit “It is not on the list” route, with a separately identifiable result.

Do not switch between the two rules depending on whether the tool happens to find a match. Otherwise a typo could turn selection of an existing company into creation of a new one. The user should consciously recognise whether they selected a catalogue entry or supplied their own text for further checking.

When no item matches, offer a next step consistent with the process. It might be searching by town or contacting someone who can establish the right location. Do not offer to add a branch if the customer lacks that permission. A user-supplied value needs a distinct description and state; it must not look like an approved catalogue entry simply because both results fit in one field.

The W3C APG describes a combobox, a field associated with a popup, and distinguishes suggestions selected manually from automatic selection. These are different acceptance behaviours described in the pattern guide. A dropdown alone does not determine what happens when the field is left.

Prepare three states to show on the studio prototype:

  • “Rzeka” has been typed but no branch selected. It is a query from which suggestions will be produced.
  • “Rzeka Studio - warehouse” is highlighted in the list. The user is exploring an option, but the design rule must decide whether it is already selected.
  • “Rzeka Studio - centre, Lipowa Street” has been confirmed. The form has a recognisable result with a specific location.

The appearance of states should match their meaning. Do not show a green confirmation merely because the field contains letters. If a record must be selected, the error should explain that and retain the query so the customer does not start from an empty field.

Agree search scope with the catalogue owner. Can people search by full name, town, code or former name? Users do not need technical documentation of those rules. A short hint such as “Name or town”, however, must reflect what the list actually supports.

If the task is finding content rather than selecting a record, a better solution may follow from designing an internal B2B site search (in Polish). Search results should lead to material. Here the choice must also become an unambiguous value in the form.

A suggestion must make the difference recognisable

Two entries with the same visible name need additional context. For a branch that might be town, address and location role. For a product model it might be code and variant feature. Do not show the entire record just because it is available. Choose data that distinguishes the options for this task.

In our list the warehouse and service point should differ before the click. Shortening both to “Rzeka Studio...” removes exactly the information needed to choose. Designing long names and text in an interface (in Polish) requires preserving the meaning of the distinguishing ending, even if the name takes two lines.

Check information order with real material. If every branch starts with the company name, the first characters may be of little use. A town or location type may guide the eye better. The full identity should still be available before confirmation, not only on the next screen.

A form for international partners may mix writing directions, names and numeric codes. Do not assume aligning everything to one side is sufficient. Two text directions in names, codes and addresses (in Polish) require a readable relationship between fragments. In acceptance testing, reproduce the lengths and writing types present in the catalogue using a controlled sample. A Polish demonstration name alone will not test mixed text.

Also enter a name with a common abbreviation or diacritic. If the search does not recognise it, the interface can suggest another route, such as a town. “Try entering a town” gives a concrete way to continue. An empty result may reveal a limitation in the matching method.

Do not distinguish options by colour alone. Someone exploring the list should receive the name and context with a keyboard or screen reader too. Test the complete suggestion announcement, not only how attractive the highlighted part of a word looks.

Aeneia conceptual photography

On a phone, check the view with the keyboard open. People should see differences between suggestions and reach later items if the list scrolls in its own area. When a name takes two lines, the item height must not cut off the address. In the trial, also scroll to the end of the available set and return to the field. Decide whether closing the keyboard closes the list and what happens to a choice in progress.

With very similar records, avoid automatically merging entries to make a “tidier” list. That is a separate data decision. Checking false matches when AI merges records (in Polish) shows why similarity of name does not establish identity. Presentation can be simplified, but the difference between a warehouse and a service point must not be lost.

Aeneia Design

Aeneia Design can design selection from a large catalogue: recognisable suggestions, clear confirmation and behaviour after the text changes. We will base the work on actual names and situations in which a user might select misleadingly similar entries. Design an unambiguous record selection

What is confirmed when the field is left?

A user can type a fragment, move through the list with arrows and click the next field. What remains selected? In GOV.UK's accessible-autocomplete component, confirmOnBlur can confirm the indicated option when the user clicks outside the control. This option is described in the component documentation. A library default does not replace a decision about your own form's behaviour.

For branches with similar names, test a variant requiring explicit confirmation. Looking through several suggestions with the eyes or keyboard then serves to explore them. Only clicking an item or using the agreed keyboard action assigns the branch. The person completing the form should recognise what happened without reading the name of a technical setting.

Check Enter, Tab and Escape in the whole form. If Enter confirms a suggestion, it should not unexpectedly submit the entire request in the same action. If Escape closes the list, decide whether it retains an earlier choice. Behaviour should follow the chosen pattern rather than an accidental combination of two event handlers.

After confirmation, show enough information to recognise the choice. “Rzeka” alone does not establish whether the form stores the centre or warehouse. The name with address can remain in the field or beside it. There is no need to show a technical identifier to the customer if it does not help them recognise the place.

The stored result must nevertheless retain a link to the specific record. A name may change later. Storing only the text is insufficient to establish which branch was selected when two have similar names. Agree implementation details with the data owner and implementer; acceptance must confirm the right object and a readable presentation.

Then add a character to the confirmed name. This is a key trial: does changing the text invalidate the selection, or does the form still send the old branch identifier? Visible text and hidden result should not tell different stories. Show that the item needs to be selected again or provide a clear change action.

A branch may depend on an earlier service choice. After switching from consultation to material collection, check whether the selected location still fits. If not, name the reason and request a new choice while preserving the remaining data. Do not keep the old identifier under the new service merely because the branch name still looks correct in the field. The catalogue owner confirms the rule; the design shows its effect.

A similar distinction applies to choosing a date on a site (in Polish). Typing a recognisable date does not always mean an available time has been confirmed. For a branch too, distinguish entered text from a value accepted under the task's rules.

The list may arrive late or not at all

Design result loading. If a list fetches data after a few letters, distinguish that state from no matches. Showing “Not found” before the response finishes encourages people to change a correct query. If fetching fails, explain the problem and offer retry while preserving the typed words.

In a trial, enter two different queries quickly and arrange for their responses in reverse order. A later-arriving list for the earlier text should not replace results for the current query. Users may not notice suggestions no longer match what they see in the field. Choosing from that list produces a technically correct record for the wrong context.

Separately test additional results arriving while the list is being explored. If the user highlighted the third branch, new entries should not silently move the indication to another object. The active suggestion must be tied to a record, not only a row number. Otherwise Enter may confirm its neighbour even though the person has already read the earlier item's name. Repeat the trial when suggestions are reordered.

Also test selecting an item that has meanwhile been withdrawn or stopped handling this type of request. The interface should name the problem with that specific choice and allow it to be changed. Do not replace the branch with the first available entry without the user's knowledge. Availability in the catalogue does not make locations interchangeable.

On returning to a saved form, show what could be restored. If the identifier still exists, its current name may differ from the remembered one. If the item has disappeared, explain that a new choice is needed. Other form fields need not be cleared for that reason.

Accept the field against awkward names: very long, identical to another, containing a code and absent from the catalogue. Ask a participant to select a specific location and explain what was chosen. Also observe the moment they leave the field. Check whether the first suggestion was selected without conscious confirmation.

This work can be combined with interface design at Aeneia Design. The result should align three things: the user's intent, information visible in the field and the object passed on. Then the tube of drawings will travel to the chosen location, even if the warehouse has almost the same name.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear