Three bespoke academic dashboards for university programme coordinators.
Project Overview
During my time at GIFT University, I built a Coordinator management system featuring three distinct dashboards tailored to different academic stakeholders: Master's programme coordinators, BS programme coordinators, and university administrators. This was one of my earliest full-stack projects, where I practised end-to-end software delivery — from requirements gathering to implementation.
The Problem
GIFT University coordinators managed student registration, timetabling, and academic progress through fragmented spreadsheets and manual processes. There was no unified system providing role-appropriate views and actions for different coordinator types, leading to errors, duplication, and poor visibility.
Three Dashboards, Three Roles
Master's Coordinator
Graduate programme management, student progress tracking, thesis coordination, and academic scheduling for postgraduate cohorts.
BS Coordinator
Undergraduate registration management, semester planning, attendance oversight, and inter-department coordination for BS programmes.
University Admin
University-wide view covering all programmes, coordinator performance, aggregate reporting, and system configuration.
My Responsibilities
Requirements Gathering
Conducted in-depth interviews and workshops with Master's and BS programme coordinators to understand their workflows, pain points, and data needs.
Stakeholder Design
Designed three distinct dashboards tailored to different coordinator roles, ensuring each view surfaced only role-relevant data and actions.
Full Development
Built the complete application from requirements to deployment, implementing authentication, role-based access control, and all coordinator workflows.
University Integration
Integrated with existing university data sources to surface student records, course schedules, and registration data within the coordinator dashboards.
Key Challenges & Solutions
Role-Specific UX Design
Each coordinator role had fundamentally different data needs and workflows. I designed a shared component foundation with role-based rendering, avoiding three completely separate codebases while still providing each user the focused view they needed.
Translating Non-Technical Requirements
Academic coordinators had no technical background, so bridging the gap between their workflow descriptions and formal software requirements was a core challenge — solved through iterative prototyping and regular feedback sessions.
Data Integrity for Academic Records
Student and programme data required strict validation and audit trails. I implemented database-level constraints, form-level validations, and activity logging to ensure data accuracy and accountability.
Let's Work Together
I'm currently available for freelance projects and open to new opportunities. If you have an idea or just want to say hi, send me a message!