As an LA I want to be clear what details I am confirming are up-to-date

[markhobson]

When reviewing a scheme the user confirms "that the details in this scheme have been reviewed and are all up-to-date". Some details of a scheme, like outputs, are read-only and as such cannot be updated. This may cause confusion since the user cannot update these details, nor truthfully confirm that they up-to-date.

We should make it clear that they are only confirming details that they can change are up-to-date. Some ideas:

• Hide outputs
• Move outputs below the review question and clarify that the user is confirming that the above details are up-to-date
• Add copy to outputs to clarify that this is read-only information and is exempt from review

[KPresleyATE]

Would suggest moving review question up (second bullet).

[markhobson]

We could clarify how up-to-date we expect a scheme's details to be if it's undergoing change control.

[markhobson]

Authority feedback:

• ...We are unable to update the information in the outputs section.
• Our scheme scope was revised and there was not an option to update scheme details
• A request for the platform to be more responsive to change. Ideally we, as administrators, would have the ability to amend and update all details on projects that are live, e.g. names of schemes. I feel this would help prevent confusion and improve our ability to provide accurate updates/Pulse surveys.

[markhobson]

Prototyped a number of options to clarify what details are being confirmed as up-to-date:

1. Move outputs card below confirmation
2. Explain why some details can't be updated
3. Explain why some cards can't be updated

[markhobson]

Went for (2), as it's the most concise and explains how to change details outside of the service at confirmation time: