Students need a clear path into activities.
Discovery, registration, team membership, schedules, and participation status need one coherent experience.
Selected work / Case 03
Education operations platform
School Activity Manager
A multi-tenant product ecosystem for coordinating school activities—from registration and attendance through scheduling, participation, oversight, and institutional records.
Product capability previewThe same activity lifecycle, shaped for administrators and students.
Portfolio-level oversight sits beside a focused activity hub, showing how registration, sessions, attendance, teams, equipment, and expenses remain connected across roles.
The operating challenge
School activities involve more operational work than a calendar can hold.
Activity programmes bring together students, teachers, administrators, schedules, venues, attendance, resources, and institutional oversight. When those pieces live in separate documents and messages, the activity record becomes difficult to trust and coordination depends on individual follow-up.
School Activity Manager is being designed as shared infrastructure for that lifecycle. It gives each role an appropriate working experience while keeping activity information connected across the institution.
Teachers need operational control.
Attendance and day-to-day management must remain practical during busy, real-world sessions.
Institutions need consistent oversight.
Roles, approvals, records, and activity outcomes must remain visible across the school.
Product ecosystem
Different roles. One activity lifecycle.
The product avoids treating students, activity leaders, and administrators as variations of the same user. Each experience is shaped around its responsibilities while sharing the same operational truth.
Activity discovery and registration
Gives students a structured view of available activities, participation requirements, registration status, and the information needed to take part.
Scheduling and sessions
Connects recurring activity schedules with individual sessions, venues, responsibilities, and the people expected to attend.
Offline-first attendance
Supports attendance work when connectivity is unreliable, preserving the fast interaction expected during a live school session.
Role and approval controls
Separates who can propose, manage, approve, and oversee work while preserving wider visibility of the activity programme.
Operational records
Brings participation, activity history, schedules, and supporting records into one institution-level operating model.
Multi-school foundations
Uses tenant-aware product and data architecture so each institution can operate independently on a shared platform.
Product and architecture
Resilient in the field. Structured at the institution level.
School environments require a product that is quick enough for daily use, strict enough for role-sensitive information, and resilient when a session happens beyond reliable connectivity.
Experience architecture
Mobile-first role experiences reduce friction for students and activity leaders, while shared product rules preserve consistent institutional behaviour.
Role-aware UXOffline workflowsApproval statesReusable design system
Technology foundation
A Flutter application layer, structured state management, local persistence, and a tenant-aware PostgreSQL backend support connected and offline operation.
FlutterDartRiverpodDriftSupabasePostgreSQL
A clearer programme for students, staff, and school leadership.
The platform direction replaces scattered coordination with a durable activity record—helping schools make participation easier, administration more consistent, and oversight more meaningful.
Plan your education productNext case study
Academy Operations Platform →