Enabling guardians to join Plurall and follow students’ progress

Registration had to respect school policies and existing technical limits while securely connecting guardians to students. We introduced self-service registration and bulk invitations.

Role
Product designer
Timeline
2 weeks · 2024
Scope
Guardian registration and onboarding
Teams involved
Engineers, business leaders, data, marketing, and customer success

At a glance

Plurall wanted to expand guardian participation and create new opportunities for families, but joining depended largely on students registering guardians or school staff adding them one by one. I worked with the Onboarding and Management team to understand both routes, adapt an existing student code into a secure self-service journey, and make school invitations easier to manage. We tested the experience with more than 200 participants. After launch, guardian registrations grew 96% compared with the same period a year earlier.

Listen to the project story
YoY
96%
New guardians
180K+
Over the previous 3 months
33%

Guardians mattered to schools and the business

Guardians are central to the school journey. They follow students' progress, support learning at home, and help schools maintain stronger relationships with families.

For SOMOS Educação, which developed Plurall and also owned the educational materials used by schools, reaching more guardians was a strategic move to support student retention at schools using those materials. The company aimed to grow Plurall's guardian base by 15% and increase guardians' share of platform traffic by 4%. New materials and features for guardians would also create more opportunities for B2C revenue.

Research exposed two enrollment barriers

I started by reviewing earlier attempts to connect guardians: a banner and an account-linking alert. I documented both approaches for the team, then we compared page views with clicks. The banner converted at 2% and the alert at 4%, both below the expected 8%. These rates measured clicks on the prompts, rather than completed registrations.

We also reviewed feedback collected on those pages. Students asked for the notifications to stop and said they did not want to provide a guardian's details. The comments showed resistance to the repeated requests, alongside the low conversion rates.

Past user interviews and a review of the existing journey also showed that students could register guardians, but many skipped the step, assumed their guardians would not be interested, or avoided sharing access to their grades. Guardians could also ask a teacher or school director for access.

Neither route was easy to scale. Guardians depended on a student taking action or on school staff adding them individually. The barrier was not just the registration form; it was how access began.

Mapping registration data and platform-generated information clarified what each onboarding route already knew about students and guardians.

The problem extended into school onboarding

Student behavior was only part of the problem. Through interviews and workshops with school directors and internal stakeholders, we learned that many schools did not consistently introduce guardians to Plurall during onboarding. Some guardians did not even know the platform existed.

We also revisited how teachers and directors brought guardians into the product. When a guardian asked the school for access, staff had to add them one by one. We needed to address both the awareness gap and the effort required to invite families at scale.

The journey had to be simple and secure

A self-service route needed to work for guardians with different levels of technical confidence. Students had to be able to find the connection information in their own accounts, while guardians needed a secure way to connect to the correct student from a different account or device.

We also needed to make school-assisted invitations simpler without conflicting with school policies or the platform's technical limits. Guardians should not have to rely on one route alone.

I also flagged a case we could not yet see clearly: what would happen if a guardian tried to connect to a student who was not registered in Plurall.

Annotated flowchart of the existing guardian registration landing page and lesson-booking journey, with account-status branches and open questions
An annotated map of the existing registration and lesson-booking journey exposed account-status gaps and questions about connecting family members.

Comparing options opened up a simpler path

Research shifted the question from how to improve student invitations to how guardians could join on their own and how schools could invite them at scale. We ran workshops with stakeholders and the cross-functional team so each group could share its knowledge of families, schools, the business, and the platform.

We studied how other products let guardians register and connect to another account. I documented the journeys in a comparison board, noting shared patterns, opportunities to improve, and what each product did differently.

I mapped three possible routes: self-service registration with a QR code, registration with a student code, and a personalized link. I took the flows to the PM and squad to gather feedback and assess the effort. We compared ideal scenarios with what we could deliver within the time available, technical limits, and business goals.

During these discussions, the technical team suggested reusing something already in the ecosystem to connect guardians with students, avoiding a much larger build.

Benchmarking compared guardian registration and account-linking journeys in ClassDojo, MyTutor, and Sophia.
Paper wireframes of desktop and mobile registration screens, with form fields, step indicators, and purple annotations
Early paper wireframes explored registration layouts, form fields, and step indicators across desktop and mobile.

An existing code enabled independent registration

Following the technical team's idea, we found that every student already had a unique identification code in their account. It was underused, but could securely connect a guardian and student without requiring the student to register the guardian.

We worked with Engineering and stakeholders to adapt the code for registration, making it shorter, easier for students to find and share, and simpler for guardians to enter. Guardians could then create their own accounts and connect with students without waiting for an invitation.

The solution used an existing part of the ecosystem rather than introducing an entirely new verification system. That reduced technical complexity while removing the journey's primary dependency.

The proposed flows explored account linking in both directions, notifications, and what guardians could do after connecting to a student.
On tablet, guardians could choose their registration route, enter the student code, confirm the student, and see when the accounts were connected.

Testing refined the journey

We tested the journey remotely with more than 200 participants through Maze. The study helped us identify where guardians hesitated, misunderstood instructions, or struggled to enter and validate the student code.

We also checked the handoff between accounts and devices: whether students could find the code, guardians could use it from their own account, and the connection reached the right student. We used what we learned to simplify the language and clarify steps on both sides of the journey.

Portuguese research planning template with sections for objectives, evaluation metrics, target audience, and methodology
Research planning template covering objectives, success measures, participant profiles, and methods. The examples illustrate the template rather than this project's findings.

Two simpler ways for guardians to join

Guardians could create their own accounts and use the adapted student code to connect with the right student. Clear instructions helped them complete the flow without relying on someone else to register them.

Teachers and directors could upload a list of guardians and send invitations in bulk instead of adding them one by one. Families now had two routes: join independently or receive an invitation from their school.

The desktop journey gave guardians a dedicated entry point, guidance for finding the student code, and confirmation before linking the accounts.
The mobile approval screens let students provide a guardian's contact details and see confirmation that the request had been sent.
From their profile, students could see linked guardians, distinguish pending approval from an active connection, and resend an invitation email.

Communication brought the new journey to families

I took part in initiatives with schools to explain why guardian participation mattered and how staff could share the new routes with families. I kept Marketing involved throughout the process so launch communication could explain the new registration and account-linking journey. Social media outreach then expanded to encourage guardians to create accounts and connect with students.

Plurall's Instagram announcement: independent guardian registration is now available, illustrated with an account registration screen.
Instagram announcement introducing independent guardian registration.
Saved Plurall YouTube thumbnail showing a family beside the school calendar on a phone. The original video is unavailable.
YouTube thumbnail from the family launch communication. The original video is no longer available.

The new journey expanded guardian participation

Guardian registrations increased 96% compared with the same period the previous year. More than 180,000 guardians registered during the off-peak season.

Over its first three months, the new journey recorded 33% more guardian registrations than the previous version. These registration gains supported Plurall's goal of expanding the guardian base and created a stronger foundation for family engagement.

The growth opened a separate project focused on what happened after guardians joined: how to improve retention and engagement, and how to offer relevant materials and features to the new families coming into Plurall.

YoY
96%
New guardians
180K+
Over the previous 3 months
33%

The whole entry journey had to work together

Improving the registration form alone would not have solved the problem. Students could miss or avoid invitations, school staff had to add guardians individually, and some families did not know Plurall existed.

The student code gave guardians an independent route, while bulk invitations and school outreach made the assisted route easier to use and discover. Connecting these parts of the journey gave more families a practical way into Plurall.