EDUTRACK PREVIEW · Fictional demonstration records only · Do not enter real student information

Attendance overview

Course attendance at a glance.

● Demo Administrator
Prototype mode: This build runs with fictional sample data saved in this browser. It demonstrates the course, attendance and PDF workflows. Firebase Authentication, shared Firestore persistence and production security rules must be connected before real student records are entered.

Department overview

Academic attendance summary for the selected session and semester.

Courses in department
0Active course records
Registered students
0Unique students across courses
Classes held
0Closed attendance sessions
Average attendance
0%Across registered course places

Course attendance snapshot

Selected academic term
CourseRegisteredClassesAverage attendance

Attendance attention list

Below 75% threshold
StudentCourseAttendance

Quick actions

Common tasks

Course directory

Manage the courses offered by the department.

Department courses

0 courses
Course codeCourse titleDepartmentLecturerRosterRep code accessAction

Student directory

Student identity is stored once; Regular or Carryover status belongs to each course registration.

Course roster

S/NMatric numberFull nameCourse statusAttendanceEligibility
No students are registered for this course and term.
CSV columns: Full Name, Matric Number, Status. Status must be Regular or Carryover. The import is attached to the selected course and academic term.

Attendance register

Open a class session, mark the register and close it when complete.

Register controls

Select a course and session.
Live student check-in code
------
Code expires soon
Share only with students in the classroom. The code is time-bound.

Registered students

S/NMatric numberStudent nameRegistrationCurrent statusMark status
No course registrations found.

Student check-in portal

Enter the current session code to record attendance for a registered course.

In this prototype, choose a fictional student to simulate the student login. Production mode will identify the student through their authenticated account and prevent them from selecting another student's identity.

Mark my attendance

OTP / QR session

My course attendance

Selected student

Choose a student to view their course attendance.

Offline submissions

0 pending

If the browser goes offline during a check-in, the submission is held locally. It is only accepted when the session and code remain valid on reconnection; expired submissions are flagged for lecturer review.

No queued check-ins.

PDF & attendance reports

Collate attendance into clean, printable tables for departmental submission.

Report settings

A4 landscape · tables repeat headings across pages · page numbers included

Course attendance summary

S/NMatric numberStudent nameRegistrationHeldPresentAbsentLateExcusedAttendanceEligibility
No report rows are available for this course and term.
Attendance calculation: (Present + Late) ÷ (Closed sessions − Excused sessions) × 100. Excused sessions are excluded from the denominator by default. The 75% threshold is configurable in Settings.

Attendance audit history

Review who changed an attendance record, what changed and when.

Recent changes

0 entries
Date and timeActorActionStudentCourseChange
No changes recorded yet.

Workspace settings

Institution details and attendance policy.

Institution profile

Used on exported reports

Role permissions in this preview

Illustrative only
RoleCourse accessAttendanceRosterReports
AdministratorAll department coursesView / manageManage / importDepartment + course
LecturerAllocated coursesOpen / mark / close / correctViewOwn courses
Course RepresentativeAssigned coursesOnly when authorisedManage / importAssigned courses
StudentRegistered coursesOwn check-in onlyOwn profileOwn statement
Production requirements: connect Firebase Authentication and Firestore, deploy the supplied security rules, create user profiles with assigned roles, and verify the geofence on a trusted backend before using this with real student data. Browser GPS and device fingerprints are deterrents, not proof of identity or physical presence.