Save

[jennifer-hodgson]

Save

Potential use cases

• Continue
• Save and continue
• Save and come back later
• Confirm
• Accept and send

Overview

The save function is used in several different ways across HMRC services. Save and return currently exists in the GDS design system (draft documentation here. However, save is used in a number of others ways within HMRC services, eg save and continue and save and exit, that are not currently documented.

Further work is needed to make the way we use "Save" more consistent. For example, why use "Save and continue" as a variant of "Continue" when the assumption must be that a user's information is saved as they move through a journey. Also: different save functions. How do we communicate to users that they can come back later to complete a journey, for example.

[The need for this pattern arose as a result of the HMRC design system hackday]

[jennifer-hodgson]

Should this be a more high-level issue surrounding the buttons we use to guide users through journeys?

[jennifer-hodgson]

There are discrepancies in our use of Continue versus Save and continue. Both are being used to mean the same thing, that the user's data has been saved and they are moving on to the next part of their journey. Based on a quick scan of prototypes, the following services use a Continue button (at least as far as I can tell from their prototypes):

• Lifetime ISA
• Apply for a tax refund
• Marriage allowance
• Soft Drinks Industry Levy
• Online payments
• Self Assessment
• Registration of a trust
• Repayments

Whereas, the following services use the wording "Save and continue":

• Anti-money laundering
• Register your company
• Manage and register your pension

The guidance in the GOV.UK Design System currently displays a "Save and continue" example, under the entry for Button.

Save an exit is also being used in the following services (again, not exhaustive, on the basis of a quick scan of prototypes and code search):

• Business rates check
• Climate change agreement

Save and return, or save your progress, that is, save your details and come back later is being worked on as part of the GOV.UK design system.

[vickytnz]

I think it's important to understand what is meant by 'save' - I take this to mean persisting data - that if a user signs out and signs back in, the data will still be there. Services that don't allow for persisting data will just use continue (for example, if a service is so short that there's not a clear user need to allow for persisting data).

Services that don't allow for persistent data, will just use continue, as per for example the question example for check if you're eligible https://check-before-you-start-pattern.cloudapps.digital/pages/questions/over-18

[jennifer-hodgson]

Thanks for this, Vicky. Yes, this is what we are trying to understand: to what extent "save" and "save and continue" are being used interchangeably, when they actually mean quite different things - and this could be quite misleading.

[jennifer-hodgson]

Add to GOV.UK guidance on Button.

[jackiebrownlee]

CDS have two services that have long and complex journeys, and will need a Save and Return solution. Having done some digging around the various services who have implemented S&R already, I think this warrants reopening this discussion.

[jennifer-hodgson]

Agreed. Have re-opened. Discussions also happened previously on duplicate issue #61

[MarkKeeling]

I began looking into possible solutions for MTD Sign Up today and found the following:

The GDS Design System button component describes the use case for secondary CTA's: https://design-system.service.gov.uk/components/button/#secondary-buttons

It also describes the terminology to use for saving pages: https://design-system.service.gov.uk/components/button/#how-it-works

To me, the pattern exists in GOV.UK already. Do we have any research on this method not working?

He's what I was intending to test with:

[terrysimpson99]

Pairing 'Save and continue' with 'Save and come back later' can fail to be discriminated by screen readers in some circumstances. Screenreader users don't always wait for labels to be read in full before moving on. Both labels in this case start with 'Save and ' and may appear to be the same button if curtailed in this way. Somebody else may be able to comment further.