Skip to Content

RTI Alerts Inbox & Tier Review

The RTI alerts inbox (WP-RTI-FE) is where you review open signals about your students and, when the evidence is ready, request a formal tier-review. Every decision remains yours — the system proposes and you decide.

The alerts inbox

Your inbox lists three kinds of open alerts:

Alert kindWhat it means
Skill Alert (مهارة تستدعي الانتباه)One skill is flagging as weak — a nudge to watch this skill. No plan change is implied.
Student Alert (طالب في حاجة لخطّة دعم)Cross-skill breadth suggests this student needs a Targeted Support Plan. This is the gateway to Tier 2.
Intensive Review (مراجعة مكثّفة)Breadth across multiple domains, or an acute-regression signal, suggests a more intensive review. This is the gateway to Tier 3 candidacy.

Only the highest-severity open alert per student shows at any time. When a Student Alert upgrades to Intensive Review, the lower alert closes automatically.

No data yet? When a student’s skill carries the “need more evidence” status (لا توجد بيانات كافية لاتخاذ قرار موثوق), no alert opens. A low-priority hint appears on the student card reminding you to collect more data at the next session. This hint is not a red alert badge — it is informational.

What you see per alert

  • The alert kind and the skills that contributed.
  • The student’s current RTI tier (Core / Targeted / Intensive).
  • A “Modify the plan” action — always the primary option before any tier-review path (V-12, the teacher-decides rule).
  • A “Request tier review” action — only shown when sufficient evidence and fidelity are present.

Acute-regression alerts

When progress drops ≥20% across 2 comparable sessions (GSR-02), an Intensive Review alert opens. This is a review signal, never an automatic plan change. To dismiss it, you must choose a reason from a closed list of 8 override reason codes from the controlled vocabulary, for example Override_Contextual_01 (contextual circumstance) or Override_DataGap_04 (insufficient data). There is no free-text dismissal field.

The 3-step tier-review

When evidence is ready and you want to move a student to a heavier or lighter tier, you request a formal review. The flow is 3 steps:

  1. Request — choose a review type (escalation / de-escalation / maintenance) and a reason code from the controlled vocabulary. Amal pre-fills available evidence from the Data Room.
  2. Packet review — the assembled decision packet shows what evidence is available, whether fidelity was adequate, and what the engine recommends (review / maintain / defer). You cannot edit the packet — you approve or defer.
  3. Approval — for any tier change, a specialist (or an admin with specialist permissions in Wave 1) must approve. You see a “waiting for specialist approval” status while it is pending.

Fidelity gate. If a plan’s delivery was low (under 80%) OR the plan went off-track (no sessions delivered for several consecutive instructional weeks), escalation AND de-escalation are both blocked until the plan is back on track. You will see: “أكملي الجرعة المخططة قبل تقييم التدخّل.” The numeric results may still be shown as a performance record, but they cannot drive a tier move.

RTI tiers cannot be changed directly. There is no button that sets a tier. The only path is through a completed, approved tier-review request. This is by design — it protects against mistaking delivery gaps for plan failure.

Getting Started