Key takeaways
- Name the exact intervention, its schedule, and its start date, never just a tier number.
- Set the decision rule and review date before the intervention starts.
- Collect progress data on a fixed schedule so tier decisions rest on a trend.
- Record each tier decision next to the data and the reason.
- The same documented trail supports a referral if a student does not respond.
MTSS tier documentation records, for each student receiving support, which intervention they get, how often, how they respond, and why the team kept, changed, or ended it. The checklist below lists what to document at each tier with a done-when standard, so a tier decision or a referral conversation rests on a written trail rather than memory. Your district and state MTSS procedures remain the source of truth for timelines and required forms.
Tier 1: universal support
| Item | Done when |
|---|---|
| Screening results | The screener name, date, and the student's result are recorded |
| Classroom supports in place | The class-wide expectations and routines taught are written down with dates |
| Concern described | The teacher's concern is written in observable terms, with a few dated examples |
| Classroom data collected | At least two to three weeks of simple data on the concern, such as a daily rating or work samples |
Tier 2: targeted intervention
| Item | Done when |
|---|---|
| Intervention named | The specific program or routine is recorded, such as "Check-In Check-Out" or "small-group phonics, 3 students," not "Tier 2 support" |
| Schedule set | Frequency, session length, group size, start date, and who delivers it are written down |
| Baseline recorded | Three to five data points on the target skill or behavior before the intervention starts |
| Goal and decision rule set | A target and a rule, such as "four consecutive weekly points below the goal line triggers a team review" |
| Progress data on schedule | Data is collected at the planned frequency, usually weekly, with gaps noted and explained |
| Delivery tracked | Sessions delivered versus planned are recorded, so a flat trend can be read correctly |
| Family notified | The date and method the family was told about the intervention are logged |
| Review date set | A team review is on the calendar before the intervention starts |
Tier 3: intensive, individualized support
| Item | Done when |
|---|---|
| Tier 2 record attached | The Tier 2 intervention, delivery, and data that led to the change are linked to the Tier 3 plan |
| Individualized plan written | The plan names what changed from Tier 2: more time, smaller group, different approach, or a behavior plan |
| Behavior function examined | For behavior concerns, an FBA or structured ABC data collection is documented |
| Data collected more often | Progress data is collected at least weekly, and often more, on a named measurement type |
| Team and roles recorded | Who delivers, who collects data, and who reviews are named |
| Review cadence set | Reviews are scheduled more often than at Tier 2 |
Every tier change
| Item | Done when |
|---|---|
| Criteria were set in advance | The decision rule used was written before the data came in |
| Decision recorded with evidence | The decision (intensify, continue, fade, or end), the date, the data summary, and the reason are recorded together |
| Delivery considered | The record says whether the intervention was delivered as planned before concluding it did not work |
| Family informed | The family was told about the change, and the contact is logged |
Student: composite fourth grader, Check-In Check-Out for task completion, started Sept 15, daily ratings by homeroom teacher.
Baseline: 45 percent of daily points. Goal: 80 percent. Decision rule: four consecutive weekly averages below the goal line triggers review.
Weekly averages, weeks 1 to 6: 50, 58, 62, 71, 76, 79. Sessions delivered: 29 of 30.
Decision, Oct 27: continue for four more weeks, then begin fading the afternoon check-out if weekly averages stay at or above 80 percent. Reason: steady upward trend under consistent delivery, approaching the goal.
When a student is not responding
If a student does not respond to well-delivered interventions across tiers, the same trail supports a referral or evaluation conversation: what was tried, for how long, how consistently, and how the student responded. Bring the intervention records, the progress data with the decision rules, delivery records, and family contact history. Because it was documented as it happened, the team is not rebuilding months of support from memory.
For choosing the measure at Tier 2 and 3, choosing the right measurement type matches common goals to the free IEP data sheets. For behavior at Tier 3, the practical guide to running an FBA covers the assessment. The blog's MTSS and RTI documentation guide and Check-In Check-Out guide go deeper on Tier 2 routines, and setting up a school-wide documentation system covers getting every classroom to record Tier 1 data the same way.
Common questions
What documentation is needed for Tier 2?
The intervention name, start date, schedule (how often, how long, group size), who delivers it, a baseline, progress data on a fixed schedule, fidelity notes, the decision rule, the review date, and family notification. Record the decision at each review next to the data.
How long should a student stay in a tier before a change?
Long enough to read a trend under reliable delivery, often six to eight weeks for a Tier 2 intervention with weekly data. Your district's MTSS procedures set the actual timelines, so check them before setting review dates.
What data justifies moving a student to Tier 3?
A documented Tier 2 intervention delivered as planned, a baseline, several weeks of progress data below the goal line under the decision rule you set in advance, and a team decision recorded with the reason.
Can MTSS documentation support a special education referral?
Yes. A clear record of interventions tried, how consistently they were delivered, and the student's response is often part of the information an evaluation team reviews. District and state procedures define what is required.