Phase 0 UI Foundation

One secure place to recognise every student journey.

ASCEND ONE helps schools track co-curricular participation, achievements, attendance, points, results, and accolades across the full student experience.

6+

Activity pillars

Mobile

Built for

SaaS

Future model

Today's summary

Achievement pulse

Sport

Participation recorded

+5

Culture

Participation recorded

+10

Service

Participation recorded

+15

Clubs

Participation recorded

+20

Branding foundation

Premium, calm, education-focused design.

This foundation gives the project a professional visual system before the database is connected. The structure is intentionally simple so Supabase Auth, roles, school data, points, and reporting can be added cleanly later.

Track participation

Capture student involvement in events, fixtures, practices, clubs, tours, service projects, and school activities.

Record achievements

Build a structured history of results, awards, colours, accolades, leadership roles, and external recognition.

Points-ready foundation

Prepare for a configurable points engine that can support houses, grades, teams, categories, and school-specific rules.

Privacy-first design

Keep student information protected with future role-based access control and school-level data separation.

Co-curricular coverage

Built for the whole student, not only the classroom.

ASCEND ONE should eventually give schools a complete view of student involvement across all recognised activity areas.

Sport

Ready for attendance, results, awards, and points.

Culture

Ready for attendance, results, awards, and points.

Service

Ready for attendance, results, awards, and points.

Clubs

Ready for attendance, results, awards, and points.

Leadership

Ready for attendance, results, awards, and points.

External achievements

Ready for attendance, results, awards, and points.

SaaS-ready from the start

Even though Phase 0 is for one school, the UI and future database should assume multiple schools later. This means future tables should include school_id where appropriate, and staff should only access student data for their own school.

POPIA-aware

Student data must not be public. Future phases should use secure authentication, role-based permissions, and careful reporting rules.

Next foundation step

Add dashboard shell and protected app layout.

School-first architecture