Niagara College team project
Movement Unlimited
A scheduling and records application built by a five-person team for a client. It organizes sessions and client details that had been tracked in spreadsheets.
The problem
The client needed a consistent way to manage records that had been tracked in spreadsheets. The team designed an application with structured data and clear validation.
My role on the team
On a five-person team, I contributed to backend endpoints, relational models, and input validation. I also worked on session flow, calendar readability, and role-specific Help content.
How it works
Sessions connect a date and time to a teacher, a session type, and the people attending. We put validation alongside those relationships so the calendar and session screens use the same records. I helped refine the session forms and the way scheduled sessions appear on the calendar.
What it does
- Relational records for sessions and scheduling
- Backend endpoints with input checks
- Role-based access and a calendar view
Result and lessons
The team built a structured workflow for sessions and scheduling. I learned to align field validation and database relationships with the client’s process.