Skip to main content
OpenEduCat logo
solutionPage.moduleBadge

Open-Source Attendance for 4-Year Universities

Run attendance across every campus, lecture hall, and lab from one database. TAs and proctors mark sections they own; the registrar pulls Title IV last-date-of-attendance on demand.

Open-source attendance management for universities is a self-hostable system that handles 200-seat lectures, multi-campus scheduling, and delegated teaching-assistant marking inside one institution-controlled database, then produces the last-date-of-attendance values the financial-aid office needs for Title IV federal aid certification under 34 CFR §668.22 without a separate vendor.

2,679Title IV-participating 4-year degree-granting institutions reported by NCES IPEDS 2023-2415.4MFall 2024 4-year US university enrollment per NCES, the population OpenEduCat scales to via branch isolation30 daysFederal R2T4 deadline after withdrawal-determination date; built-in LDA export keeps the registrar inside it (per 34 CFR §668.22)

solutionPage.featuresTitle

solutionPage.featuresSubtitle

Multi-campus, one database

Branches in OpenEduCat map to campuses, satellite sites, and extension centers. Sections, rooms, and instructors stay isolated by branch security, while the provost's office runs cross-campus enrollment and attendance reports from the same Postgres instance. No cross-campus data sync job, no per-campus vendor contract, and one upgrade path for the whole system.

200-seat lecture hall flow

RFID gates at the door and QR check-in from a student's phone process a full lecture in under three minutes. The instructor sees a live seated and missing count on the course form before starting. Late reads close after the configured grace window so a student who arrives 30 minutes in is marked late, not absent, with the rule logged.

TA and proctor delegation

Faculty assign teaching assistants and proctors to a section with mark-only, mark-and-edit, or read-only scopes. Every edit is signed with the TA's user ID so the instructor of record always sees who changed a row. Permissions track the academic term so a TA loses access the moment the section ends, with no manual cleanup.

Title IV LDA reporting

The attendance module stores per-section last-date-of-attendance and never-attended flags. The financial-aid office exports the values for Return of Title IV Funds calculations without opening a ticket with IT. Source row IDs ride along in the export so federal auditors can walk any LDA back to the verified attendance event.

Cross-listed and combined sections

A graduate-and-undergraduate cross-listed section shares one roster and one attendance record but reports separately to the registrar. Lab sections that share a lecture inherit lecture attendance unless explicitly overridden. The data model handles the same workflow you already run by spreadsheet today, without the brittle exports.

openeducat_attendance hardware mix

Run ZKTeco fingerprint readers at lab doors, MIFARE RFID at lecture-hall gates, dynamic QR on the student portal for hybrid classes, and instructor manual entry for seminars and capstone studios, all writing to the same attendance table. Hardware-procurement decisions stay decoupled from the software.

SIS, report card, and SAP

Section rosters, transcript holds, and satisfactory-academic-progress evaluations live in the same database as attendance. A failed-attendance threshold flags a student's SAP review in real time, with no overnight ETL job from an attendance vendor to the SIS to the financial-aid system.

2,679
Title IV-participating 4-year degree-granting institutions reported by NCES IPEDS 2023-24
15.4M
Fall 2024 4-year US university enrollment per NCES, the population OpenEduCat scales to via branch isolation
30 days
Federal R2T4 deadline after withdrawal-determination date; built-in LDA export keeps the registrar inside it (per 34 CFR §668.22)
NACUBO
Cost-allocation categories from NACUBO FARM align with the OpenEduCat analytic accounts so attendance-driven funding can be reconciled in one ledger

solutionPage.faqTitle

solutionPage.faqSubtitle

Can a single OpenEduCat instance handle a system with 6 campuses and 40,000 students?

Yes. Use one company per system, branches per campus, and Postgres on hardware sized for the row volume. Section, room, and instructor record rules already isolate by branch. Production deployments run six- and seven-figure student records on a single instance with read replicas for reporting workloads. The architecture scales horizontally on the database tier without a vendor charging per active user.

How does a teaching assistant mark a 200-person lecture?

The TA opens the section's attendance form, scans an RFID or QR roll at the door, and reviews the missing list on a phone or tablet. Manual overrides are signed with the TA's user ID. The instructor of record approves or rejects from the same form, and the audit log keeps the trail. The full read-and-mark cycle for a 200-seat lecture takes under three minutes once the gate is configured.

Does the system handle a withdrawal mid-semester for Title IV?

Yes. Mark the student withdrawn with a withdrawal-determination date. The attendance module pulls the verified last-date-of-attendance from the section logs and exports the row financial aid needs for the Return of Title IV Funds calculation. No off-system spreadsheet, no manual roster review. The 30-day window in 34 CFR §668.22 is a routine deadline, not a fire drill.

We use a separate SIS today. Can we run only the attendance module?

Yes. openeducat_attendance can run with a minimal openeducat_core install. Import rosters via CSV or the OpenEduCat student API and export attendance back to your SIS on a schedule that matches your reporting cadence. Most universities consolidate student, course, and attendance on OpenEduCat once they see the integration cost of keeping the three split across three vendors.

What does LGPLv3 mean for us as an institution?

The module is free to install, modify, and run on any hardware. If you distribute a modified version outside the institution, the source for your changes ships with it. Running a modified instance internally carries no redistribution obligation. Most universities self-host with internal customizations and never need to publish anything, since they are the end user of their own modifications.

¿Listo para Transformar Su Institución?

Vea cómo OpenEduCat libera tiempo para que cada estudiante reciba la atención que merece.

Pruébelo gratis por 15 días. No se requiere tarjeta de crédito.