Documentation Requirements: IDEA, Section 504, FERPA, Title VI

Four federal frameworks set expectations for the records a school keeps about a student's support: IDEA for students with IEPs, Section 504 for students with disabilities served under a 504 plan, FERPA for who may see any of it and when, and Title VI with the Equal Educational Opportunities Act for the language families receive it in. None of them prescribes a form. All of them assume a dated, factual, retrievable record exists, and each becomes a problem for the district at the moment that record turns out to be somebody's memory. This guide lays out what each framework expects, what a complete record includes, and a review checklist for leaders.

The four frameworks at a glance

IDEA: the progress report is only as good as the data

IDEA's IEP content rules (34 CFR 300.320) require measurable annual goals, a description of how progress toward each goal will be measured, and a statement of when periodic reports on that progress will be provided, for instance with quarterly report cards. The regulation sets no minimum number of data points. It sets a standard the data has to meet: the report must describe progress toward a measurable goal, in the measure the goal names.

That standard fails in predictable ways. A goal measured in percent of trials correct cannot be reported from a daily yes or no mark. A goal with two data points in a quarter cannot honestly be described as showing progress, and a hearing officer will ask why the report did. A report written from memory the night before it is due is a narrative, not evidence. Our complete guide to IEP progress monitoring covers matching the measurement to the goal, and from daily notes to IEP progress report covers the report itself.

Two further IDEA provisions matter for records. When a district uses response to intervention in identifying a specific learning disability, 34 CFR 300.309 requires data-based documentation of repeated assessments of achievement at reasonable intervals, provided to the parents. That is a regulatory requirement for dated tiered-intervention data, and it is where thin MTSS records become an eligibility problem. And 34 CFR 300.503 requires prior written notice, in the parent's native language unless clearly not feasible, whenever the district proposes or refuses to change identification, evaluation, placement, or services.

Section 504 and MTSS: implementation evidence

Section 504 does not carry IDEA's progress-report clock. It requires an evaluation before placement, a plan that provides a free appropriate public education, periodic reevaluation, and procedural safeguards. What a reviewer, a parent's advocate, or the Office for Civil Rights asks in a 504 dispute is usually simpler than an IDEA question: was the plan implemented? A 504 plan that lists preferential seating, extended time, and a check-in with a counselor is a promise. The dated record of the seating, the extended time granted on each assessment, and the check-ins that happened is the evidence the promise was kept. Tracking IEP and 504 accommodations as daily evidence covers how to keep that record without adding a second system.

MTSS is defined by states and districts rather than federal statute, but it inherits the same expectation from two directions. From above, a tier change or a referral for evaluation should rest on dated intervention data, and the IDEA rule cited earlier turns that into a legal requirement when the data feeds an SLD determination. From the side, several states now require that behavior referrals be documented. California's SB 274, effective July 2024, requires a referral for in-school intervention to be documented and placed in the student's record within five business days. The MTSS tier documentation checklist lists what a team should be able to produce at each tier.

FERPA: who sees what, and the trail that shows it

FERPA defines education records broadly: records directly related to a student and maintained by the school or by a party acting for it. A teacher's daily behavior notes in a shared system are education records. So are data points, accommodation logs, and family messages kept in a platform the school uses. The practical consequences:

• Access rights. Parents may inspect and review their child's records, and the school must comply within 45 days (34 CFR 99.10). IDEA tightens this for students with IEPs: without unnecessary delay and before any IEP meeting or hearing (34 CFR 300.613). Several states set shorter windows. A record that cannot be retrieved for a parent inside the window is a violation regardless of its quality.
• Amendment. Parents may ask that inaccurate or misleading records be amended, and are entitled to a hearing if the school refuses. Factual, observable notes ("left the room twice after tasks were assigned") survive an amendment request; characterizations ("defiant," "manipulative") do not.
• Internal sharing. Records may be shared without consent with school officials who have a legitimate educational interest. Every adult in the building does not have one for every student. Role-based access that matches legitimate interest, with an audit trail, is how a district demonstrates the exception was applied rather than assumed. What teachers should see versus the support team works through the lines.
• Vendors. A vendor may hold records as a school official only under the school's direct control over their use and maintenance, which in practice means a signed data agreement, a named subprocessor list, and working export and deletion. Student data compliance review: questions to ask a vendor is the checklist.

Title VI and the EEOA: the language the record reaches families in

Title VI of the Civil Rights Act of 1964 and the Equal Educational Opportunities Act of 1974, as applied by the U.S. Departments of Education and Justice (most fully in their January 2015 guidance on English learners), require schools to communicate with limited-English-proficient parents in a language they can understand about anything the school communicates to English-proficient parents. The guidance names registration, grievance procedures, language assistance programs, parent-teacher conferences, report cards, discipline, and special education and related services among the essential information, and it states that schools should not rely on students, siblings, or untrained staff to interpret.

For a records review, the question is whether the communications the school sends English-speaking families have equivalents for every other language the school's families speak, and whether the school can show it. A progress update program that reaches half the families is a Title VI exposure created by the school's own good practice. Multilingual families: communicating without a translator covers the practical side.

Contemporaneous documentation and due process

Hearing officers, mediators, and OCR investigators weigh records on a few plain qualities. Was the entry made at or near the time of the event, or reconstructed later? Is it dated? Is it factual and observable rather than a judgment? Is it consistent with the other records, the progress reports, and the notices? Can the district produce it on request? A record that is contemporaneous, dated, factual, and retrievable carries weight. The rest of the file, however well written, is testimony.

The record you did not keep is the case you cannot make. A district that provided every accommodation in a 504 plan but logged none of them is in the same position at a hearing as a district that provided none. This is why documentation load is a legal-risk question and not only a staffing one: the practices that make records complete are the ones that make them fast enough to keep. Our post on documentation habits that hold up covers the teacher-level habits, and special education paperwork and burnout covers why the load itself is the failure point.

A leader's review checklist

Where Evident fits

Evident is the daily record layer: teachers log data points, notes, accommodation deliveries, and family updates once, with timestamps, and the same entries build the progress report, the evidence packet, and the translated family update. Access is role-based and audit-logged, the school signs a data agreement with a named subprocessor list, and export and permanent deletion are built in. Family-facing text is translated with student names removed first. The security overview describes the controls, and the sample evidence packet shows what the record produces. Your district's IEP system remains the official record where your state requires it; Evident is where the evidence behind it is kept current.