Newtonschool
Make campus preference a clear, persistent, and editable part of the student journey, while reducing manual operations by 46%.
Despite asking students for their campus preferences, the flow lacked visibility and priority — leading to:
Students unaware of their chosen or assigned campus
Trust issues due to mismatch between expectation vs. final allocation
High volume of support tickets for preference updates
Backend teams manually overriding entries due to compliance gaps
Manual ticket count dropped by 46%
Backend ops load reduced
Built Trust between students and parents
Campus preferences were taken from students midway in a long NSAT flow, often ignored or misunderstood
Students were unaware of what they selected or whether they could change it
Lack of transparency led to mistrust and confusion at the time of campus allocation
Support & backend teams had to manually handle high ticket volume for simple preference changes
Compliance risks arose due to lack of documented student consent for final allocations
Ownership of redesigning how students choose and interact with campus preferences
Goal: Make preference selection visible, editable, and trustworthy across their journey
Worked closely with PM + ops to understand tech, compliance & business constraints
Designed edge-case flows for pre/post-payment, no-shows, and lock-in logic
Project shipped across all live cohorts applying to Newton School of Technology within 2 weeks (₹25L BTech program)
Introduced a persistent, always-visible preference widget during key stages (dashboard, interviews, prep)
Students could edit their choice until a defined lock-in date, post which preference is frozen
Communicated preference status clearly (editable, locked, submitted)
Design system components reused for rapid implementation
Created fallback/error states for edge cases (e.g. missing data, expired lock date)
