Release Recap
The CR LiftEd 26.7 release offers special education teams more control over how they capture and interpret data. Districts can now customize ABC dropdown values to match their own frameworks, track intervention phases directly alongside behavior data, and benefit from several targeted improvements to data collection workflows.
The following will be released:
ABC Customization
Districts can now create and manage custom Antecedents, Consequences, and Locations for ABC data collection.
The District Library includes three new tabs, one for each value type, where District Administrators, Principals, and BCBAs can add, edit, archive, and restore values. These tabs control what appears in the ABC dropdown menus during data collection and are only visible to those roles in the District Library. Other users in the system will not see these tabs.
Values added to the library will display in the dropdown menu of options when team members collect ABC data.
ABC graphs now filter to show only the antecedents and consequence values that have data for the selected behavior and timeframe, keeping visualizations focused and relevant.
Behavior Phase Tracking
Special education teams can now record and track intervention phases alongside behavior data across student profiles, graphs, reports, and exports. This gives BCBAs, behavior specialists, and educators a structured way to document where a behavior is in the intervention cycle and visualize how data trends are related to each phase.
District Library: A new “Behavior Phase” tab in the District Library allows District Admins to manage phases available across the district.
LiftEd includes six default phases that cannot be edited or removed: Baseline (fixed initial phase), Intervention, Fading, Generalization, Maintenance, and Discontinued.
Each phase tile displays basic creation details.
District admins can create custom phases, which will always display after the default phases in dropdowns.
Student Profile: The Behaviors table within student profiles now contains a Current Phase column, enabling teams to see where each behavior stands without opening a graph or report.
Any user with access to a student can log phase changes from the behavior’s ellipses menu and support backdating, optional labels, and notes.
When a user attempts to enter a backdated effective date, a confirmation message will display on screen before proceeding.
When saving a phase change, a confirmation displays the effective date, so users can verify the change before it applies. A behavior phase can only update once per day, and a behavior can only have one active phase at a time.
Behaviors added to the system prior to launch of the phase change capability will display as "Not Specified" for the current phase until a new phase is initiated.
Graphs, Reports, and Exports: Phase changes appear on behavior graphs as vertical dotted lines with labels, making it easy to see how behavior data shifts across intervention stages.
Hovering over a phase marker shows details; clicking allows editing or deletion.
If a phase has an optional label entered, the optional label will display on the graph. If there is no optional label, the phase name will be displayed.
No phase marker or label will display on the graph until a new phase change is initiated.
Editable fields include:
Name
Label
Phase
Notes
Effective date
A confirmation message will display prior to deletion.
Reports and exports now reflect both the current phase on the graph and the phase associated with each data entry.
Workflow Improvements
Behavior graphs now show a daily total when hovering over a datapoint, giving users a summary without leaving the graph view. The value displayed depending on the measurement type:
Frequency: total count across all sessions for that day.
Duration: total duration across all sessions for that day.
Interval: overall percentage across all intervals for that day.
Duration now supports manual entry, enabling team members to document how long a behavior occurred after the fact rather than relying solely on the in-app timer.
The minus button within data collection is now always visible, making it possible to record a zero value as an intentional data point rather than leaving the session blank.