Software & apps · Practical guide

Explain what Select all includes before a grouped action

A selection checkbox above a table can mean the visible rows, the current page or all filtered records. Visitors may trigger a much broader action than they intended.

Healthcare scheduling software, planning board and organised folders in a blue, white and orange office.
Choose software around the work your team needs to do.

What to change

Ask your supplier to state whether selection covers the visible page or the entire result set, with a clear count and review before consequential actions.

A worked example

Illustrative example

A control states Select all 20 items on this page, while a separate action is required to extend selection to the full filtered set.

Healthcare software workflow connecting task cards, a checklist and a database.
Map the work and the information it depends on.
Healthcare software testing with normal paths and a separate exception route.
Test the exceptions as well as the normal workflow.

Why this matters to your practice

Select all can mean all visible rows or every result across many pages. Before a grouped action, the user needs to know which meaning applies. Ask your supplier to state the scope beside the selection and confirm it again where consequences warrant a review. Demonstrate a list longer than one page, then change its filters. The final selection count and affected items should remain understandable, without relying on an assumption about what was hidden off screen.

A practical review example

A portal list may contain many more items than fit on one page. Ask your supplier to select all, move to another page and change a filter in a fictional example. The selected count and affected scope should remain understandable. If the interface offers a separate choice to select every matching result, make that distinction explicit. A visitor should not discover the meaning only after applying an action, and an off-screen selection should not silently remain broader than the current controls suggest.

How to check the result

Accept when the selected population is visible and unambiguous before a grouped operation, including across page controls and filters.

A mistake to avoid

A single tick in the header cannot communicate selection scope or warn that records outside the visible page are included.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore software & apps services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.