A Functional Assessment And Curriculum For Teaching Students With Disabilities

Getting a Functional Assessment Right Before You Build a Curriculum

Most people skip the assessment part or treat it like paperwork they have to file so the district doesn't sue them. That's why their curriculum feels generic. I've seen individualized education programs that were basically copy-pasted from a template with the student's name filled in. The kid ends up with twelve pages of goals that don't match what's actually happening in the classroom. A Functional Assessment And Curriculum For Teaching Students With Disabilities isn't really two separate things. It's one process. You figure out what's driving the behavior or the learning gap, then you build the curriculum around that specific function. If you do it backwards, everything falls apart. The standard approach starts with collecting data. Direct observation, parent interviews, records review, and then a hypothesis statement. The hypothesis is the part everyone rushes through. It should look something like this: when given independent academic work, the student engages in off-task behavior to escape non-preferred tasks, as evidenced by... and then you put actual numbers. Not "often" or "sometimes." Actual frequency, duration, intensity. I spent three weeks trying to figure out why a sixth grader would consistently fling his materials during math. The referral said "defiant." The records said "behavioral problems." Parent interview suggested he was struggling with reading. I watched him for two days doing ABC tracking — antecedent, behavior, consequence — and realized the behavior only happened during independent worksheet work. Not during group instruction. Not during one-on-one. Not during reading. The function was task avoidance, but specifically avoidance of independent text-heavy academic work. So we stopped assigning him independent worksheets and built a curriculum around embedded instruction with visual supports and frequent check-ins. His "behavior incidents" dropped from averaging four per day to zero in about two weeks. The problem wasn't defiance. It was a reading comprehension deficit masked as behavioral dysfunction.

Building A Functional Assessment And Curriculum For Teaching Students With Disabilities

Here's the practical sequence. First, you identify the target skill or behavior. This seems obvious but teachers frequently pick the most visible problem instead of the most impactful one. A student who shouts out in class might be more helpfully addressed by building turn-taking skills into the existing content rather than running a separate social skills group. Second, you collect baseline data. Three to five days of direct observation gives you something workable. More than that and you're just delaying the intervention. Less than that and you're guessing. Use momentary time sampling for classroom behaviors — check in every two minutes and record whether the behavior is occurring at that exact moment. It takes about twenty minutes per session and gives you a reliable estimate without requiring continuous full-time observation. Third, you develop the hypothesis. This is where most assessments go sideways. The hypothesis needs to be testable. "The student has an emotional disturbance" is not a testable hypothesis. "The student engages in elopement during unstructured transitions between indoor and outdoor activities" is testable. You can design an intervention around that and see if it changes the data.

Fourth, you match the curriculum to the function. This is the part that doesn't get enough emphasis. If the function of a behavior is escape, the curriculum modification might involve reducing response demands, increasing choice, or embedding preferred activities within non-preferred ones. If the function is attention-seeking, the curriculum should build in structured opportunities for appropriate attention-seeking behavior. If it's sensory-based, you need an environmental modification first, not a behavioral one. I ran into a kid last year — ninth grade, diagnosed with autism, referred for "stereotypic behavior" that was mostly hand-flapping when excited or overwhelmed. The initial assessment classified it purely as self-stimulatory. But when I did a structured observation during different activity types, I noticed the flapping increased dramatically during unstructured times and decreased during highly structured, predictable routines. The hypothesis shifted from sensory-motivated to anxiety-related. We built a curriculum around teaching self-advocacy language — "I need a break" instead of hand-flapping — and paired it with a predictable visual schedule he could reference independently. The flapping decreased by about sixty percent in six weeks. Not gone, but manageable. The important thing is that treating it as purely sensory would have missed the actual lever to pull. For the curriculum construction itself, you're looking at a few concrete elements. Skill sequencing matters more than anyone admits. Take applied behavior analysis work with students who have intellectual disabilities. The difference between a curriculum that works and one that doesn't often comes down to how finely you've broken down the prerequisite skills. A student who can't button a shirt might not be struggling with buttoning. They might be struggling with the fine motor coordination to hold the shirt steady with one hand while manipulating the button with the other, or they might not have developed the visual discrimination to align the buttonhole with the button. You test each component separately before you assume the target skill is the problem.

Universal Design for Learning principles should be baked into the curriculum from the start, not layered on as an accommodation after the fact. That means multiple means of engagement from day one — giving students choice in how they demonstrate learning, varying the rewards and incentives, and building in options for collaboration versus independent work. It means multiple means of representation — presenting information visually and verbally, providing glossaries and graphic organizers as standard materials rather than accommodations. And it means multiple means of action and expression — allowing students to respond by writing, speaking, drawing, or using assistive technology without having to justify which mode they're using. Data collection doesn't have to be elaborate. A simple frequency count with a tally sheet takes maybe ten seconds per occurrence and gives you a clear picture over time. For skills-based curriculum, probe data — administering a task and recording correct versus incorrect responses — is sufficient for most progress monitoring. You're not running experiments. You're checking whether the student is learning the material you're teaching them. One thing that trips people up repeatedly: the curriculum has to be measurable. "The student will improve reading comprehension" is not a measurable goal. "The student will answerWh-questions about a grade-level passage with eighty percent accuracy across three consecutive sessions" is measurable. You need to be able to look at the data and say definitively whether the student met the goal or not. Vague goals create vague interventions and then people blame the student when nothing changes.

Here's where the method breaks down. Functional assessments are only as good as the observer. If you're doing a formal functional analysis — the kind where you systematically manipulate antecedents and consequences to identify function — you need someone trained in that methodology. There are published protocols from the Field et al. framework and the Iwata methodology. If you haven't done formal FA training, you're limited to indirect methods and descriptive assessments, which are useful but don't give you the same level of confidence about function. I've seen cases where the hypothesis was wrong because the observer misattributed the function, and the entire intervention plan was built on a false premise. The student didn't get better. Nobody figured out why until someone with more experience re-ran the assessment. Another limitation: functional assessments capture behavior in a snapshot. A student might engage in escape-motivated behavior during academic tasks on Monday but social attention-motivated behavior during the same tasks on Thursday depending on what happened the night before, whether they had a good sleep, or whether a peer interaction went poorly. One assessment doesn't tell the whole story. I usually recommend at least two assessment sessions separated by a few days, and if the hypotheses don't converge, a third session with a different observer. Curriculum implementation is where the rubber meets the road. You can have the most thorough functional assessment in the world and if the teacher doesn't implement the curriculum with fidelity, it won't work. Fidelity checks are non-negotiable. They don't have to be expensive — a five-minute classroom walk-through with a simple checklist taking thirty seconds per item covers most of what matters. Are the prompts being delivered as designed? Is the reinforcement schedule matching the plan? Are the data being collected on schedule? If fidelity is below eighty percent, you fix the implementation before you conclude the curriculum doesn't work.

Progress monitoring should happen at least weekly for behavior goals and biweekly for skill-based goals. More frequent than that and you're just generating noise. Less frequent and you'll miss trends until it's too late to adjust. Graph the data. Visual inspection of trend, level, and variability across three to five data points is sufficient for making most instructional decisions. You don't need statistical analysis for a classroom setting. The biggest mistake I see is treating the functional assessment as a one-time event that happens at the beginning of the year and then gets filed away. It's not. The function of behavior changes. Skills develop. What was working in September might not be working in November. Reassess when data show a plateau for three to four weeks, when the student's environment changes significantly, or at minimum every ninety days. The reassessment doesn't have to be as thorough as the original. Often a quick re-observation and a review of progress data is enough to confirm you're still on the right track or to signal that a pivot is needed. If you're looking for a starting point for the assessment portion, the Functional Behavior Assessment Checklist from the Technical Assistance Center on Positive Behavioral Interventions and Supports has a straightforward template. For curriculum mapping tied to functional assessment findings, the PBIS.org curriculum resource library has free materials organized by function and age group. Neither is a complete solution — you'll always need to customize — but they're better than starting from scratch and they save probably two or three hours per student compared to building your own framework from scratch.