Open Source Attendance Management For K12 Schools

"Free" usually means no licence fee for vendor-hosted SaaS — you do not get the source code, cannot deploy inside the district network, and cannot extend reason codes or state-reporting templates without a paid change request. Open source under LGPLv3 means the code is published: your IT director can read it, run it on the district's own infrastructure, fork it to add a district-specific reason code, and demonstrate to a FERPA or BIPA audit that no biometric data leaves the perimeter.

BIPA (740 ILCS 14), Texas CUBI (Business & Commerce Code 503.001), Washington HB 1493 and a growing list of state statutes require written informed consent before collecting a minor's biometric identifier and impose strict storage rules — BIPA carries $1,000 to $5,000 statutory damages per violation and a private right of action. The largest source of exposure is sharing the biometric template with a third-party SaaS processor. Because OpenEduCat is self-hostable, the template database lives inside the district's own VPC, never transmitted to a vendor — the cleanest legal posture under every US state biometric privacy statute.

Yes. OpenEduCat uses model inheritance as a first-class extension mechanism. Custom templates — a district-specific CALPADS extract, a new PEIMS reason, a Florida Survey 2 variant — live in a separate module that inherits from the core attendance module. When the core upgrades, your custom module continues to apply on top. State reporting specs change every year; the district adapts without forking off the upstream codebase or losing security updates.

PowerSchool and Infinite Campus are the dominant proprietary US K-12 SIS attendance platforms with deep state-reporting libraries. The trade-off: both are closed-source SaaS, priced per-student-per-year, with limited control over biometric storage and no ability to read or extend the source. OpenEduCat covers the same ground — daily attendance, period attendance, tardy tracking, absence coding, state extracts, parent notification — under LGPLv3, with self-hosting and no per-seat cost. The choice depends on whether the district values vendor-managed convenience or source-code control and biometric-data sovereignty.

Yes. Every attendance edit — including back-dated marks tied to grade-change requests, extended-illness reclassifications and credit-recovery adjustments — is logged with user ID, timestamp, IP and prior value. The log is filterable by student, staff, date range and action, and exportable for the district's retention period. When a parent files a FERPA challenge over a record that affected GPA or graduation, or when a state auditor reconciles ADA funding, the chronological evidence is in the system — aligned with NCES Common Data Element guidance and US Department of Education attendance-reporting frameworks.

Yes. The attendance module exposes the same open XML-RPC and JSON-RPC API as the rest of OpenEduCat, so absence notifications fire to your existing parent-communication tool (ParentSquare, Remind, ParentMail), gradebooks read attendance directly, and PowerSchool / Infinite Campus / Skyward / Aeries sync rosters and daily attendance via the open API rather than a per-seat connector licence. Districts that want to keep their existing SIS and only swap the attendance engine can do so.