Of all the things written into an IEP or a 504 plan, accommodations are the part most likely to be promised and least likely to be documented. The goal section gets progress monitoring. The services section gets a minutes log. The accommodations grid gets a binder, and the binder gets opened about once a year, the week before the review. This guide is about closing that gap: turning the wording on the grid into a light daily record that proves the accommodation happened and starts to show whether it helped.
It is written for the people who actually deliver accommodations day to day: the case manager coordinating a caseload, the 504 coordinator who never sees the classroom, and the gen-ed teacher who has six plans to honor across thirty students. The examples use composite students, named so and never real, with numbers that fit a normal classroom rather than a research study.
Why accommodation delivery goes undocumented
Accommodation delivery is the least-documented obligation in special education, and the reason is structural, not lazy. The work is spread across many adults, the record belongs to no one in particular, and nothing forces the question until the meeting.
Three things stack up. The first is diffusion of responsibility. A goal has one case manager who owns the data. An accommodation might be delivered by a science teacher third period, a math teacher fifth, and a testing proctor in May. Each one assumes someone else is keeping the record. No one is.
The second is invisibility. A delivered accommodation usually leaves no trace. You read the directions aloud, the student takes the test, the moment passes. Unlike a worksheet or a probe, there is no artifact unless you make one.
The third is the binder problem. The accommodations grid lives in a plan document that no one opens during a normal week. If the only place the accommodation is written is a binder, the only time anyone checks delivery is when the binder comes out, and by then the year is over.
The fix is not heroic record keeping. It is a small habit attached to things you already do, plus wording clear enough that a delivery check takes seconds.
Reading the accommodations grid
Before you can track an accommodation, you have to know exactly what it is. Most grids are written for the meeting, not for the classroom, so the entries are short and vague. The first job is to translate each line into something a person could actually deliver and check.
Take the two most common vague entries. "Extended time" tells you nothing about how much, on what, or where. "Preferential seating" tells you nothing about near what or away from what. As written, neither can be tracked, because neither can be clearly done or not done.
A composite seventh grader we will call Priya. Her grid lists two accommodations in the usual shorthand:
- Extended time
- Preferential seating
Rewritten so any teacher could deliver them and any observer could confirm delivery:
- Extended time (1.5x) on all tests and quizzes longer than 15 minutes, taken in the resource room when Priya requests it.
- Preferential seating in the front third of the room, within clear sightline of the board, away from the hallway door.
The rewrite does not change what Priya is entitled to. It makes the entitlement specific enough that delivery is a yes-or-no fact rather than a judgment call.
You do not need to rewrite the legal plan to do this. Keep a working version of the grid for the classroom that spells out the specifics, and confirm at the next review that the plan wording matches practice. The point is that a vague entry produces vague evidence, and vague evidence is what falls apart in a meeting.
A good rewrite answers four plain questions for each accommodation: what exactly is provided, on which tasks or occasions, where it happens, and who is responsible for providing it. "Extended time" answers none of them. "Extended time (1.5x) on tests over 15 minutes, in the resource room, provided by the proctor" answers all four, and a substitute could read it and do the right thing. The four accommodation categories give you a quick check that the wording is concrete: a presentation accommodation should name how the material is delivered, a response accommodation should name how the student answers, a setting accommodation should name where, and a timing accommodation should name how much and on what. If you cannot tell which category an entry belongs to, it is probably too vague to track.
What counts as delivery evidence
Accommodations fall into four categories: presentation (how the material is given to the student), response (how the student shows what they know), setting (where the work happens), and timing or scheduling (when and how long). Each category produces a different kind of delivery evidence, and knowing the category tells you what a record should even look like.
| Category | Example accommodation | What a piece of delivery evidence looks like |
|---|---|---|
| Presentation | Directions read aloud; text-to-speech for passages | A note on the assignment or a quick log that directions were read aloud on that date, initialed by the adult who did it |
| Response | Answers dictated to a scribe; speech-to-text | The scribed work itself, or a note that a scribe was provided for that task on that date |
| Setting | Separate, quieter room for testing | A note that the test was administered in the resource room, with the date and proctor |
| Timing or scheduling | Extended time, 1.5x, on tests over 15 minutes | A note that the extension was offered and the minutes used, on the test cover or a short log |
The pattern across all four is the same. Delivery evidence answers one question: on this date, for this task, was the accommodation provided. It does not have to be elaborate. An initial and a date on the test cover is evidence. A one-line entry in a log is evidence. What it cannot be is a memory in June of a Tuesday in October.
Notice that some categories leave a natural artifact and some do not. Response accommodations often produce the work itself (the scribed essay exists). Presentation and timing accommodations usually leave nothing unless you make a mark. Those are the ones that need a deliberate check.
Building a tracking habit that survives a real week
A tracking system that asks you to stop and log things in a separate session will not survive past September. The trick is to track the right subset of accommodations and to attach the check to a routine you already run.
- Sort the grid into setup and action accommodations. A setup accommodation is arranged once and then stands: preferential seating, a printed copy of notes, a calculator that lives in the desk. An action accommodation needs an adult to do something each time: read directions aloud, provide a scribe, move the student to a separate room for a test. You log the second kind.
- For each setup accommodation, record the arrangement once. Write that preferential seating is in place as of the date you set it. You do not re-log it daily. If the arrangement changes, you note the change. That is the whole record.
- Attach each action accommodation to the moment it happens. Mark extended time on the test cover as you hand the test back, not in a logging session that night. Initial the assignment when you read the directions aloud. The check rides along with a thing you are already touching.
- Track on task days only, not calendar days. Extended time on tests produces evidence on test days, which might be six days a quarter, not forty. You are not logging every period of every day. You are logging the handful of occasions the accommodation actually applied.
- Do a five-minute weekly scan. Once a week, glance down the action accommodations and confirm each one that should have a mark has one. This catches a missing record while you can still fix it, the same way a weekly data review catches a flat goal line before the quarter ends.
The most common mistake is trying to log everything every day to feel thorough. It is not thorough if you abandon it by October. A short, sustained record on the accommodations that need active delivery beats a perfect system you keep for three weeks.
A typical grid holds somewhere between five and ten accommodations. Once you sort them, you usually find that only three or four are the action kind that need a delivery check, and those three or four apply on a limited set of occasions rather than all day. That is the realistic size of the job: a few accommodations, marked on the days they apply, for one student. Multiplied across a caseload it is still manageable, because the action accommodations tend to repeat across students (extended time and read-aloud directions show up again and again), so you are not inventing a new routine for each plan.
When you share delivery across several teachers, write down who marks what before the year starts. The science teacher initials the read-aloud in third period; the case manager logs the testing-room setting on test days; the proctor records extended-time minutes in May. The single most common reason delivery goes untracked is that everyone assumed someone else owned the mark. A one-line assignment of responsibility, agreed out loud, prevents most of that.
Free printable tracking and log chartsNo account neededThe two questions that are different data
There are two questions about any accommodation, and they need separate records because they answer to different audiences. The first is: was it delivered. The second is: did it help.
Delivery is a question of record. It protects the student's right to the accommodation and shows that the plan was followed. The answer is a yes or no with a date. You collect it by marking that the accommodation was provided.
Effectiveness is an instructional question. It tells the team whether the accommodation is doing its job, whether it should stay, change, or fade. The answer is a judgment, usually a quick rating, gathered on a sample of occasions rather than every time.
This guide focuses on delivery, because delivery is the obligation that goes undocumented. The effectiveness question, how to rate it honestly without ever withholding a support a student is entitled to, is its own discipline, covered in the companion guide on documenting accommodation effectiveness.
Handling refusals and gaps honestly
Two situations come up often enough that they deserve a plan: the student who declines an accommodation, and the day it simply was not provided. Both are part of the record, not embarrassments to hide.
When a student refuses an accommodation, that is still delivery evidence. You offered it, it was available, and the student chose not to use it on that date. Record exactly that. A pattern of refusals is useful information for the team, because an accommodation a student consistently waves off may need to change, but the answer is to bring the pattern to the meeting, not to quietly stop offering it. The student is still entitled to it until the team decides otherwise.
When an accommodation was not provided, say why and resume. Maybe a substitute did not know to read the directions aloud, or the testing room was double-booked. Note the gap plainly, like "directions not read aloud the day of the assembly schedule, substitute covering." A short, honest gap holds up and is even useful, because it becomes one of the naturally occurring without occasions that help answer whether the support matters. What does not hold up is an invented mark for a day you cannot actually account for.
A note on 504 plans and IEPs
The tracking habit is the same for both plans, but the documents differ in a way that changes where accommodation evidence sits. An IEP carries measurable goals and progress monitoring alongside its accommodations, so the accommodation record is one stream of evidence among several. A 504 plan is usually accommodations without goals, which means the accommodation record is often the main evidence that the plan is being followed at all. If you coordinate 504 plans, your delivery log is doing more of the work, because there is no goal data sitting next to it.
That difference matters most at review time. For an IEP, the team has goal progress to discuss even if the accommodation record is thin. For a 504, a thin accommodation record can leave the team with little to show that the plan meant anything in practice. Either way, schools remain responsible for their own legal and procedural obligations, and the structure of these plans varies by state and district, so check your local rules. The practical takeaway is the same: the lighter the rest of the document, the more your accommodation record carries.
Preparing the annual-review summary
The payoff of a light delivery record is the review. If you have a term of simple checks, the summary writes itself. You are reporting a pattern, not reconstructing a year.
The move is to take the delivery marks you already have and translate them into a few specific sentences per accommodation: what was provided, how consistently, and what you observed about whether it helped.
Accommodation: Extended time (1.5x) on tests and quizzes over 15 minutes, taken in the resource room when Priya requests it.
What the term's record shows:
- 7 qualifying tests this term.
- Extension offered on all 7; Priya used it on 5 and declined it on 2 shorter quizzes.
- On the 5 she used, she completed the test; on a comparable timed task in class where the extension was not set up, she left the last section blank.
The three review sentences, built from that record:
"Extended time was offered on all 7 qualifying assessments this term. Priya used it on 5 and finished each of those, while declining it on 2 shorter quizzes. On one in-class timed task without the extension she left a section incomplete, which suggests the accommodation is still doing real work and should continue."
That is specific, traceable, and honest. Every claim points back to a mark in the record. Compare it to the vague version a team writes from an empty grid: "Extended time was provided as needed and appears to be helping." No one can check that, and no one should trust it.
The good summary names what was offered, how often it was used, and one concrete observation about effect. If you have those three facts from your record, you have your sentences. If you do not, the gap is in tracking, not in writing, and that is the part to fix for next year.
Putting it together
Accommodation tracking does not require a new system on top of your week. It requires reading the grid until each entry is specific, marking the handful of accommodations that need active delivery at the moment they happen, and glancing at the record once a week so gaps surface while you can still close them.
If you are starting from a caseload of plans that were never tracked this way, do not try to fix all of them at once. Pick one student, rewrite their grid into specific wording, sort it into setup and action accommodations, and keep the action ones for a month. A tracking habit you actually keep on one plan is worth more than a perfect system you keep on none. The companion guides go deeper on the accommodation-versus-modification line, on documenting effectiveness ethically, and on assembling the evidence for the meeting.
Common questions
Who is responsible for tracking accommodation delivery?
Every adult who is supposed to provide an accommodation is responsible for delivering it, and the case manager usually coordinates the record. The common failure is that the gen-ed teacher assumes the case manager tracks it, the case manager assumes the teacher does, and no one keeps a record. Decide out loud who logs what. This varies by state and district, so check your local rules, but a clear assignment beats a shared assumption every time.
Do I have to log every accommodation every day?
No. Separate the accommodations that happen by setup, like preferential seating, from the ones that need an adult action each time, like reading directions aloud or providing a separate testing room. Setup accommodations need a record that the arrangement is in place, not a daily mark. The action accommodations are the ones worth a quick delivery check, and only on the days the relevant task actually occurs.
What do I do if a student refuses an accommodation?
Note it. A refusal is delivery evidence too: you offered the accommodation and the student declined it on that date. Record that you offered it, that it was available, and that the student chose not to use it. Patterns of refusal are useful information for the team, because an accommodation a student consistently refuses may need to change. Never quietly drop an accommodation because a student waved it off once.
How does tracking differ for a 504 plan versus an IEP?
The tracking habit is the same: read the wording, deliver it, keep a light record. The plans differ in structure. An IEP carries measurable goals and progress monitoring alongside accommodations, so accommodation evidence sits next to goal data. A 504 plan is usually accommodations without goals, so the accommodation record is often the main evidence the plan is being followed. Either way, schools remain responsible for their own legal and procedural obligations, so check your local rules.