Design Backlog: Refine the Successful Submission page after user registered an operation

[zoeyli-46]

After the user registers an operation, they get a successful submission page. Currently, we direct the user to report any transfers and closures that they had, per the BA's request to put this language on this page.

Figma

Task:

• [ ] Refine the language to be more user-friendly
• [ ] Consider removing this language from the success page and moving it somewhere else in the flow
• [ ] Confirm the changes with the BA

[zoeyli-46]

Hey @patriciarussellCAS I made this ticket to deal with the successful submission page aftering registering an operation that has the language about closures/transfers. figma

[patriciarussellCAS]

Thanks @zoeyli-46 - if there is time I will flag this for BA during our registration walkthrough next week. If they want the closures/transfers language to stay here, then we'll leave it. My feeling (with no user testing to back this up though) is that industry users will want to flag a closure/transfer BEFORE they complete registration. I'm thinking that on the page where they "add a facility" it might be helpful to include language about where and how they let us know about a transfer, rather than getting through the whole process and THEN informing us about them. But we can leave it like this for now and see what comes out of user testing :)

[zoeyli-46]

Hey @patriciarussellCAS that screen was in the Registration user testing that we did in August :) both SFO and LFO did not mind that flag being at the end but lets discuss it with the BA at registration collab if we have time!

[patriciarussellCAS]

Ok great. I'm happy to ice box this for now if the BA and users like it.