PBIS Tier 2 and Tier 3 Intervention Tracking Log
Track PBIS Tier 2 and Tier 3 interventions, progress monitoring, and team review decisions in one student-level log. Use it to document what was assigned, how often it is checked, and what the team decided next.
Trusted by frontline teams 15 years of frontline software
Built for: K 12 Education · Special Education · Student Support Services · School Counseling
Overview
The PBIS Tier 2 and Tier 3 Intervention Tracking Log is a student-level form for documenting targeted and intensive behavior supports. It captures the submission notice, student and team details, the intervention assigned, the progress monitoring plan, and the review decision so the team can see what was done, when it started, and what happened next.
Use this template when a student has moved beyond universal supports and needs a documented intervention plan with regular review. It works well for check-in/check-out, mentoring, behavior contracts, individualized reinforcement plans, and other supports that require baseline data, monitoring frequency, and a clear decision trail. The form is especially useful when multiple staff members share responsibility and need a single record of assignment, implementation, and follow-up.
Do not use this template as a general discipline referral, a one-time incident note, or a broad student profile. It is not meant to collect unnecessary PII or open-ended narrative that does not affect the intervention. If your school does not yet have a defined PBIS process, this log may be too detailed for early-stage behavior tracking. It is most effective when the team already knows who owns the intervention, what measure will be used, and when the next review will occur.
Standards & compliance context
- Limit student data to the minimum necessary under data minimization principles and avoid collecting fields that are not needed for the intervention.
- If the form is public-facing or accessible to families, ensure WCAG 2.1 AA-friendly labels, validation, and keyboard navigation for all fields.
- If the log includes any sensitive student or family information, include a clear consent or data-use acknowledgment before submission.
- Use an audit trail for review decisions so the team can show when the intervention changed, who approved it, and why.
- If the form is used in special education or accommodation workflows, keep prompts aligned with reasonable-accommodation needs and avoid unnecessary medical detail.
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 expectations for what information is collected, why it is collected, and how the record will be used.
- Data use notice
- I understand this form may contain student PII and will be used for intervention tracking and team review.
Student and Team Information
This section identifies the student, the responsible staff, and the date so the intervention record is traceable.
-
Student ID
Enter the district or school student identifier. Avoid entering SSNs or other unnecessary identifiers.
- Student name
- Grade level
- Submitting team member
- Team role
- Submission date
Intervention Assignment
This section defines the support that was assigned and the context needed to implement it correctly.
- Intervention tier
- Reason for intervention assignment
-
Intervention name
Enter the specific intervention or support being provided.
- Start date
- Planned end date
- Service delivery setting
Progress Monitoring Plan
This section explains how the team will measure response to the intervention and what success should look like.
- Progress monitoring measure
- Monitoring frequency
-
Baseline level
Enter the starting value for the selected measure, if available.
-
Goal level
Enter the target value for the selected measure, if applicable.
-
Monitoring notes
Briefly describe how data will be collected and who is responsible.
Review Decisions and Follow-Up
This section captures the team’s decision, the fidelity check, and the next action so the intervention does not stall.
- Review date
- Implementation fidelity
- Team decision
-
Decision summary
Summarize the data reviewed, the decision made, and any changes to the intervention plan.
- Next review date
How to use this template
- 1. Enter the submission notice and data-use language first so the record clearly states what information is being collected and how it will be used.
- 2. Fill in the student and team information fields with the minimum necessary identifiers, the responsible staff member, and the date the log is created.
- 3. Record the intervention assignment by selecting the tier, naming the intervention, stating the referral reason, and specifying the start and end dates plus the service setting.
- 4. Define the progress monitoring plan by choosing the measure, setting the monitoring frequency, entering the baseline and goal levels, and adding any notes needed for consistent data collection.
- 5. Complete the review section after each team meeting by documenting fidelity, the decision made, the summary of next steps, and the next review date.
- 6. Close the loop by assigning follow-up actions to a named staff member so the intervention does not stall between review cycles.
Best practices
- Use the referral_reason field to describe observable behavior patterns, not labels or assumptions.
- Match the monitoring_measure to the behavior being targeted so the data can actually guide the team decision.
- Keep the intervention_name specific enough that another staff member could implement the same support without guessing.
- Set the monitoring_frequency before the intervention starts so data collection is routine, not retroactive.
- Document implementation_fidelity at every review so the team can tell whether the plan was delivered as intended.
- Use progressive disclosure in the form design so staff only see fields relevant to the selected tier or intervention type.
- Keep student identifiers to the minimum necessary and avoid collecting extra PII that does not affect the intervention.
- Write the decision_summary as an action record, including who will do what before the next review date.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this PBIS intervention tracking log used for?
This template documents when a student is assigned to a PBIS Tier 2 or Tier 3 intervention, what support was selected, and how progress is reviewed over time. It gives the team a single place to record baseline data, monitoring frequency, fidelity, and follow-up decisions. Use it when a student needs targeted or intensive behavior support beyond universal Tier 1 practices.
Who should complete the log?
A PBIS team member, case manager, counselor, behavior specialist, or designated intervention lead usually completes it. The person entering the log should know the intervention plan and have access to the monitoring data and review notes. If multiple staff contribute, one owner should be responsible for keeping the record current and consistent.
How often should the log be updated?
Update it when the intervention is assigned, whenever progress monitoring data is collected, and at each team review meeting. The monitoring_frequency field should match the actual cadence used for the student, such as weekly or biweekly. Do not wait until the end of the intervention to backfill the record, because that makes review decisions harder to trust.
What kind of student information should be included?
Include only the student identifiers and context needed to run the intervention and review the case. Use the minimum necessary PII, and avoid collecting extra details that do not affect the support plan. If your workflow allows it, keep the submission notice clear about data use and whether the record is part of an audit trail.
How does this relate to Tier 2 versus Tier 3 supports?
Tier 2 entries usually track targeted supports for students who need more than universal supports but less than individualized intensive planning. Tier 3 entries are for students needing more individualized, high-intensity intervention and closer review. The template works for both, but the referral_reason, monitoring plan, and team_decision fields should reflect the different level of support.
What are common mistakes when using this template?
Common issues include vague referral reasons, missing baseline data, and monitoring measures that do not match the behavior being tracked. Another frequent problem is recording the intervention name without stating the setting, frequency, or who is responsible for delivery. Teams also sometimes skip fidelity review, which makes it hard to know whether the intervention failed or was not implemented as planned.
Can this log be customized for different schools or programs?
Yes. Schools can rename intervention tiers, add local behavior supports, or adjust review cadence to match their PBIS process. You can also add conditional logic for different intervention types, such as check-in/check-out, mentoring, or individualized behavior plans, while keeping the core fields intact.
How does this fit with other student systems or integrations?
This log can be used alongside SIS, MTSS, or behavior tracking systems as the review record for intervention decisions. Many teams use it to summarize data pulled from other tools rather than replacing those systems. If you integrate it with other records, keep the field mapping simple so student ID, dates, and review outcomes stay aligned.
What should happen after a submission is made?
The team should confirm the intervention assignment, verify the monitoring plan, and schedule the next review date. If the submission includes consent or data-use acknowledgment, that should be recorded before the intervention begins. The log should make it clear who will follow up, what will be measured, and when the next decision point occurs.
Related templates
Go deeper on the topic
-
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 —...
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
Artificial intelligence in the workplace: boost productivity, streamline tasks, and empower employees with smarter, more meaningful work.
-
Discover 7 common intranet platform failures that exclude frontline workers—and the specific capabilities that close the gap for deskless teams.
Ready to use this template?
Get started with MangoApps and use PBIS Tier 2 and Tier 3 Intervention Tracking Log with your team — pricing built for small business.
