How to Document Response to Intervention (RTI) and MTSS Frameworks

Why RTI and MTSS Documentation Is Different From Other School Records

Most educators think of documentation as something that happens after the work is done. Lesson plans, grade books, behavior incident reports. You do the thing, then you write about it.

Response to Intervention (RTI) and its broader cousin, Multi-Tiered System of Supports (MTSS), invert that assumption. Documentation is not a record of what happened; it is the evidence base that drives every decision in the system. Without the right documentation at each tier, the system has no foundation. Data teams cannot make tier-movement decisions. Parents cannot understand what is happening with their child. Special education eligibility evaluators cannot determine whether a student had adequate opportunity to respond to intervention. And in due process, the district cannot demonstrate it fulfilled its Child Find obligations.

This guide walks through what documentation is required at each tier, how to structure it, what auditors and hearing officers look for, and how to avoid the documentation gaps that most commonly trip up schools.

The Logic of a Tiered Documentation System

Before getting into the specifics of each tier, it helps to understand what the documentation architecture is supposed to accomplish.

RTI and MTSS are prevention and intervention frameworks. They organize support along a continuum, from universal instruction for all students, to targeted small-group intervention, to intensive individualized support. The tiers are not permanent categories; they are decision points. A student moves between tiers based on how they are responding to instruction.

That means documentation at every level needs to answer a specific question:

• Tier 1: Is core instruction working for the majority of students, and which students are not meeting benchmarks?
• Tier 2: Is this student responding to targeted supplemental intervention?
• Tier 3: Is this student's need too intensive for supplemental intervention, and what does that imply about next steps?

Every document in the RTI system is ultimately in service of those three questions. When documentation is incomplete or inconsistent, the answers are ambiguous, and ambiguous answers create both educational and legal problems.

Tier 1: Universal Screening Documentation

Universal screening is the starting point. Two to three times per year, all students are assessed on measures that predict academic or behavioral success. The most common screening tools in use today are curriculum-based measures (CBM) for reading and math, social-emotional learning screeners for behavioral MTSS, and state-adopted benchmark assessments.

What Tier 1 Documentation Must Include

Universal screening documentation is largely a data-management task, but the records must be complete and organized in a way that supports decision-making. Every screening cycle should produce:

• The name of the screening tool used and the version (norms change; the tool version matters for interpretation)
• The date the screening was administered
• The benchmark cut scores used for that season (fall, winter, spring benchmarks differ)
• Each student's raw score and performance level (typically: benchmark, some risk, at risk)
• The name of the person who administered and scored the assessment
• A record of how the data were reviewed, whether in a grade-level data team meeting, a building leadership meeting, or another structured review

A brief example: Madison Elementary administers the DIBELS 8th Edition in the fall of second grade. The school's reading coach, Carlos Peña, documents that 76 of 98 students (78%) scored at or above the fall benchmark for Oral Reading Fluency. The 22 students scoring below benchmark are flagged for data team review to determine whether they need Tier 2 support, additional diagnostic assessment, or both.

That record does several things at once. It shows that core instruction is working for most students (an 80% benchmark rate is the common threshold for a healthy Tier 1). It identifies the students who need more. And it documents who made those determinations and when.

Class-Wide and Grade-Level Data

A common Tier 1 documentation gap is recording only individual student scores without capturing class-wide or grade-level patterns. When a particular classroom consistently has a high percentage of students below benchmark, that is a Tier 1 instructional fidelity concern, not a student-specific concern. The documentation should capture that analysis so it is not lost between screening cycles.

Tier 2: Targeted Intervention Logs

When a student is identified as needing more support than core instruction provides, Tier 2 begins. Tier 2 interventions are typically delivered in small groups (3 to 8 students) with a standard protocol, such as a structured reading intervention program or a social skills curriculum. They supplement but do not replace Tier 1 instruction.

Components of a Complete Tier 2 Intervention Log

Each student receiving Tier 2 support needs an intervention log that documents the following:

Intervention identification: Name of the intervention program, the specific protocol being followed (lesson numbers, skill sequence), and the delivery format (small group size, duration per session, frequency per week).

Baseline data: The assessment data that triggered Tier 2 placement, including the score, the benchmark cut score, and the date.

Intervention start date: When the student first received the intervention, not when the decision was made. These are often different dates, and the gap between identification and service delivery is a frequent audit finding.

Session logs: For each intervention session, the log should capture the date, who delivered the intervention, which lesson or skill was addressed, attendance (the student was present or absent, and if absent, whether a make-up session occurred), and any relevant observational notes about the student's engagement or performance.

Progress monitoring schedule: Tier 2 requires more frequent progress monitoring than Tier 1 screening. The standard expectation is bi-weekly progress monitoring using a curriculum-based measure (CBM) that is sensitive to small increments of growth. The documentation should record the tool, the date of each probe, the score, and the goal line.

A Concrete Example

Imagine a third-grade student named Jordan Ellis, identified in the fall screening as reading at the 12th percentile on ORF, well below the fall benchmark. The intervention coordinator documents the following:

Intervention: Wilson Reading System, small group of 4 students. Duration: 30 minutes, 4 days per week. Baseline ORF: 42 words correct per minute (WCPM), fall benchmark: 80 WCPM. Intervention start date: October 3. Progress monitoring: administered weekly using DIBELS ORF progress monitoring passages. Goal: reach 65 WCPM by the winter benchmark assessment (12 weeks).

Each session log entry for Jordan records the date, lesson completed, attendance, and a brief observational note. By week 8, Jordan's progress monitoring data show a slope of 1.2 WCPM per week, which exceeds the expected growth rate. The data team documents this at their next meeting and discusses whether Jordan is on track to meet the goal or needs adjustment.

That documentation trail tells an evaluator, a parent, or an auditor: the right student was identified, the right intervention was implemented with fidelity, and the student's response is being tracked with valid data.

What Tier 2 Logs Often Miss

The most common gap in Tier 2 documentation is inconsistent session logging. When every third or fourth session goes unrecorded, it is impossible to evaluate attendance, dosage, or delivery fidelity. A progress monitoring graph with a trend line is only meaningful if the intervention was actually happening with the frequency the graph assumes.

The second most common gap is failing to document what happened when a student was absent. If Jordan misses 10 of 40 planned sessions and that is not noted, the data look like they reflect 40 sessions of intervention when they only reflect 30. That matters both for interpreting the data and for determining whether the student received adequate dosage.

Tier 3: Intensive Intervention Tracking

Tier 3 intervention is the most intensive level of support within the RTI/MTSS framework. It typically involves individualized intervention (rather than a standard protocol group), increased frequency and duration, and more intensive progress monitoring. Tier 3 is not the same as special education, but it is often the step that precedes a referral for special education evaluation.

What Makes Tier 3 Documentation Different

The key difference between Tier 2 and Tier 3 documentation is individualization. Where Tier 2 uses a standard protocol with a small group, Tier 3 requires documentation that shows how the intervention has been individualized for this student's specific profile of need.

A Tier 3 record should include everything in a Tier 2 record, plus:

• A diagnostic assessment summary: What assessments, beyond universal screening, were used to understand the student's specific skill deficits? This might include diagnostic reading assessments, phonological processing measures, curriculum-based evaluations, behavioral rating scales, or functional behavioral assessments.
• An individualized intervention plan: The specific skill targets, the instructional approach, and the rationale connecting the diagnostic data to the intervention design.
• Progress monitoring that is more frequent than Tier 2: Weekly or twice-weekly probes are typical, with graphed data reviewed regularly.
• Documentation of problem-solving team meetings: Who met, what data were reviewed, what decisions were made, and what was changed.
• Documentation of previous tier supports: A Tier 3 record should include or reference the Tier 2 history. A student arriving at Tier 3 should have a visible documentation trail showing what was tried before and how they responded.

A Concrete Example

Consider a fifth-grade student, Maya Ortega, who has been in Tier 2 reading intervention for 16 weeks and whose progress monitoring data show a slope of 0.3 WCPM per week against an expected slope of 1.5 WCPM. The problem-solving team meets and reviews the data. They document the following:

Meeting date, attendees (classroom teacher, reading specialist, school psychologist, assistant principal), and data reviewed. Decision: Insufficient response to Tier 2. Plan: Move Maya to Tier 3. Diagnostic reading evaluation administered to understand phonological processing profile (results: significant deficits in phonemic awareness and phonological memory, average decoding of decodable words but near-zero performance on multisyllabic words). Individualized intervention plan developed targeting multisyllabic word reading with an Orton-Gillingham-based approach, 45 minutes daily, delivered 1:1 by the reading specialist. Progress monitoring: weekly ORF probes, monthly phoneme segmentation fluency.

That record shows that the team followed the data, understood why Tier 2 did not work, and designed something more targeted. If Maya is later referred for a special education evaluation, that record is the foundation of the evaluation.

Progress Monitoring Data Collection and Graphing

Progress monitoring data is only useful when it is consistently collected and visually represented in a way that supports decision-making. Data-based decision making (DBDM) is the core methodology of RTI, and the graph is the primary decision tool.

What a Valid Progress Monitoring Graph Needs

• A clear x-axis (dates of each probe) and y-axis (the metric being measured, such as WCPM or number of correctly computed digits)
• A goal line connecting the baseline data point to the end-of-intervention goal
• A trend line (or aimline analysis) showing the student's actual rate of growth
• Data points plotted consistently: one point per probe administration, with the correct date
• A notation for any changes in intervention (if the intervention was modified at week 8, that change should be marked on the graph)
• A notation for any probe sessions that were missed and why

Without these elements, the graph cannot be read accurately. A trend line based on 4 of 12 planned data points does not tell you the same thing as a trend line based on 12 of 12 data points.

Decision Rules for Tier Movement

Decision rules are the pre-established criteria the team uses to determine whether a student's tier level should change. Documenting the decision rules used is as important as documenting the decision itself. If Maya's team used a three-point rule (three consecutive data points below the goal line trigger a problem-solving review) or a slope comparison (if the student's slope is less than half the expected slope after 8 sessions, review the intervention), that rule should be written down in the record.

Decision rules should be established before the intervention begins, not after the data are reviewed. When rules are applied retroactively, they are less defensible in due process and harder to apply consistently across students.

Parent Notification Documentation

Parent notification is not optional in RTI and MTSS. While the specific notification requirements vary by state, the general obligation under the Individuals with Disabilities Education Act (IDEA) and its accompanying guidance is that parents must be notified when their student is receiving intervention beyond core instruction.

What to Document in Parent Notifications

For each parent communication related to RTI or MTSS, the record should include:

• Date of the communication
• Method (meeting, phone call, written letter, email, or a combination)
• Who participated in the communication from the school side
• What information was shared: the data that triggered the intervention, the name and description of the intervention being provided, the frequency and duration of the intervention, and how progress will be monitored
• Parent response: did the parent have questions, express concerns, give consent where consent is required, or decline to engage?
• Whether interpreters were needed and whether interpretation services were provided

A brief example: On October 10, reading specialist Elena Watts called Jordan Ellis's mother, Priya, to inform her that Jordan had been identified through fall screening as needing additional reading support. Elena documented the call in Jordan's RTI folder: date, duration (12 minutes), what she explained (fall ORF score, benchmark comparison, description of the Wilson Reading group), Priya's response (agreed to the intervention, asked whether Jordan would still receive his regular reading instruction, confirmed he would), and the plan to share progress monitoring data at the winter parent-teacher conference.

That record demonstrates that the parent was informed, that the communication was substantive, and that the family had the opportunity to ask questions.

Parent Notification When RTI Feeds Into Special Education Referral

If RTI data will be used as part of a special education eligibility evaluation, the parent notification requirements become more formal. This is the point where prior written notice and, in many states, written parental consent for evaluation become mandatory. The RTI documentation trail must be able to show that parent notification was timely, that the family was informed at each tier transition, and that the communication was accessible (language-appropriate, jargon-free, and documented).

How RTI Documentation Feeds Into Special Education Eligibility

This is where the documentation stakes are highest. When a student is referred for special education evaluation and RTI data are part of the evaluation, the quality of that documentation directly affects the eligibility determination and, if challenged, the outcome of a due process hearing.

What Evaluators Need From the RTI Record

A school psychologist conducting a special education eligibility evaluation under an IDEA framework needs the RTI record to demonstrate:

1. That the student received adequate instruction in the general education setting. Documentation of Tier 1 fidelity, including evidence that the student's classroom used a research-based curriculum and that instruction was delivered with fidelity, addresses this.

2. That the student had repeated opportunities to respond to intervention. Multiple tiers of documented intervention with adequate dosage (sessions delivered as planned, not just scheduled) and sufficient duration (most guidance suggests at least 8 to 12 weeks per tier, ideally longer) demonstrate this.

3. That interventions were implemented with fidelity. Fidelity documentation (observation records, implementation checklists, or notes confirming the intervention protocol was followed) is distinct from session logs but equally important.

4. That the student's lack of adequate response is documented through valid data. Progress monitoring data that are valid (correct tool, correct frequency, correct administration), graphed, and reviewed by a team meets this standard.

5. That the team used data-based decision making. Meeting notes that show the team reviewed data, applied decision rules, and made decisions grounded in the data rather than intuition support this element.

What Auditors and Due Process Hearings Look For

Auditors reviewing RTI implementation and hearing officers in due process proceedings look for specific documentation failures. The most common findings include:

• Gaps between identification and intervention start (a student was flagged in October but intervention did not begin until January)
• Insufficient intervention dosage (too few sessions per week, or sessions too short to match the research base for the intervention)
• Progress monitoring data that are sparse, inconsistently dated, or not graphed
• Tier movement decisions that are not supported by data or that lack meeting documentation
• Parent notification that was absent, late, or not documented
• No evidence of instructional fidelity monitoring
• RTI records that are incomplete or exist only for students who later received special education, rather than for all students who received intervention

Every one of those findings is a documentation problem, not necessarily a service delivery problem. Schools often provide solid intervention and fail at the documentation. In due process, the documentation is the intervention from the hearing officer's perspective.

Common RTI and MTSS Documentation Mistakes

Starting the Clock Late

The date intervention begins matters. When a student is identified in fall screening and intervention does not begin for six weeks, that gap raises questions about whether Child Find obligations were met promptly. Document not just when the intervention started but what happened between identification and service: data team review date, intervention assignment date, group formation date.

Treating Progress Monitoring as Optional

Progress monitoring is not a nice-to-have. Without it, you cannot evaluate whether the intervention is working. A student can attend every session of an intervention that is not helping them, and without progress monitoring data, no one will know until the next universal screening cycle, 3 to 4 months later.

Keeping Records in Too Many Places

RTI documentation that lives partly in a teacher's binder, partly in a shared drive, partly in the student information system, and partly in the school psychologist's files creates a fragmented record that is nearly impossible to reconstruct for an audit or evaluation. Schools that maintain a single complete student RTI folder (physical or digital) are far better positioned.

Writing Session Notes That Are Too Vague to Be Useful

"Intervention delivered" is not a session log entry. A useful session log entry names the specific lesson or skill practiced, notes the student's attendance and engagement, and captures any deviation from the planned protocol. This level of specificity takes an extra 90 seconds per session and makes a significant difference in what the record can demonstrate.

Missing Tier 1 Data at the Class Level

A student's Tier 2 or Tier 3 record should include evidence that Tier 1 was working for the majority of the class. If a classroom had 80% of students below benchmark, that is a Tier 1 problem, and moving students to Tier 2 without addressing Tier 1 puts those students at risk while the systemic problem goes unaddressed. Documenting class-level screening data alongside individual student records makes this visible.

A Note on Tools

Schools managing large numbers of RTI cases across multiple tiers often find that the documentation load is significant, particularly for intervention coordinators and school psychologists tracking dozens of students simultaneously.

If your school uses structured documentation templates, whether in a purpose-built platform or in tools you have customized for RTI, the structure itself removes a significant amount of the cognitive load from the person completing the record. NotuDocs supports custom documentation templates that teams can configure to match their specific progress monitoring formats, session log requirements, and tier-movement decision documentation, so that practitioners are filling in data rather than rebuilding the structure from scratch each time.

RTI and MTSS Documentation Checklist

Use this at each stage of the process to verify your records are complete.

Tier 1: Universal Screening

• Screening tool name, version, and administration date recorded
• Benchmark cut scores for the current season documented
• Individual student scores and performance levels recorded
• Assessor name recorded
• Class-level and grade-level benchmark rates documented
• Data team review meeting notes completed (date, attendees, decisions)
• Students identified for Tier 2 consideration listed with follow-up plan

Tier 2: Targeted Intervention

• Intervention name and protocol documented (specific lesson sequence or program)
• Group composition and delivery format documented (group size, frequency, duration)
• Baseline data recorded (score, date, benchmark comparison)
• Intervention start date recorded
• Session logs completed for every session (date, lesson, attendance, observations)
• Absences documented with make-up session information where applicable
• Progress monitoring tool, frequency, and goal recorded
• Progress monitoring data graphed with goal line and trend line
• Decision rules documented
• Parent notification documented (date, method, content, parent response)
• Data team review meeting notes completed at each decision point

Tier 3: Intensive Intervention

• Diagnostic assessment results documented (tools, scores, interpretation)
• Individualized intervention plan documented: targets, approach, rationale
• Previous tier documentation referenced or included
• Progress monitoring at higher frequency than Tier 2
• Problem-solving team meeting notes completed (attendees, data reviewed, decisions)
• Fidelity monitoring documentation included (observations or implementation checklists)
• Parent notification at each tier transition documented
• Referral documentation if student is referred for special education evaluation

Parent Notification

• Date and method of each communication recorded
• School participants identified
• Content of communication documented (data shared, intervention described)
• Parent response documented
• Interpretation services documented if needed
• Prior written notice completed if referral for special education evaluation follows

Special Education Referral Connection

• Tier 1 adequacy evidence available (curriculum, fidelity data, class-level benchmark rates)
• Intervention dosage adequate and documented (sessions delivered vs. planned)
• Progress monitoring data complete, valid, and graphed
• Decision rule application documented
• Timely parent notification across all tiers documented
• Complete RTI record consolidated and accessible for evaluation team

RTI and MTSS documentation is demanding, but the demands are proportionate to what is at stake. The documentation is the record of whether the system worked for a child. When it is complete, coherent, and specific, it protects the school, informs the team, and demonstrates that every student who needed support got it.

---

Related Guides

• How to Document IEP Meetings and Annual Reviews
• How to Document Functional Behavioral Assessments and Behavior Intervention Plans
• Case Management Documentation Best Practices