Design Refresh Alpha: Rename “Submit” Button to “Save” | Voters

Design Refresh Alpha: Rename “Submit” Button to “Save”

now

Claudine Richardson

The current “Submit” button should be renamed to “Save” to better reflect its actual function, which is to save progress on a packet rather than formally submit or finalize it. Renaming the button will reduce confusion and make the action more intuitive for users.

18 hours ago

Claudine Richardson

Merged in a post:

Rename "Submit" Button to "Save"

Saumya Dubey

The "Submit" button should be renamed to "Save" to accurately reflect its function of saving progress on any packet.

18 hours ago

Claudine Richardson

marked this post as

now

Suraj Udupi

We do have similar requirement. ‘Save’ button for updating cards and categories (instead of the ‘Submit’ button in the status section). 
Auto save the cards/form (i.e. categories etc), or add a save button at the top (next to refresh).
This would create efficiencies for the allocator, so they wouldn't need to click 'submit' to save and then have to recategorize as 'To-do' before they allocate to someone.

Claudine Richardson

Hiya Saumya Dubey, thanks for this post! I have a few more questions for you:

Can you clarify if the 'Submit' button's functionality will remain the same, and only the label needs to be changed?
Are there any other areas in the application where you feel the 'Submit' button should be renamed to 'Save'?
Could you provide some examples of situations where the current 'Submit' button label has caused confusion or errors?

Harsh Seksaria

Hi Claudine Richardson,

Yes, the functionality remains same, only re-labelling would help. We can also do "Save and Submit".
Not yet.