Skip to content

rookieNick/Faceducation_SmartSchoolManagementSystem

Repository files navigation

Faceducation — Facial Recognition Attendance + Enterprise Campus System

Live Demo: https://faceducation-react.vercel.app

Note: The facial recognition service will be disabled on the demo due to cloud resource constraints.

About This Project

Faceducation is an enterprise-level education management system that combines:

  • Facial-recognition attendance (with anti-spoofing + averaged embeddings)
  • Auto scheduling timetable capabilities and conflict-aware operations
  • A full campus workflow system (barring, leave management, replacements, programme management, enrollment, reporting)

The system is designed around real operational workflows (recommend → approve → execute) and role-based actions.

Tech Stack

  • Frontend: React (Vite + TypeScript)
  • Backend API: Flask
  • Facial Recognition Service: FastAPI (separate service; may be disabled on demo)
  • Database: MySQL
  • Caching / Queue / Sessions: Redis

Modules

Authentication & Accounts

  • Login
  • Account Registration
  • Profile Management (CRUD + account updates)

Facial Recognition Attendance (Multiple)

  • Facial Recognition Attendance (login + attendance using averaged embedding)
  • Anti-spoofing measures to prevent fraudulent attendance
  • Late detection & restrictions
    • Configurable grace period
    • Late markings don’t count as attendance
    • Real-time notifications for late students
  • Classroom monitoring
    • Periodic presence verification
    • Alerts for early departures
  • Automated reporting
    • Presence / late / absent breakdowns
    • Notification-ready outputs (e.g., parent/guardian messaging)

Academic Operations

  • Timetable Management
    • Publish daily/weekly timetables
    • Room & instructor assignment
    • Prevent conflicting bookings
    • Student-friendly timetable views
  • Programme Management
    • Manage programme offerings, prerequisites, cohort limits
  • Programme Enrollment
    • Enrollment requests
    • Approval tracking and status visibility

Governance & Workflows

  • Barring System
    • Automatic barring based on low attendance thresholds
    • Configurable rules
    • Appeal process + supporting documents
  • Leave Management
    • Student leave applications
    • Teacher leave applications
    • Approval workflows (PL/Teacher/Admin)
    • Leave balance carry-forward logic
  • Class Replacement
    • Teacher substitution requests
    • Approval + schedule update flow

Reports & Analytics

  • Attendance and performance insights
  • Summary dashboards and workflow visibility

Roles & What They Can Do

Roles are designed to reflect real campus operations and approvals.

Student

  • Register/login and manage profile
  • View timetable and enrolled programmes
  • Submit leave applications (with supporting details)
  • View attendance status and outcomes (present/late/absent, barred status)
  • Submit appeals if barred (with documents)

Teacher

  • Take/verify attendance (including late rules + presence checks)
  • Monitor classroom attendance and early departure alerts
  • Review student leave requests (where applicable)
  • Create class replacement requests
  • Recommend barring actions (when attendance thresholds are violated)

Programme Leader (PL)

  • Approve / reject teacher leave (first-level approval)
  • Review academic workflow items that require programme-level decision
  • Provide recommendations before admin final approval

Admin

  • Full system administration (accounts, configurations, master data)
  • Final approver for critical workflows
    • Approve teacher leave (admin-only final approval)
    • Approve barring recommendations
  • Manage timetable operations and system-wide rules
  • Oversee reporting and analytics

Workflow Highlights

Barring Workflow (Teacher/PL Recommendation → Admin Approval)

  1. Attendance is captured through facial recognition and/or verification checks.
  2. System computes attendance rate using configured thresholds.
  3. When the threshold is violated, Teacher/PL can recommend barring.
  4. Admin reviews recommendation + evidence/records.
  5. Admin approves/rejects the barring decision.
  6. If barred, Student may submit an appeal with supporting documents.

Leave Management Workflow (Carry-Forward + Approval Rules)

  • Leave balance carry forward is applied based on year-end rules.
  • Student leave: Student applies → Teacher/Admin reviews (based on rules) → Approved/Rejected.
  • Teacher leave: Teacher applies → PL approves (first stage)Admin approves (final stage; admin-only).

Class Replacement Workflow

  1. Teacher submits a replacement request (reason + target class).
  2. Approval is performed based on role rules.
  3. If approved, timetable/class assignment updates accordingly.

Preview Gallery

Account Registration Module

Account Registration - 1 Account Registration - 2 Account Registration - 3 Account Registration - 4 Account Registration - 5

Login

Login - 1 Login - 2

Profile

Profile

Facial Recognition Attendance Module

Attendance - 1 Attendance - 2 Attendance - 3

Barring Module

Barring

Leave Management

Leave - 1 Leave - 2

Class Replacement

Class Replacement - 1 Class Replacement - 2 Class Replacement - 3

Programme Management Module

Programme Management - 1 Programme Management - 2 Programme Management - 3 Programme Management - 4 Programme Management - 5 Programme Management - 6

Programme Enrollment

Programme Enrollment - 1 Programme Enrollment - 2 Programme Enrollment - 3 Programme Enrollment - 4 Programme Enrollment - 5 Programme Enrollment - 6 Programme Enrollment - 7

Timetable Management Module

Timetable - 1 Timetable - 2 Timetable - 3

Releases

No releases published

Packages

No packages published