Can a search bar have multiple actions that the user can take on it?

Context: I'm designing a system for a bike shop to manage the maintenance of all their bikes. Currently the mechanics fill out generic paper sheets by hand and once a month the manager manually adds them all to a google doc. The new system would let mechanic print out a custom paper sheet, then go into this app and update it themselves.

Problem: So the mechanic has two actions they need to do once they've entered a bike's number: print out the sheet, and log the repair. Is it acceptable to do two action buttons underneath a single search? I'm imagining it a bit like the Google Homepage, where you can do both 'search' and 'I'm feeling lucky'. If you hit enter, it would default to logging the repair.

Is there any UX pattern this is breaking? Is it intuitive?

low fidelity screenshot with one search bar and two buttons below it

Constraints: Mechanics may print out a sheet and then not come back to the site until much later. Mechanics generally won't need to print out multiple sheets at once. Mechanics can't leave the repair page open as it is on one shared computer for multiple mechanics. All the bikes have a 3 digit number. Every search will return exactly one page (i.e., I can't search '23' and get '23, '231, 234'.)


I would avoid displaying those buttons until the search process resolves. Google's a bad example since the result doesn't require an action if it's not what you wanted.

The two buttons you propose don't account for sad path cases like:

  1. That ID number doesn't exist
  2. The entered ID number esists but wasn't the intended record (eg I transposed numbers or fat fingered something)
  3. The entered ID exists but isn't valid (eg its been completed and archived)

If you put the buttons on the screen before the search returns results, you're creating a process where you need to validate the action again anyway.

I suggest an autocomplete or type ahead style search that displays records in an ever shrinking list. Then add the "action" buttons to each returned record. Its not really additional effort for the user and it solves a lot of UX issues that you'd need to catch otherwise.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.