A four-stage chain for the meeting where a school team reviews intervention data: a flagged pre-read built from raw numbers, a time-boxed agenda, a decision record with owners and dates, and the collection plan for the next cycle.
The MTSS meeting is Thursday at 7:20, twenty-two students are on the list, and the data lives in four exports nobody has merged. An hour later the team has talked about six students, decided three things, and written down one. This chain covers the cycle around that meeting.
Stage one turns raw exports into a pre-read that groups students by the decision actually due: new to Tier 2, continue, intensify, change, exit, or watch, each with the two or three numbers behind it and a line on what is missing. Stage two builds a time-boxed agenda ordered by urgency rather than alphabetically, with the single question each student's slot has to answer. Stage three converts messy meeting notes into a decision record carrying the data cited, the rule applied, an owner, and a due date, and writes UNCLEAR rather than guessing. Stage four names what to collect before next time.
For MTSS and RTI coordinators, student support team chairs, school counselors, and interventionists. It sorts by data rather than by label, it refuses to write an eligibility conclusion, and it keeps what the team decided separate from what the team merely discussed.
You handle the paperwork around a school data review meeting: you prepare, you structure, and you record. You do not decide. Sort students by the decision that is due, never by a label or a guess at a disability. Where the notes are ambiguous, write UNCLEAR and the question the team has to resolve.
DECISION RECORD, grade 6 MTSS review, 11/13 Student A. Decision: continue check-in check-out, eight more weeks. Data: point card 41 to 63 percent over six weeks, fidelity 92 percent. Rule: district continue rule. Owner: counselor. Review 1/15. Student B. Decision: intensify. Data: completion flat at 52 percent for four weeks, fidelity 71 percent. Rule: none in writing; team proposed fixing fidelity before changing the intervention. Owner: MTSS coach, due 11/22. Review 12/11. Student C. Decision: UNCLEAR. The team discussed a referral question and did not resolve whether the reading data supports Tier 3. Question to resolve: which of the two screener administrations is the valid baseline. Owner: reading specialist, due 11/20. Student D. Decision: exit to Tier 1 with a four-week watch. Data: 84, 81, 88, 86 percent across four weeks. Rule: district exit rule. Owner: classroom teacher, weekly spot check. Review 12/11. DISCUSSED, NOT DECIDED Whether the grade 6 writing block is driving the escape-motivated behavior seen in three students. Placed on the 12/11 agenda. REFERRAL QUESTIONS RAISED One, routed to the process that handles evaluation requests.
Run stage one the day before the meeting, not the morning of. It needs the actual exports: progress monitoring points, attendance percentages, office referral counts, screener scores. Merge them first, or paste them separately and say which is which. If your district has written tier entry and exit rules, paste those too. Without them the chain proposes rules and labels them proposals, which is useful once and awkward twice.
Stage three is the one that earns the price. Paste rough notes during the meeting, even fragments, and run it before people leave the room. Notes reconstructed on Friday lose the numbers anyone cited.
Where it fails: it cannot see a student, it will treat a stale export as current, and it does not know which staff member is permitted to see which record. Check the audience question yourself.
Before the record is filed, confirm every UNCLEAR line has an owner and a date, that no line contains an opinion about eligibility, and that the decisions match what people in the room believe they agreed to.