Route without over-asking
Separate fields PSR needs now from fields a student can provide after they choose a path.
Progressive forms, fewer dead ends
Ask once. Route clearly. Explain login.
This is a prototype form shell, not a submission form. It shows how PSR can reduce friction before the real Kwaray HubSpot form, application system, and authentication handoff are wired.
Form UX rules
Preserve momentum
Use save-and-return, recovery links, plain eligibility language, and clear human contact paths.
Show commitment
Surface format, duration, price field, sequence, and pathway fit before asking for account creation.
Explain activation
Tell the student what account they are creating, why it matters, and how to recover access.
Critical KPI
First login within 24 hours.
Activation belongs in the front-end plan. Confirmation copy, email handoff, recovery states, and first-login prompts all need to be designed and measured as part of the enrollment journey.