Specially Designed Instruction Checklist

What Specially Designed Instruction Actually Looks Like in Practice

Specially Designed Instruction (SDI) is the part of a student's IEP that describes the modifications and accommodations that make the general education curriculum accessible to them. It's where the law meets the classroom, and it's also where most IEP meetings fall apart because people conflate accommodations with modifications with service delivery. A well-written SDI section tells you exactly who does what, how often, and in what setting. A vague one gives you nothing to enforce. I spent eight years writing and implementing IEPs before I stopped treating SDI as a checkbox exercise. The turning point was a student whose IEP said "extended time" under SDI without specifying the format. The testing coordinator gave him double time on paper tests but not on computer-adaptive assessments. He got different treatment depending on which platform his teacher used, and nobody caught it until the state report card came out. That student's IEP looked compliant on paper and was functionally useless in practice. That's the baseline you're working from.

Building a Specially Designed Instruction Checklist

A functional checklist for SDI needs to cover five categories: the disability-based need, the specific instruction type, the delivery mode, the frequency and duration, and the progress measurement. Every line item in a student's SDI should answer at least one of those questions. If a line just says "speech language therapy 30 minutes," you don't know who delivers it, in what setting, toward what goal, or how success is measured. That's a service schedule, not specially designed instruction. Here's the structure I use, built from the ground up after realizing that checklist-style approaches save about 40 minutes per IEP compared to free-form writing: Category 1: Need Statement

• Which disability category drives this SDI?
• What specific skill gap does it address? Reference the present levels.
• Is this need ongoing or seasonal?

Category 2: Instruction Type Category 3: Delivery Parameters Category 4: Frequency and Duration

Category 5: Progress Monitoring The most common error I see is writing SDI that duplicates the general education curriculum instead of designing instruction that's specially designed. If a student receives the same reading lesson as everyone else with the only difference being that they get extra time, that's an accommodation, not specially designed instruction. SDI requires a qualitative difference in how the content is taught, not just a quantitative difference in how much time is given. Another pattern that shows up constantly is conflating related services with SDI. Speech therapy is a related service under IDEA. It's not SDI unless it's being used to directly support access to the academic curriculum. When a student gets speech for social pragmatics that feeds into their participation in Socratic seminars, that's where SDI and related services overlap and both need to be documented separately. They serve different legal and instructional purposes.

The third mistake is writing SDI that can't be observed or measured. Phrases like "teacher will provide support as needed" or "student will receive differentiated instruction" are unenforceable. "As needed" means nothing without a defined trigger. Differentiated instruction means everything and therefore nothing. I had a parent tell me once that her son's IEP said he received "visual supports" and when I asked what that looked like, the teacher had no idea either. The IEP was technically compliant and completely hollow.

The Edge Case That Broke My Spreadsheet

About three years ago I worked with a student who had a specific learning disability in reading and an anxiety disorder that manifested as school refusal on test days. His SDI included extended time, small group administration, and a quiet setting for assessments. The problem was that the anxiety component wasn't addressed in the SDI at all. It was in his accommodated testing section, but the testing coordinator didn't know about it because the IEP team had split the document into two separate binders — one for instruction and one for testing — and the counselor's recommendations stayed in the testing binder. The workaround I implemented was a cross-referencing system. Every SDI line item now includes a note flagging whether it connects to another section of the IEP. For this student specifically, I wrote "Anxiety-related accommodations per Section 504 Plan attached — see Page 4, Item 7" directly in the SDI. It sounds minor but it eliminated the binder separation problem entirely. Now every service provider reads the same document top to bottom instead of mining fragments from different sections.

Advanced Nuance: The SDI-to-Goal Alignment Problem

Most IEP teams don't explicitly connect SDI to specific goals. They list goals in one section and SDI in another and assume the connection is obvious. It isn't. When you're writing the SDI checklist, I recommend adding a field that maps each SDI item to the exact goal numbers it supports. So instead of writing "reading intervention 4x/week 30 minutes," you write "reading intervention 4x/week 30 minutes — supports Goal 1, Goal 3, and Goal 5." This does two things. First, it forces you to justify each SDI item by linking it to an measurable outcome. Second, it gives parents and auditors a clear trail from service to result. When a dispute comes up about whether the student received services as written, you can point to the alignment map and show exactly which goals were targeted and what the data says. The counter-intuitive part is that adding this alignment field actually reduces the number of SDI items you write. When I started requiring explicit goal mapping, my teams naturally eliminated about 30 percent of SDI lines that couldn't be traced to a goal. Those were drift items — well-meaning additions that had no connection to measurable outcomes. Some were legacy items from previous years that nobody had removed. The ones that stayed had purpose.

Limitations and When This Approach Fails

A checklist-only approach to SDI has real limitations. It works well for students with clear, discrete needs — a specific learning disability in math, speech language impairment affecting fluency, ADHD requiring organizational support. It breaks down for students with complex, overlapping needs where the boundaries between accommodations, modifications, related services, and SDI blur significantly. A student with multiple disabilities who needs adaptive PE, occupational therapy, and alternative assessment isn't well-served by a linear checklist. The checklist also assumes that the IEP team has the expertise to make accurate decisions about what "specially designed" actually means for a given disability. It doesn't provide that expertise. A checklist won't tell you whether a student with dyslexia needs Orton-Gillingham or Wilson or just phonics-based explicit instruction. Those decisions require professional judgment about the student's profile, not a form field. For complex cases, I recommend pairing the checklist with a separate narrative section that documents the team's clinical reasoning. The checklist handles the compliance and tracking. The narrative handles the justification. Both are necessary. Neither is sufficient alone.

Download and Implementation

The full Specially Designed Instruction Checklist I've been referencing is structured as a spreadsheet with tabs for each category above, plus a goal-alignment tab and a cross-reference flag system. It takes approximately 15 minutes to complete per student once you're familiar with the format, compared to 45 minutes or more for free-form IEP writing. The time savings comes from not having to figure out what to include each time — the structure does the thinking for you. If you're building your own version, start with the five-category framework and add columns for goal alignment and cross-reference flags. Don't add complexity until you've used the basic version for at least a semester. The biggest mistake teams make is over-engineering the checklist before they've tested whether it actually changes their output quality. A simple checklist used consistently beats a comprehensive one that sits in a folder nobody opens. The checklist format also scales poorly across grade levels without modification. What works for a high school student needing SDI in algebra is very different from what a kindergartener needs in foundational reading. I maintain separate versions for elementary and secondary, with the secondary version including additional fields for transition-related SDI and postsecondary skill building. The elementary version includes more granular developmental benchmarks.

One final note on enforcement: the checklist is only as good as the team's willingness to use it honestly. I've seen IEPs where every box was checked and every field was filled, but the resulting SDI section described exactly what every student in the class receives. That's a compliance facade, not specially designed instruction. The checklist surfaces that problem faster than free-form writing does, but it can't fix the underlying issue. That requires a team that actually believes the student needs something different, not just something documented.