2025 · INTERNAL TOOLS | DASHBOARD
Student Behavior & Discipline Platform
A system for the Dean of Students to log incidents, track patterns, and stay notified — built in 8 phases as requirements became clearer.
Built at Immaculata-La Salle High School
Tech Stack
Overview
Staff were managing incident reports through email and spreadsheets. I built a submission form for staff and a dashboard for the Dean of Students to review, filter, and manage cases — shipped in 8 phases as requirements evolved through stakeholder feedback — which is how internal tools actually get built. All data stays within the school's Microsoft 365 environment, which matters when you're dealing with student records. Role-based views mean staff only see the cases they filed.
What I Built
- Staff incident submission form with category, severity, and follow-up fields
- Dean of Students dashboard — filterable by date, student, category, and status
- Power Automate email notifications on submission and status change
- Role-based access — staff vs. administrator data visibility
- SharePoint as the data layer — no external database required
- 8-phase development lifecycle from requirements to production deployment
What I Learned
Translating institutional paper workflows into digital systems with multiple stakeholder types
Building role-based access with MSAL without a dedicated backend
Managing multi-phase projects solo — scoping, building, testing, and deploying incrementally
Handling sensitive student data within Microsoft 365 compliance boundaries