Breadcrumb: BCBA › Target configuration
Override mastery for a context or maintenance
Give one generalization context, or a target's maintenance probes, their own measurement and mastery settings, and reset them to the target's settings later.
By default, every generalization context and every maintenance probe of a target is judged by the target's Active configuration: the same trials, thresholds and steps you set for teaching. Sometimes one setting needs different rules, for example fewer trials at school or a lower threshold with a new therapist. An override gives one context, or the maintenance phase, its own values. Only the values you change are stored; everything else keeps following the Active configuration.
Before you start
- Overrides apply when your clinic collects generalization and maintenance in Granular mode, where each run is scored against criteria. In Simple mode aides record a pass or fail, so there is nothing to override and the buttons below do not show.
- Generic targets cannot be overridden.
- A context override needs the context to exist first: see Configure generalization for a target.
- You do this on the target's page in the web app: open the plan's Goals tab and select the target's name. See Review a target's details page.
- Org owners can set overrides the same way.
Override one generalization context
The Generalization section of the target's page lists the contexts. Each shows Inherited or Overridden, and an overridden context also shows how many fields differ, for example 2 fields overridden. Open a context row to see its Effective configuration, with each overridden value tagged.
- On the context's row, select Edit override. The Configuration override window opens with the context's name in its title. Its helper line says Inherited from Active configuration — updates live. or This context no longer follows the Active configuration., and a grid shows where each value comes from.
- Change the values this context needs. The form is the target type's usual editor, with the number of sessions needed to pass the context and Count different days under it. The toggle starts as the target has it. Turn it on to pass the context on consecutive days, each with every session in this context passing; see Counting days instead of sessions.
- Optionally, fill Regression Criteria: a Regression floor and Consecutive sessions below floor. Fill both or leave both empty. The floor must mean worse performance than the context's pass threshold, or saving shows an error that names the threshold. The regression count is always in sessions, even when the context counts days.
- Select Apply. It is available only once something differs from what you opened.
The message Context configuration applied appears and the window closes.
Reset a context
On an overridden context, open Edit override and select Reset to inherited, then confirm. The message Context configuration reset to inherited appears and the context follows the Active configuration again. Applying values that equal the Active configuration has the same effect.
If you close the window with unsaved changes, Discard configuration changes? asks first; Discard changes throws them away. Clicking outside the window does not close it.
Override maintenance probes
The Maintenance section of the target's page shows Judged by the target's Active configuration or Maintenance-specific override. When there is an override, it lists only the overridden values. You can set one at any status, before the target reaches maintenance.
- In the Maintenance section, select Configure. The Maintenance Settings window opens.
- Under Probe judging, select Maintenance-specific override. The Maintenance judging override window opens.
- Change the values probes should be judged by. This form has no session count, no Count different days and no regression criteria.
- Select Apply. The message Maintenance judging override applied appears and you return to Maintenance Settings.
- Select Close. The probe judging choice is already saved, and so is any change to the probe schedule. Save schedule is needed only on a target with no schedule yet, to keep the suggested values as they are.
When an override is stored, Edit override sits next to Maintenance-specific override.
To go back to the Active configuration, select Judge probes by the target's Active configuration. The override is removed at once, without asking, and Maintenance judging reset to inherited appears. Reset to inherited inside the override window does the same but asks first.
For a target already in maintenance, the plan's Goals tab opens the same Maintenance Settings window: see Configure maintenance for a target.
What happens next
- New runs in that context, and new maintenance probes, are scored under the overridden values. Runs saved before keep their result. A run edited later is scored again under the settings as they are at that moment.
- Values you did not override keep following the Active configuration. A later change to the target's configuration reaches every inherited value in every context and in maintenance.
- A context that counts days, from the target or from its override, shows its progress in days, for example 2 of 3 days. Changing the toggle does not take back a context that has already passed.
- If someone changes the target's Active configuration while your override window is open, Apply is refused with a message asking you to reopen the editor. Close it and open it again; your unsaved changes are lost.
- Changing a Rate target's unit removes the rate thresholds from its overrides without warning. Check the overrides after such a change.
- The mobile app has no override editor. Aides see the effect in the result of each run.