Custom IEP software development, built around the rules it has to follow

An Individualized Education Program is a legal document before it is a form in an application. Federal regulation sets what it must contain, when it must exist, who may see it and, from 2027, how accessible the system holding it has to be.

This page is for two buyers: a district whose IEP system cannot hold its process, and an edtech company building a special education product that has to survive procurement. Bles Software builds custom software, AI agents and integrations from Israel for clients in the US, the UK, the EU and Israel. We do not sell an IEP product. We build the one your process needs, or fix the one you own.

Start from what the regulation says the document must contain

34 CFR 300.320(a) lists what an IEP must include, and it reads like a data model somebody already wrote for you: present levels, measurable annual goals, how progress toward them is measured and reported, the services and program modifications, any non participation with nondisabled children, assessment accommodations, and the projected start date with frequency, location and duration.

Most IEP systems that frustrate their users store that as free text behind a rich editor. Progress reporting then becomes manual work, because a goal that is only prose cannot be measured by the software holding it. Model goals and their measurement method as structured records and the quarterly report writes itself.

The clocks the system should keep, not the staff

Four dated obligations run through every special education office. An initial evaluation must be conducted within 60 days of receiving parental consent, or the timeframe the State sets instead (34 CFR 300.301(c)(1)). An IEP must be in effect for each child at the start of each school year (34 CFR 300.323(a)). The team reviews it not less than annually (34 CFR 300.324(b)(1)(i)). A reevaluation must occur at least once every three years unless the parent and the agency agree it is unnecessary (34 CFR 300.303(b)(2)).

These are cheap to build and expensive to miss. Derive every due date from consent, school year start and the last signed plan, then surface what is at risk this week. Build the exceptions too: the 60 day window does not apply where a parent repeatedly fails to produce the child, or where a child transfers mid evaluation.

FERPA shapes the architecture, including ours

Parents may inspect and review education records (34 CFR 99.10) and ask for an amendment where a record is inaccurate or misleading (34 CFR 99.20), with a hearing if that is refused (34 CFR 99.21). A system that overwrites history in place, or cannot produce a complete readable record for one child on request, makes both rights hard to honour.

The vendor relationship has its own rule. Under 34 CFR 99.31(a)(1)(i)(B) a contractor counts as a school official only where it performs a function the agency would otherwise use employees for, is under the direct control of the agency over the use and maintenance of education records, and is subject to the redisclosure limits in 34 CFR 99.33(a). Read that as a build constraint: scoped and logged access, and development against realistic synthetic records rather than live student data.

Accessibility now has a date on it

The Department of Justice published its Title II web and mobile accessibility rule on 24 April 2024, at 89 FR 31320. It requires public entities to meet WCAG 2.1 Level A and AA for web content and mobile apps they provide, directly or through contractual, licensing or other arrangements. Procurement teams read that last clause twice, because a purchased IEP system is exactly such an arrangement.

The dates then moved. An interim final rule published on 20 April 2026 extended both by a year, and 28 CFR 35.200(b) now reads: 26 April 2027 for a public entity other than a special district government with a total population of 50,000 or more, and 26 April 2028 for an entity under 50,000 or any special district government. For a school district the rule settles its own classification. 28 CFR 35.104 defines a special district government as a public entity other than a county, municipality, township or independent school district, so an independent school district is not one, and the same section sets a district's total population from the Census Bureau's most recent Small Area Income and Poverty Estimates. Look that figure up before assuming the later date, because a district at 50,000 or more is on April 2027.

Where AI helps, and where it must not decide

The useful applications are narrow and real: turning a case manager's observations into a first draft of present levels, suggesting measurable phrasing for a goal the teacher already chose, or flagging that a draft goal has no stated measurement method before the meeting rather than after it.

What it must not do is decide eligibility, services, placement or goals. The IEP is developed by a team that includes the parents, and 34 CFR 300.324(a)(1) sets what that team must consider. We found no Department of Education or OSEP guidance specific to AI in IEP development as of September 2026, so State and district policy governs and it varies. Build the approval step, the authorship record and the log of what was suggested versus what a human kept.

What a first engagement looks like

The honest first question is whether to build at all. An established platform that fits your process is cheaper than anything custom, and we will say so if that is what your requirements describe. Custom earns its cost when the process is genuinely yours: an unusual State reporting extract, a multilingual parent workflow, a product you are taking to market, or a system sitting between tools that will not talk to each other.

Where a build is right, the first paid step is small and yours whether or not we continue: a written scope of the workflow as it runs today, the integration surface against your student information system, the data model for goals and progress, and a delivery sequence with the compliance clocks in it.