Improving parent engagement and platform adoption for an independent school
An independent secondary school in the south of England had spent £80,000 on a parent engagement platform. It covered homework tracking, school communications, fee payments, academic reports, and absence notifications. Eighteen months after launch, active monthly users represented 23% of the parent body.
The school's IT director believed the problem was parents not being sufficiently comfortable with technology. A user experience (UX) audit found something different. The platform required three separate login credentials across two distinct interfaces. It sent an average of 11 push notifications per week. And it placed fee account information and pastoral welfare notes side by side on the same screen.
Parents had not failed to engage. The product had failed them.
- 77% of the parent body had not logged in during the previous month, despite the school sending three reminder emails
- Three separate login credentials were required to access the platform's full functionality across its two interfaces
- Parents received an average of 11 push notifications per week, many duplicated across email and the in-app message centre
- Fee account statements and pastoral welfare notes appeared in the same section of the same screen, with no visual or structural separation
- The platform had no mobile-optimised view; 68% of parent login attempts came from mobile devices
- First-time login required parents to complete a 14-step verification process before accessing any content
The school had procured a widely-used platform without conducting structured research into how its parent community actually used digital tools in daily life. The assumption was that because the platform was feature-complete, adoption would follow. It did not.
When the team was brought in, the brief was framed as a communications problem. Parents were not reading school updates. They were missing fee deadlines. Absence alerts were being ignored. The school wanted to know whether it needed a stronger enforcement policy or a new email strategy.
But the data told a different story. Parents who did log in did so infrequently and for a narrow set of tasks, typically checking a specific report or paying a term's fees. They were not disengaged from school life. They were responding rationally to a product that made even simple tasks unnecessarily effortful.
- Digital product audit: end-to-end review of the platform's onboarding flow, navigation architecture, information hierarchy, and notification logic
- Heuristic evaluation: assessment of the platform against established usability principles, identifying 31 distinct friction points across the two interfaces
- On-site observation: accompanied parents through first-time and return login sessions in a controlled environment, capturing where and why they stopped
- Parent journey mapping: constructed journey maps for four distinct parent personas, covering a range of digital confidence levels, household structures, and school engagement patterns
- Contextual interviews: 22 depth interviews with parents across year groups, exploring attitudes to school communication, notification fatigue, and privacy concerns around financial and pastoral data
- Co-design workshops: two half-day sessions with mixed groups of parents, school administrative staff, and the IT director, generating and pressure-testing design concepts for a simplified experience
- Wireframing: low-fidelity prototype of a proposed unified interface, tested with 14 parents across two rounds of structured feedback
The audit began with the first screen a new parent would ever see: the registration email. From there, the team mapped every step required before a parent could read a single piece of school content. The process involved 14 distinct interactions, two separate email confirmations, and required parents to set up credentials for a secondary portal before the primary one would unlock. Several parents in the observation sessions gave up before reaching the home screen.
The heuristic evaluation identified issues across consistency, error recovery, cognitive load, and trust. Financial information and sensitive pastoral notes shared a single view with no clear demarcation, which several parents described as unsettling. The notification volume had been configured by the school's administrative team with no understanding of how the platform's alert system worked. As a result, many parents were receiving the same message three times across different channels.
The journey mapping work was particularly revealing. The four parent personas ranged from a working single parent checking updates on a commute, to a parent of a child with additional learning needs who needed reliable access to detailed welfare information. None of the four personas were well-served by the current structure. For each, the platform added friction where it should have removed it.
The co-design workshops shifted the conversation. Rather than presenting findings and recommendations to the school leadership team, the team brought parents and school staff into the same room to work on solutions together. Administrative staff who had built the notification schedule were surprised to learn that parents experienced it as overwhelming. Parents were surprised to learn that some of the most useful data in the system was buried three levels deep.
The work produced a set of design recommendations and a tested wireframe prototype for a restructured parent experience. The recommendations did not require the school to replace its existing platform. They required the school to reconfigure it, working within the tools already available, and to address the structural decisions that had been made at the point of set-up.
The core change was consolidation. The two-interface model was collapsed into a single entry point with a unified login. The 14-step onboarding process was reduced to five steps, with verification deferred until a parent attempted to access fee or pastoral information rather than demanded upfront before they could see the school calendar. Notification frequency was restructured around weekly digests by default, with real-time alerts reserved for genuine urgency, such as same-day absence notifications.
Financial and pastoral information was separated into distinct sections with clear labelling and a visible explanation of who within the school could see each type of record. This addressed a concern raised in every interview with parents who had children receiving learning support or pastoral care. They had not realised their welfare notes were visible in the same view as their account balance. Several described feeling that boundary as blurred in a way they were not comfortable with.
The wireframe prototype was tested with 14 parents across two rounds. Task completion rates for the five most common actions improved from 41% to 89% in testing. Parents who had previously described the platform as confusing or off-putting completed the same tasks without assistance and without prompting.
- Active monthly users increased from 23% to 71% of the parent body within six months of the redesign going live
- First-time registration completion rate rose from 38% to 84% following the reduction in onboarding steps from 14 to 5
- Weekly notification volume reduced from an average of 11 to 3 per parent, with opt-out rates for notifications falling from 34% to 9%
- Fee payment on-time rates improved by 22 percentage points, attributed in part to clearer access to account information and a simplified payment flow
- Support requests to the school's administrative team relating to platform access dropped by 61% in the first full term after implementation
- Parent satisfaction with school communication, measured in the school's annual survey, rose from 52% to 79% approval
