← ALL PROJECTS
CampusFlow
A scheduling platform that reduces student-support handoffs with clear operational workflows — one queue, one owner, no lost requests.
Overview
Support requests that stop falling through cracks.
CampusFlow began when a student helpdesk admitted that requests were living across three inboxes and a whiteboard. I designed a single shared queue where every request has an owner, a deadline, and a visible history — for students booking help and staff resolving it.
The app is React with TypeScript over Supabase: realtime queue updates, role-based views for students, volunteers, and coordinators, and gentle reminders before a booking goes stale.
Approach
Designed with the desk, not for it.
- 1Shadowed the helpdesk. Sat through two full support shifts to see where requests actually got stuck — the whiteboard, not the inbox, was the bottleneck.
- 2One queue, three views. Students see simple booking; volunteers see their own workload; coordinators see the whole board — all reading from the same live data.
- 3Typed everything. TypeScript end to end, from Supabase row types to form states, so pilot bugs showed up in the editor instead of in front of students.
- 4Handed it over properly. Wrote a short staff handbook and trained two coordinators, so the pilot could run a full term without me.
Gallery
From desk to deployment.
Related work