Review requirements and UR findings for confirmation page when registering an ECT or mentor and iterate content

[JSJohal]

Why? What's the need?

We've prototyped an add ECT journey as part of #124. However, we've used the confirmation page from the existing ECF1 service for UR, as we're not sure about the specific requirements the existing service is not meeting.

In user research, some problems were found with this confirmation page:

• users found content around appointing an AB confusing, and see it as more of a statement of what they have not done rather than a reminder
• users wanted more specifics on what they have to do next and how it fits into the wider registration ecosystem "If there's another step I need to actively go and do now, make that really explicit"
• Users wanted to be able to add another ECT
• Users wanted more reassurance that they were done

Success criteria / when is this ticket done?

• Review which requirements aren't being met on confirmation page when adding an ECT
• Review which requirements aren't being met on confirmation page when adding a mentor
• Review problems from UR
• Consider how this content needs to be different depending on whether programme type is provider led or school led
• Also consider how this content differs when mentor is yet to be assigned and when the mentor is already assigned
• Potentially look at if they're QTS awarded yet

What's out of scope

Helpful links or other information

[mason-emily]

ECTs: https://lucid.app/lucidspark/b6f362cf-8201-4799-aac2-9efb0f18b2a9/edit?view_items=SbmazPBp09QE&invitationId=inv_cf2261a1-b288-46f7-bb47-51121c5d0ec6

[claire-hughez]

@mason-emily to check eligibility and if that impacts the confirmation page