E-Learning Portal for Schools

ClassDojo, ParentSquare, Bloomz, and Remind are parent-communication tools not integrated with the school SIS or LMS. Teachers duplicate work: attendance goes into the SIS, grades go into the LMS, and separately teachers post announcements to ClassDojo or ParentSquare for parents. openeducat_parent replaces the standalone parent-communication tool with a portal that reads from the SIS, LMS, attendance, and fee record automatically. Parents see the same attendance, grade, and assignment data teachers entered once, without a separate sync. Schools consolidating on the platform typically report 60-80% reduction in parent-communication time in annual staff surveys.

COPPA (Children's Online Privacy Protection Act) governs online data collection from children under 13 in the US. The platform ships with K-12 defaults: no external behavioural tracking or advertising, parent-consent capture at enrolment with renewable mechanism, data-deletion workflow honoring parent requests, and access controls scoped to education-record use only. The school remains the data controller under COPPA; the platform provides the mechanisms the school needs to comply. Self-hosted deployments keep student data inside institutional infrastructure, simplifying the COPPA compliance posture further. State-specific laws (California SOPIPA, Illinois SOPPA, New York Education Law 2-d) build on the same platform baseline.

Yes. Many K-12 schools run Google Classroom or Microsoft Teams Education as the day-to-day teacher-assignment tool because both are strong for daily-assignment workflow and integrate with the host productivity suite. Neither is a full LMS or SIS. The typical setup is Google Classroom or Teams for daily assignments plus OpenEduCat for SIS, attendance, gradebook, fees, and parent portal. LTI 1.3 and Google Classroom API integrations bring Classroom-created assignments and grades into the OpenEduCat gradebook, so teachers keep their preferred assignment tool while the SIS and parent portal stay in sync automatically.

FERPA (Family Educational Rights and Privacy Act) protects student education records from unauthorized disclosure. The platform ships role-based access controls scoped to legitimate educational interest, immutable audit logs of who accessed which record when, parent-rights workflow for review and amendment of education records for students under 18, and directory-information opt-out handling. The school remains the FERPA custodian; the platform provides the technical mechanisms. Self-hosted deployment keeps education records inside institutional infrastructure, which most district legal counsels prefer for FERPA posture. State-specific enhancements (California AB 1584, Colorado Student Data Transparency and Security Act, Connecticut Public Act 16-189) layer on top.

Chronic absenteeism, defined by NCES and the US Department of Education as missing 10% or more of scheduled school days (roughly 18 days in a 180-day year), predicts graduation risk better than grades at middle-school age. The platform tracks scheduled learning time (in-person periods plus synchronous online sessions) and attendance completion against it, then flags students in three tiers: at-risk (5-9% absences), chronic (10-15%), and severe chronic (above 15%). Counsellors see a weekly priority list. Research from Attendance Works and the Everyone Graduates Center at Johns Hopkins shows early intervention at grade 6-8 improves high-school graduation rates by 10-15 percentage points, but only if students are flagged in September, not April.

Yes. US public districts, UK Multi-Academy Trusts, and international school groups roll data up from campus level to district or group level while each campus retains full autonomy over daily workflow. Each campus can run its own bell schedule, calendar, fee structure, and staffing model; the district or group dashboard aggregates attendance, enrolment, and financial metrics. A UK MAT running 12 academies produces one unified DfE School Census export instead of stitching 12 separate exports; a US district running 50 schools produces one federal CRDC (Civil Rights Data Collection) export. Role-based access ensures a campus principal sees their campus, a district superintendent sees the district, and a regional director sees the assigned campuses.

The platform follows WCAG 2.1 AA with 2.2 alignment in progress: screen-reader support, keyboard navigation, accessible video player with caption tracks, and high-contrast themes. For K-12 special-education specifically, the IEP (Individualized Education Program) and 504 Plan workflows in openeducat_health track accommodations, service minutes, goal progress, and annual-review scheduling per IDEA (Individuals with Disabilities Education Act) requirements. Assignment-level accommodation flags (extended time, reduced item count, alternative-format response) surface to teachers automatically. Section 504 and Title II of ADA compliance require both the accessible platform baseline and the school's accommodation workflow; the platform provides the substrate the school builds on.

A single-campus K-12 school with 500-1,500 students typically completes an OpenEduCat rollout in 8-14 weeks: 2-3 weeks for platform provisioning and configuration, 3-4 weeks for data migration from the existing SIS (PowerSchool, Infinite Campus, Skyward, or district-specific system) via CSV import with parent and historical grade backfill, 2-3 weeks for teacher training on the LMS and parent-portal workflow, and 1-2 weeks for parent-app rollout with grade-level or school-wide launch events. A multi-campus district with 5,000-20,000 students typically runs a 6-12 month phased rollout with campus-by-campus migration. Change management is the determining factor: schools that invest in teacher training and parent communication launch smoothly; schools that treat it as an IT project alone hit friction.