Loading...
education

MTSS and RTI Intervention Documentation and Progress Monitoring Form

MTSS and RTI Intervention Documentation and Progress Monitoring Form tracks tiered supports, service delivery, and progress data in one place so teams can review what was tried and what happens next.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: K 12 Schools · Charter Schools · Special Education Programs · Educational Service Agencies

Overview

This MTSS and RTI Intervention Documentation and Progress Monitoring Form is for recording a student’s support plan, the schedule used to deliver it, and the data collected to judge whether the intervention is working. It brings together the submission notice, student and team details, intervention plan, delivery schedule, progress monitoring data, and decision-making fields in one record.

Use it when a student is receiving tiered academic or behavior support and the team needs a consistent way to document what was provided, by whom, how often, and with what result. It is especially helpful for review meetings, intervention adjustments, and cases where a school needs a clear audit trail of services and outcomes. The form also supports data minimization by collecting only the student and intervention details needed for the review.

Do not use it as a general student profile, discipline log, or full evaluation packet. If you do not have a measurable intervention, a baseline, and a progress measure, the template will not produce useful decisions. It is also not the right tool for one-time accommodations that do not require progress monitoring. The form works best when the team is ready to compare baseline, current performance, and goal data over time and then document the next step.

Standards & compliance context

  • The submission notice and data use acknowledgement support informed collection of student information and help limit the form to the minimum necessary data.
  • If the form is shared with families or includes student-identifying details, keep consent and disclosure language clear and avoid collecting PII that is not needed for the intervention record.
  • The structure supports an audit trail for MTSS and RTI review decisions by documenting the intervention, monitoring data, rationale, and follow-up date.
  • For accessibility, field labels, validation messages, and progress data displays should meet WCAG 2.1 AA expectations so staff can complete and review the form reliably.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice and Data Use

This section sets the purpose of the record and explains how the information will be used before any student data is entered.

  • Purpose of this submission
  • I understand this form collects student support data for intervention tracking and team review. (required)
  • Consent and disclosure notice

Student and Team Information

This section identifies the student, the responsible staff, and the review date so the record is tied to the correct support team.

  • Student name (required)
  • Student ID

    Optional if your school uses a non-PII internal identifier.

  • Grade level (required)
  • School or program (required)
  • Case manager / intervention lead (required)
  • Next MTSS/RTI team review date

Intervention Plan

This section defines what support is being provided, at what tier, and for how long so the intervention can be evaluated against a clear plan.

  • Primary intervention area (required)
  • If other, describe the intervention area
  • Tier level (required)
  • Intervention name (required)
  • Intervention description (required)

    Describe the instructional strategy, program, or support being delivered.

  • Start date (required)
  • Planned end date

Delivery Schedule and Staffing

This section captures fidelity details such as frequency, duration, group size, setting, and who delivered the intervention.

  • Sessions per week (required)
  • Minutes per session (required)
  • Group size

    Enter 1 for individual intervention.

  • Delivery setting (required)
  • Interventionist role (required)

Progress Monitoring Data

This section records the measurable evidence the team uses to decide whether the intervention is helping the student make progress.

  • Progress monitoring measure (required)
  • Baseline score
  • Current score (required)
  • Goal score
  • Date of most recent progress check (required)
  • Progress trend (required)
  • Progress notes

    Summarize observations, data patterns, and any instructional adjustments made.

Decision Making and Follow-Up

This section turns the data review into an action plan by documenting the decision, rationale, next steps, and follow-up date.

  • Team decision (required)
  • Rationale for decision (required)

    Document the data-based reason for the decision and any conditional logic used by the team.

  • Next steps (required)

    List action items, responsible staff, and the timeline for follow-up.

  • Follow-up date

How to use this template

  1. Enter the submission purpose and confirm the data use acknowledgement so the record clearly states why the form is being completed.
  2. Fill in the student and team information, including the case manager and review date, so the right people can find and act on the record.
  3. Document the intervention plan with the area, tier level, intervention name, description, start date, and planned end date.
  4. Record the delivery schedule and staffing details, including frequency, minutes, group size, setting, and interventionist role, so the team can verify the support was delivered as planned.
  5. Add the progress monitoring measure, baseline, current score, goal score, date, and notes, then select the decision status and next steps for follow-up.
  6. Review the completed form with the team, assign any action items, and schedule the next follow-up date before closing the record.

Best practices

  • Use one progress monitoring measure for a given intervention cycle unless the team documents a deliberate change and resets the baseline.
  • Specify frequency per week, minutes per session, and group size instead of describing the service in vague terms like "regular support."
  • Keep the intervention description concrete enough that another staff member could deliver the same support without guessing.
  • Record the monitoring date each time data is entered so the trend line reflects the actual review cadence.
  • Use conditional logic to show only the fields needed for the selected intervention area and tier level.
  • Mark required fields clearly and leave nonessential fields optional to support data minimization and faster completion.
  • Write the decision rationale in plain language that connects the data trend to the next step, not just a label like "continue."

What this template typically catches

Issues teams running this template most often surface in practice:

Missing baseline data makes it hard to tell whether the intervention improved performance.
Changing the progress measure mid-cycle without noting it breaks comparability across review dates.
Recording the intervention without the delivery schedule leaves the team unable to verify fidelity.
Using a vague intervention description makes it unclear what was actually implemented.
Leaving the decision rationale blank turns the review into a status update instead of a documented decision.
Forgetting the follow-up date causes the intervention to stall without a planned review.
Collecting extra student details that are not needed for the support plan creates unnecessary PII exposure.

Common use cases

Elementary Reading Intervention Team
A reading specialist documents a small-group decoding intervention for a second-grade student, including the weekly schedule, progress measure, and review decision. The team uses the form to decide whether to continue the current tier or adjust the instructional approach.
Middle School Math Support Review
A case manager tracks a student receiving targeted math fluency support and records baseline, current, and goal scores at each review meeting. The form helps the team see whether the intervention is being delivered with enough frequency and intensity.
Behavior Support Coordination
An intervention team documents a behavior support plan with a specific setting, group size, and staff role so the support can be replicated consistently. Progress notes capture attendance, task completion, or other measurable indicators tied to the plan.
Pre-Referral Student Assistance Team
A school uses the template to log interventions before a special education referral, showing what was tried, when it started, and how the student responded. The record creates a clear history for the next team discussion.

Frequently asked questions

What is this MTSS and RTI Intervention Documentation and Progress Monitoring Form used for?

Use it to record a student’s intervention plan, how often support is delivered, who provides it, and the progress monitoring data used to review effectiveness. It gives the team a single record for tiered supports, decision-making, and follow-up. This is especially useful when a student needs documented evidence before a change in tier, strategy, or referral.

Who should complete this form?

It is usually completed by a case manager, interventionist, school psychologist, teacher, or MTSS/RTI team member responsible for the student’s support plan. The person entering the form should have access to the intervention details and the latest progress monitoring results. In many schools, one person enters the data while the team reviews and approves the next steps.

How often should progress monitoring be updated?

Update it on the cadence used by the intervention plan and your school’s MTSS process, such as weekly, biweekly, or at each review meeting. The key is to keep the monitoring frequency consistent so the trend line is meaningful. If the intervention changes, record the new baseline and start a fresh comparison point.

What kinds of interventions fit this template?

It works for academic interventions such as reading fluency, decoding, math computation, written expression, or behavior supports tied to attendance or task completion. The template includes an intervention area field and an optional other area field so you can document both standard and custom supports. If the intervention is not tied to measurable progress data, this form is probably not the right fit.

What should be included in the progress monitoring section?

Record the measure used, the baseline score, the current score, the goal score, the monitoring date, and a short note explaining the trend. Use the same measure over time whenever possible so the data stays comparable. If the score moved but the trend is unclear, note any changes in attendance, staffing, or intervention delivery that may explain it.

How does this form support MTSS and RTI decision-making?

It captures the evidence teams need to decide whether to continue, adjust, intensify, fade, or end an intervention. The decision status, rationale, next steps, and follow-up date make the review actionable instead of leaving it as a discussion only. That helps teams document why a student stayed at the same tier or moved to a different support level.

Can this template be customized for different schools or programs?

Yes. You can rename intervention areas, add school-specific progress measures, or adjust the decision options to match your MTSS workflow. Many teams also add conditional logic so only relevant fields appear for academic, behavior, or attendance interventions. Keep the form focused on the data you actually use so it stays quick to complete.

What are common mistakes when using this form?

Common issues include leaving out the intervention start date, changing the progress measure midstream without noting it, or documenting a goal without a baseline. Another frequent problem is recording the service schedule loosely instead of specifying frequency, minutes, group size, and setting. Those details matter because they show whether the intervention was delivered as planned.

How does this compare with tracking interventions in a spreadsheet or email thread?

A form creates a consistent record with required fields, validation, and a clear review trail, while ad-hoc notes often leave gaps in service delivery or progress data. It also makes it easier to standardize what the team reviews at each meeting. If your team needs one source of truth for intervention history, a template like this is easier to maintain than scattered messages.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use MTSS and RTI Intervention Documentation and Progress Monitoring Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?