---
title: "Adjusting an Active Plan"
url: https://docs.growamal.com/en/guides/plan-modifications/
language: en
---

# Adjusting an Active Plan

The plan modifications panel (WP-PLAN-MODS-FE) lets you make targeted adjustments to an active support plan without exiting it or starting a new one. Adjustments are logged with a reason from the closed OverrideCodeCatalog — there are no free-text fields.

## How to open the panel

1. Navigate to **Plans** (خطط) in the sidebar.
2. Select the class and the active plan you want to adjust.
3. On the plan detail, open the **Adjust plan** (تعديل الخطّة) panel.

## What you can adjust

| Adjustment | Path | What changes |
|---|---|---|
| Delivery schedule | `OVR_SCHEDULE` | Session dates, frequency, or total planned sessions within the school schedule |
| Delivery mode | `OVR_DELIVERY` | How the plan is delivered (individual, small group, whole class) — must stay within the v3 allowed options |
| Scaffold support level | `OVR_SCAFFOLD` | The support level for a specific student x skill x bundle x task combination |

Every adjustment requires a **reason code** from the 9-code OverrideCodeCatalog. The code is always picked from a dropdown — there is no free-text reason field anywhere.

> **Note:** **Context flags are separate from plan adjustments.** A context flag from the closed dictionary (7 allowed values) can only be attached during an acute-regression alert review (the TAW\_15 dismiss-with-note path in the Plan Review surface). They are not available from the plan modifications panel.

> **Warning:** **Scaffold support levels are never student-general.** When you adjust a scaffold level, you are
> setting it for a specific skill within a specific bundle and task type — not for the student as a
> whole. The student never sees their support level.

## Reason codes

The 9-code OverrideCodeCatalog contains:

| Code | When to use |
|---|---|
| Override_Contextual_01 | Session circumstances made delivery different from plan (contextual reason) |
| Override_Procedural_02 | Procedural adjustment needed (scheduling, logistics) |
| Override_Scheduled_03 | Pre-planned schedule change (calendar event, holiday) |
| Override_DataGap_04 | Insufficient data to run the plan as-is — collecting more first |

These four codes have `applicableScope=all` and are the only codes valid on the plan-modifications (adjust) path. Codes 06-09 (`Bundle_Met_Criteria_06`, `Bundle_Teacher_Modify_07`, `Bundle_Acute_Regression_08`, `Bundle_Data_Incomplete_09`) are exit-scoped and appear only when you close a plan via the exit path. Submitting an exit-scoped code on an adjust request returns HTTP 400 `SCOPE_MISMATCH`.

The full 9-code table is seeded by the admin and visible inside the dropdown when you make an adjustment.

## After an adjustment

- **Schedule and delivery changes** trigger an automatic recompute of the fidelity rate (the plan's dose changes, so the rate updates).
- **Scaffold changes** open a fresh trend segment in progress monitoring (new comparability baseline).
- The adjustment is logged to the append-only audit trail. There is no way to undo a logged adjustment — you can make a follow-up adjustment if needed.

## Related guides

- [Teacher Activation Workflow](https://docs.growamal.com/en/guides/teacher-activation/): how to set a plan for the first time
- [Intervention Fidelity Tracker](https://docs.growamal.com/en/guides/fidelity-tracker/): how schedule and delivery changes affect the fidelity rate
- [RTI Alerts Inbox](https://docs.growamal.com/en/guides/rti-alerts-teacher/): why an adjustment opens a fresh trend segment before any review signal can fire