---
title: "Logging an Intervention Session"
url: https://docs.growamal.com/en/guides/log-intervention-session/
language: en
---

# Logging an Intervention Session

The **Log Session** dialog (WP-FID-SESSION) is how you record that a planned intervention session was delivered. Each log entry feeds the fidelity tracker, which determines whether a support plan can be evaluated for a tier review.

> **Note:** **Why this matters:** a plan that was not fully delivered cannot be judged as ineffective. Logging
> sessions accurately ensures that Amal distinguishes "the plan didn't work" from "the plan wasn't
> done" — and protects students from incorrect escalation.

## How to log a session

1. Open the plan detail for the active assignment.
2. Tap **تسجيل جلسة** (Log Session).
3. Fill in the dialog:
   - **Session date** — the date the session was delivered.
   - **Duration** — actual duration in minutes.
   - **Delivery mode (optional)** — how the session was delivered: in-person individual, small group, one-to-one, or remote.
   - **Major delivery issue (optional)** — if something significant affected delivery (very short sessions, incomplete materials, or mis-delivery), toggle this on. The system uses this signal to classify the fidelity issue internally. There is no free-text field.
4. Tap **حفظ** (Save).

The session is logged immediately. A recompute of the fidelity rate runs automatically. The fidelity card on the plan detail refreshes to show the updated rate and verdict.

## Reading the fidelity card

The fidelity card shows:

| Field | What it means |
|---|---|
| **Fidelity rate** | Sessions completed ÷ sessions planned (shown as a fraction, e.g. "11 من 18") |
| **Rating** | High (≥80%) / Adequate (60–79%) / Partial (40–59%) / Low (<40%) / Unknown (no data) |
| **Verdict** | `continue` / `adjust_intervention` / `cannot_evaluate_yet` / `fortuitous_complete_dose` |
| **Escalation status** | Whether the fidelity gate permits or blocks a tier-escalation request |
| **Effect validity** | Valid / Limited / Invalid due to implementation gap |

The fidelity card also shows a short **review-meeting paragraph** in Arabic. This is a rule-written, templated text — it is never generated by an AI. It is filtered for growth language before it is shown.

> **Warning:** **Off-track plans.** If no sessions are delivered for several consecutive instructional weeks, the
> plan is marked **off-track**. While off-track, both escalation and de-escalation are blocked — a
> plan that was not running cannot be used to judge a student's response. To resume, select a
> context flag from the closed dictionary (7 allowed values). After resuming, fresh comparable
> evidence must accrue before a tier-review can proceed.

## What you cannot do

- Edit or delete a logged session — session log entries are permanent (append-only).
- Enter free text about a delivery issue — the major delivery issue field is a boolean toggle; there is no free-text field on any fidelity path.
- Store personal notes about a student — there is no notes field on any fidelity path.

## Related guides

- [Intervention Fidelity Tracker](https://docs.growamal.com/en/guides/fidelity-tracker/): the full fidelity computation engine and the escalation gate
- [RTI Alerts Inbox](https://docs.growamal.com/en/guides/rti-alerts-teacher/): how the fidelity verdict affects tier-review eligibility
- [Adjusting an Active Plan](https://docs.growamal.com/en/guides/plan-modifications/): how a schedule adjustment changes the fidelity denominator