Multiple selection needs to show the selected count
Aliases: selected-item count · selection summary · batch operation
What it is
A selection count is an explicit summary of the current multiple-selection set, such as “12 selected.” It is not a duplicate of checked styling; it externalizes the size of a collection scattered across a list, pages, or filtered results. Before moving, deleting, sharing, or exporting in bulk, people need to know both which objects are selected and how many. Individual marks cannot support that judgment after scrolling or when selection crosses pages.
Why it happens
Multiple selection asks people to maintain a changing set. Clicks, select-all, inversion, filtering, and paging alter its boundary, while hidden retained items make mental counting unreliable. A numeric summary closes the feedback loop: it exposes omissions and accidental inclusions, reveals whether hidden items count, and previews the scale of a bulk command. Without it, people confuse visible checked rows with the entire set or do not know whether “select all” meant this page, these results, or every record.
Studying it
Use tasks requiring continued selection across scroll, pages, and filtering. Compare accuracy of set-size estimates, omission and inclusion errors, bulk-operation undo, and time with and without a summary. Vary the stated scope of select-all, persistence through filtering, and item density. Ask participants to report number and range before an irreversible command, rather than only asking which objects they selected; this exposes confusion between local view and global set.
Where it stops holding
A count does not replace object identity. Sensitive, heterogeneous, or consequential sets still need inspection, exclusion of anomalies, and a comprehensible scope. A single-choice control gains only noise from a count. With infinite scrolling or live data, the number may change in the background and no longer match the set a person saw; state the snapshot time or freeze the selection. Numerical truth matters more than visual tidiness.
Applying it
- Show a count near bulk tools from the moment multi-select begins; update it after add, remove, select-all, filter, and pagination.
- State select-all scope in plain language—current page, filtered results, or all items—and let the count lead to the selected set.
- Before destructive commands, present count, scope, and reversibility together rather than an abstract verb alone.
- Test cross-page and filtered tasks. People should state how many and what range will be affected without recounting checkmarks.