The annual review is where a year of accommodation tracking either pays off or exposes the gap. If you kept a light record across the term, the meeting is a matter of summarizing what you already have. If you did not, it is a scramble to remember a year you cannot actually recall. This guide is the assembly step: the four questions the team will ask, how to turn a term of notes into a short summary per accommodation, and the one-pager that carries it all into the room.
The four questions the team will ask
Every accommodation on the plan gets reviewed against the same four questions. If you walk in with an answer to each, the conversation is grounded in evidence rather than impression.
The first question is: was it delivered. This is the delivery answer. On the occasions it applied, was the accommodation actually provided. Your delivery record answers this directly.
The second is: did it help. This is the effectiveness answer. When the support was in place, did the student do better than when it happened not to be available. Your ratings and any naturally occurring with-and-without observations answer this.
The third is: is it still needed. Sometimes a student has grown into the skill the accommodation was scaffolding, and the data shows the gap has closed. Sometimes the need is as strong as ever. This question is where the team decides whether to keep, adjust, or fade.
The fourth is: what should change. Based on the first three, what is the recommendation for next year. Continue as written, change the wording, add a piece, or reduce it with a fading plan. This is the action the meeting produces.
These four map cleanly onto the work the rest of the year was building toward. Delivery tracking answers the first, effectiveness ratings answer the second, the pattern in both answers the third, and your recommendation answers the fourth.
The order matters too. You cannot honestly answer "did it help" until you have answered "was it delivered," because an accommodation that was rarely provided cannot be judged ineffective; it was never really tried. And you should not decide "is it still needed" before you have looked at both delivery and effect together. Teams that jump straight to "what should change" without grounding the first three questions end up making next year's plan on a hunch. Walk the four in order and each one feeds the next.
Assembling a per-accommodation summary
You do not write the summary from memory the night before. You build it from the notes you already kept, one accommodation at a time. The work is collation, not recollection.
- Pull the term's records for one accommodation. Gather the delivery marks and any effectiveness ratings for a single accommodation before you touch the next one. One accommodation, one short summary, then move on.
- Count the delivery occasions. How many times did the accommodation apply this term, and on how many was it provided. A simple ratio, like 7 of 7 qualifying tests, is the delivery fact.
- Read the effectiveness pattern. Look at the ratings and any naturally occurring without occasions. Were they mostly high, mostly low, or mixed, and what did the student do when the support was absent. That is the effect fact.
- State the need and the recommendation. From the first three, decide whether the accommodation is still needed and what should change. Keep as is, adjust the wording, or fade with the data behind it.
- Write three or four sentences. Turn the count, the pattern, and the recommendation into a few specific sentences. This becomes the summary you bring to the meeting and the basis for the one-pager.
Doing one accommodation at a time keeps the work small. A student with six accommodations becomes six short collation tasks, each a few minutes, rather than one overwhelming evening.
Start this a week or two before the meeting, not the night before. Spreading six short summaries across a few planning periods is easy; doing all of them at once under deadline is how the work turns into the vague paragraphs you are trying to avoid. If you kept the weekly scan going through the year, the records are already where you need them, and the assembly really is just collation. If a record is thin for one accommodation, this is the moment you find out, while there is still time to say so honestly at the meeting rather than paper over the gap.
What a summary that holds up looks like
The difference between a summary that holds up and one that does not is specificity. A strong summary names numbers and an observation. A vague one names a feeling. Here is the same accommodation written both ways, annotated.
A composite eighth grader we will call Maya. Accommodation: extended time (1.5x) on tests over 15 minutes.
Vague version: "Extended time was used as needed throughout the year and seemed to help Maya. We recommend continuing it."
Why it is weak: "as needed" hides whether it was actually offered each time. "Seemed to help" is an impression no one can check. There is no count, no comparison, nothing a parent or teacher could trace.
Strong version: "Extended time was offered on all 8 tests it applied to this year. Maya used it on 6 and completed each of those; on the other 2 she chose not to use the extra time and finished within the standard window. On a unit test a substitute proctored without the extension in place, she left two questions unanswered that she had reached on every extended test. The accommodation appears to still be doing real work on longer assessments, and we recommend continuing it as written."
Why it holds: every claim points to a record. The count is there (8 offered, used on 6), the contrast is there (the substitute-proctored test without it), and the recommendation follows from the evidence rather than from habit.
The strong version is not longer because it is padded. It is longer because each sentence carries a fact. If you have the count, the use, and one concrete observation, you have a summary the team can stand behind.
The meeting-day one-pager
You do not bring a binder to the meeting. You bring one page per student that puts every accommodation, its delivery, its effect, and your recommendation in a single view the team can scan in a minute.
| Accommodation | Delivered | Effect | Recommendation |
|---|---|---|---|
| Extended time, 1.5x, on tests over 15 min | Offered 8 of 8 tests; used on 6 | Completed all 6; left a section blank on a timed task without it | Continue as written |
| Directions read aloud, multi-step tasks | Provided on observed multi-step assignments | Mostly partial effect; directions were also long | Adjust: read aloud and chunk the steps |
| Separate testing room on request | Used on 5 test days | Finished without distraction reports each time | Continue as written |
| Preferential seating, front third | In place since September | Steady; no off-task concerns at the new seat | Continue; recheck mid-year |
The one-pager is the summary work made visible. Each row is the three or four sentences you wrote, compressed into a line the whole team can read at once. It keeps the meeting on evidence and makes it easy to see, across all the accommodations at once, which ones are working and which need a change.
Keep the longer summaries behind the one-pager in case a row prompts a question. If a parent asks about the read-aloud row, you can read out the few sentences that back it. But you lead with the table, because the table is what lets the team move through a student's whole set of accommodations in a few minutes instead of getting stuck reciting paragraphs. A meeting that can see all four rows at once tends to make better keep-adjust-fade decisions, because the team is comparing across the accommodations rather than judging each in isolation.
One practical note on the columns: write the recommendation as an action, not a verdict. "Continue as written" tells the team exactly what to put in next year's plan. "Working well" does not, because someone still has to decide what that means for the document. The whole point of the one-pager is to walk out of the meeting with each row resolved into a concrete line for the new plan.
Welcome the parent's questions
A parent who asks hard questions about accommodations is not a problem to manage. They are asking exactly what the team should be asking, and your record is what lets you answer honestly.
The whole point of tracking accommodations through the year is this meeting. Specifics handled at the review, like grading flags, testing decisions, and anything touching diploma track, vary by state and district, and schools remain responsible for their own legal and procedural obligations, so check your local rules and bring the people who own those decisions into the room. What you own is the evidence, and walking in with a clear one-pager per student is what turns the annual review from a defense into a conversation.