Student Information System for Special Education

For districts whose IEP-management needs are covered by a document vault with role-based access, IEP team routing, accommodation delivery, and Section 618 reporting, OpenEduCat covers the essentials in one platform. For districts with deeply complex IEP workflows (specific state-required IEP wizards, specialized progress-monitoring instruments, IEP goal-bank libraries), Frontline IEP Direct and SEAS have deeper feature sets built up over decades of state-specific customization. Many districts use Frontline or SEAS for the IEP document itself while running OpenEduCat as the general SIS and daily-operations layer, connected via roster sync.

Every user has a role (special-education teacher, general-education teacher, related-service provider, administrator, parent). Each role has permissions defined per data type. IEPs and 504 plans are restricted to the case manager, IEP team members, teachers of record, related-service providers, and parents. General-education teachers not on the IEP team see only the accommodations relevant to their class, not the full IEP. FERPA-required audit logging records every access, immutably, satisfying both FERPA (34 CFR 99) and IDEA (Section 617) confidentiality expectations.

Under IDEA, when a student on an IEP faces disciplinary action removing them from placement for more than 10 school days (cumulative or consecutive), the district must hold a Manifestation Determination Review within 10 school days of the decision. The review team decides whether the behavior was caused by, or had a direct and substantial relationship to, the student's disability, or was the direct result of failure to implement the IEP. The platform tracks cumulative discipline days per IEP student, triggers Manifestation Determination workflows automatically at the 10-day threshold, and produces the documentation the review team needs.

IDEA Section 618 is the federal requirement under which states report to the US Department of Education on IDEA Part B and Part C students. Required reports include child count, educational environment (percent of day in general education), exit reasons (graduation, dropout, transfer, age-out), discipline (suspensions and expulsions), and personnel (special-education staff by qualification). The platform computes these from operational data (attendance, enrollment, discipline log, HR records) and produces state-format Section 618 files. Districts hand the files to state special-education directors for state-level submission to the US Department of Education.

IDEA Section 615(b)(3) requires Prior Written Notice whenever a district proposes to, or refuses to, initiate or change the identification, evaluation, educational placement, or provision of a free appropriate public education (FAPE) to a student with a disability. The notice must be in writing, in the parent's native language, and delivered before the proposed action. The platform generates PWN documents from templates, tracks parent receipt and response, and archives PWN documents against the student record with the 5-year retention IDEA requires.

IDEA Section 614(d)(1)(A)(VIII) requires transition-focused IEP components starting no later than the first IEP in effect when the student turns 16 (some states require by age 14). Transition components include measurable postsecondary goals, transition services needed to reach those goals, and courses of study aligned to the goals. The platform tracks transition components as first-class fields on the IEP, produces transition-service delivery logs, and generates the Summary of Performance document required at exit from IDEA services (typically at graduation or age-out).

Yes. The platform publishes a REST API and OneRoster 1.2 endpoint for roster and student demographic data. State data warehouses and district student data warehouses consume the API for state reporting, longitudinal analysis, and cross-system integration. For districts running a proprietary SIS for general SIS and using OpenEduCat for special education, roster sync flows both directions (student demographics from SIS to OpenEduCat, IEP data from OpenEduCat back to the SIS if the SIS supports it, or as flat file for state reporting).

FERPA (34 CFR 99) gives parents (and students at age 18 or beyond) the right to inspect and review education records, seek amendments, and control disclosure. The platform supports parent portal access to the full education record (within FERPA scope), amendment request workflows with district review, and consent-for-disclosure tracking. When a parent requests all education records under FERPA, the platform produces a complete export in a reviewable format within the 45-day FERPA response window. Audit logs document the release for compliance record-keeping.