The same action repeats across a dozen similar records
A user opens a record, acts, closes it and repeats this on a dozen records that share a cause and need the same decision.
The user decided once for the whole group, and the interface asks for twelve separate decisions.
A bulk action needs explicit eligibility, a preview of the affected records and a result for failures or skipped items. Similar appearance or a shared source does not guarantee that all records should receive the same action.
Key facts
- Records are modelled as separate decisions, which suits the data layer.
- Users decide at group level, by cause, source or type.
- Systems group by date, status or owner.
- Bulk actions look like a convenience during planning and become required once daily volume arrives.
- Repeated confirmation may be avoidable when records genuinely share the decision, permissions and preconditions; exceptions still need review.
Why it happens
Records modelled as separate decisions. That suits the data layer. Users decide at group level.
No matching grouping. Systems group by date, status or owner. Users decide by cause, source or type.
During planning they look like a convenience. Once daily volume arrives they are required.
How it shows up
- The work is saved for a weekly session
- The queue is cleared in bursts
- Users export, act outside the system and import the results
- Support requests ask for a way to act on all of them at once
- Records nobody needs to review pile up
Options and trade-offs
What helps:
- Selection and bulk action on the same screen as the single action
- Grouping by the attribute users decide on, learned from how they batch work
- A preview of what the bulk action will change, by count and by record
- Undo, or a confirmation sized to the action
The tension: bulk actions let users make large mistakes quickly. Without preview and undo the feature moves the risk around and saves little.
Common mistakes
- Postponing bulk actions as a convenience
- Grouping by date, status or owner when users decide by cause
- Bulk actions on a separate screen from the single action
- A bulk action with no preview of what will change
Where we’ve worked on this