A school portal for the parent who is late to pickup

The context

School district portals are a quiet bad-design story. Every parent of school-age children in North America has used one. Almost nobody likes them. They are built to satisfy an administrator’s mental model, rows of menus that mirror the school’s internal org chart, and used by parents who have different priorities, less time, and, often, less fluency in the language the portal was written in.

Arcadia’s incumbent portal had been built in 2018 as a wrapper around the district’s student information system. The SIS vendor’s defaults shaped every screen. Five years of accumulated feature requests from the district office had added forty-one items to the top-level menu. The portal had the information parents needed, nominally, but they could not find it. Monthly abandonment, a parent opening the portal and leaving without completing any task, was 62%.

The district superintendent’s office engaged us after a community meeting in which a parent had stood up and, through tears, said she could not figure out how to sign her child’s field-trip form. It had been the fourth time she had tried. The meeting made the local news. The superintendent called our practice the next morning.

How we framed it

This was not a UI project. The parents were not failing because the buttons were ugly. They were failing because the portal was organized around the school’s operational structure, not around the things parents do. Renaming menus would not fix it. The portal needed a new organising principle.

We framed it as “six tasks the portal must make instant, everything else in support”. The six tasks came out of the first two weeks of parking-lot research, not out of a workshop. Workshops produce comprehensive task lists that reflect every participant’s priorities. Real parents, caught in the three minutes before they had to pick up a child, had stark preferences.

The home screen as a weekly summary

The new home shows six cards, one per priority task, each with current status. The cards collapse into a vertical stack on mobile and sit as a 2×3 grid on desktop. Every card is actionable, tapping the lunch balance card opens the direct-deposit flow, tapping the permission slip card opens the slip requiring signature, and so on.

Cards whose status is “nothing to do” say so explicitly, “No absences to report this week” rather than disappearing. The presence of “nothing to do” matters to parents; it is what reassures them that they have not missed something.

Translation, seriously

The old portal had UI in six languages and content in one. We built the new portal with content translation as a first-class obligation. The district’s family engagement office commissioned human translation of every school-originated message, every permission slip, every attendance notice, every lunch menu, in eleven languages. The translation coordinator role was funded as a permanent staff position by the district office, not as a contract line.

This decision was the hardest to get funded and, in hindsight, the one that moved the parent satisfaction numbers most. Families who spoke Spanish, Vietnamese, or Somali at home had been living with degraded service for years. Fixing that mattered more than any feature we designed.

What did not work

An early design had a notifications feed, a stream of everything the school had ever sent the parent. Parents hated it. The volume made it useless. We replaced it with per-task status on the home screen and a quieter notifications icon in the top bar. The feed was not the answer; the right information in the right place was.

An early design also had a “school news” section on the home. Parents ignored it. School news is the administrator’s priority, not the parent’s. We moved it to a secondary tab and removed it from the home entirely. Engagement on school news dropped, which the communications office worried about, but engagement on the priority tasks, the things parents actually needed, tripled. We kept it moved.

Outcomes

Priority-task completion rates tripled across all six tasks. Support tickets per active parent dropped 44% within six months. The portal is now available at full content parity in eleven languages, up from one. The district office has committed permanent funding for the translation coordinator role.

The parent who had stood up in the community meeting came to the launch event. She signed a permission slip on her phone in thirty seconds. She did not cry this time.

Reflection

Govtech and schooltech have an orientation problem. The systems are built to serve the people inside the institution, not the people the institution serves. Fixing that orientation is almost always the project, and it is almost never what the original brief asked for. Re-framing the brief is usually the highest-leverage thing a designer can do on these projects.