Behavior Entry Processing

Run Periods, Behavior Resolutions & Resetting Entries

This page covers the three admin workflows that manage how behavior entries move from recorded incidents to processed outcomes: Run Periods, Behavior Resolutions, and Reset Behavior Entries. These tools are closely connected — run periods collect eligible entries for a date range, behavior resolutions let administrators review and finalize outcomes, and resets deactivate older entries when a school is ready to clear progression.

Before using these tools, make sure your school has already configured Behavior Forms Setup, Discipline Matrix & Major Offenses, and Administrative Decisions & Letter Templates. Those setup pages determine what outcomes appear here, how points are interpreted, and what letters or notifications can be sent.

Overview

Run Periods

Navigation: School → Behavior → Run Periods

Run periods are used to process behavior entries up to a selected end date. In a typical workflow, an administrator creates a run period, chooses whether to include violations, recognitions, or both, and then runs it. The system evaluates eligible entries, calculates points, matches outcomes, and creates the records that appear in Behavior Resolutions.

This is usually done on a regular schedule such as weekly, biweekly, or by term, depending on the school's discipline process.

What happens when a run period is executed

When a run period is executed, the system performs several steps automatically:

1. Tardy auto-import — If the run includes violations, the system first imports any tardy records from the attendance module (entries marked with the Tardy code configured in the plugin settings) into the behavior log before processing. Admins do not need to manually enter tardies — they are pulled in automatically.

2. Point calculation — For each student, the system totals points from all eligible behavior entries. For progressive/countable behavior categories, entries up to the configured limit number receive the base point value, while entries exceeding the limit receive the “point after limit” value. All direct step points from the discipline matrix are added on top.

3. Outcome matching — The system matches each student's total points against the configured behavior outcomes. It finds the outcome where the minimum point threshold is met, selecting the highest qualifying outcome first.

4. Resolution or referral creation — Based on the matched outcome type:

   • If the outcome type is Minor → the system creates a behavior resolution

   • If the outcome type is Major → the system creates a referral with status “Resolution Entry”

   This is important — a run period can generate both resolutions AND referrals depending on the student's point total and the configured outcome thresholds.

5. Auto admin decision — If only one admin decision exists for the matched outcome, it is automatically assigned to the resolution or referral. If multiple decisions exist, the admin must select one manually.

6. Email notification — After the run completes, the system sends an email to the admin who triggered the run with a summary: “X resolution(s), Y referral(s)” along with links to both the resolutions and referrals lists.

What admins do on this page

• Create a new run period

• Select the run period end date

• Choose which entries to include: Violations, Recognitions, or Both

• Run the period

• Review past runs, including created and modified dates

• Use action icons to open related lists or available actions

Run period list

The run periods list provides a running history of each processing cycle. This page is useful not just for starting a new run, but also for reviewing what has already been processed and when.

Common run period workflow

1. Open School → Behavior → Run Periods.

2. Select Add.

3. Choose the run period end date.

4. Select whether to include violations, recognitions, or both.

5. Save and run the period.

6. Check your email for the run summary showing how many resolutions and referrals were created.

7. Open the related Behavior Resolutions list to review outcomes for that run.

The resolutions list can be opened from the run period workflow. The run period filter on the resolution page uses the run period end date, which makes it easier to confirm you are reviewing the correct cycle.

Undo and re-run

Some schools need to correct a run after setup changes, late entries, or processing mistakes. Radix supports undo and re-run actions, but these should be used carefully.

• Undo reverses a run completely — it deletes all resolutions AND referrals generated by that run, resets all affected behavior entries back to unprocessed status, and reactivates the run period so it can be modified or re-run.

• Re-run processes the run period again after corrections have been made. The system tracks the original run time and re-run time separately for audit purposes. An “all records” option is available to control the re-run scope to ALL or to the unprocessed entries .

If a reset exists on or after the same timeline, certain undo or re-run actions may be restricted. This protects data consistency and helps prevent using entries that were already voided by a reset.

Important warnings for runs and resets

Radix includes safeguards when resets and runs overlap.

• If a reset date is earlier than the latest run date, the system warns that some entries may not be deactivated because they have already been used in a run period.

• Run periods dated on or before an existing reset may have undo or re-run actions disabled.

A simple best practice is to agree on one school rhythm. For example: run weekly, process resolutions, and only reset at a larger checkpoint such as quarter or semester end.

Behavior Resolutions

Navigation: School → Behavior → Behavior Resolutions

Behavior Resolutions is where administrators review the outcomes produced by run periods and finalize what a student receives. This is the step where accumulated entries become a documented consequence or reward, paired with an admin decision, scheduling details, and optional family communication.

Students may appear more than once if your school is using both consequence and reward workflows.

Resolution list

The resolutions list organizes generated and manual resolution records for admin review. Filters on this page are especially important because many schools process a large number of records over time.

List columns (24 columns)

Action icons (5 per row)

Icon	Action	Description
	Letter preview	Opens the resolution letter in a new tab for review or printing
	Notification history	View sent notification log for this resolution
	Edit	Open the resolution form to modify fields
	Delete	Remove the resolution record
	Behavior entries	View the behavior entries linked to this resolution from the run period

List features

Bulk operations

The resolution list supports bulk actions for efficient processing:

• Select All / Deselect all — Toggle selection of all visible rows

• Edit Selected Records — Opens a bulk edit form to update multiple resolutions at once

• Print Selected Letters — Generates and prints letters for all selected resolutions

Processing a resolution

When an admin opens a resolution to process it (gear icon), they review the suggested outcome and complete the fields needed for final action and communication. The form has 22 fields, and the exact fields visible depend on whether the resolution is for a consequence or a reward.

Full resolution form fields

Manual resolutions

Admins can also add a resolution directly by clicking Add New Resolution. This is helpful when a school needs to document an action outside the normal run-period cycle. When adding a manual resolution and selecting a student, the form refreshes to show the current consequence count, reward count, and last consequence information.

Letters and notifications

Behavior resolutions can trigger letters and notifications based on the selected Admin Decision and your Administrative Decisions & Letter Templates setup.

How notifications are processed

1. When a resolution is saved with “Send Notification to Parent” or “Send Notification to Student” set to Yes, the notification is queued.

2. A scheduled task (usually runs every minute) picks up queued notifications.

3. The system generates a PDF letter based on the letter template configured for the selected Admin Decision.

4. The PDF is attached to the email and sent to the parent(s) and/or student.

5. Each notification is logged for audit purposes — viewable via the notification history action icon on the resolution list.

6. After sending, the notification flags are reset and the Parent Notification Date is recorded.

Notification rules

• Parent notifications depend on a valid letter template attached to the selected Admin Decision.

• Only registered parents with custody are eligible to receive these notifications.

• Students can also receive notifications or direct messages where enabled.

• If an Admin Decision does not have a letter template, notifications will not be sent for that resolution.

Printing letters

Admins can print parent-facing letters from processed resolutions when templates are configured. Use the letter preview action icon on individual resolutions, or select multiple resolutions and use Print Selected Letters for bulk printing. This supports consistent communication and a formal paper trail for conferences, detention notices, suspensions, or rewards.

Bulk Edit Form

When an admin selects multiple resolutions using checkboxes and clicks Edit Selected Records, the bulk edit page opens with two sections:

• Top section: The bulk edit form with fields to apply across all selected records

• Bottom section: A reference table showing all selected resolutions with their current values

How bulk editing works

Each field in the bulk edit form has an enable checkbox next to it. Fields are disabled, or greyed out, by default until the admin checks the enable box. Only enabled fields are applied to the selected records — unchecked fields are left unchanged on all records. This prevents accidental overwrites.

Bulk edit form fields

The notification fields (Send Notification to Parent, Send Notification to Student, Send Message to Student) do not have enable checkboxes — they are always active in the bulk edit form.

Selected resolutions table

The bottom of the bulk edit page shows a reference table with all selected resolutions, including these columns:

Additional controls

• Add more — Returns to the resolutions list to select additional records to include in the bulk edit

• Reset Selection (red button) — Clears all selected records from the session

• Submit and Reset — Applies the enabled field changes to all selected records and clears the selection

Deleting a Resolution

When an admin clicks the delete action icon on a resolution, the system opens a confirmation page that gives the admin selective control over what happens to the linked behavior entries.

What the delete confirmation page shows

1. Student name and consequence name for the resolution being deleted

2. A danger alert confirming this is a destructive action

3. A table of ALL behavior entries linked to this resolution — each with a checkbox, all checked by default

Behavior entries table on delete confirmation

The table uses a Check All header checkbox and shows these columns for each linked entry:

What happens when the admin confirms deletion

The system performs two separate operations based on the checkbox selections:

The resolution itself is soft-deleted, marked as deleted with the user ID and timestamp recorded for audit and can’t be restored by the admin.

Deleting a Behavior Entry

Behavior entries can be deleted from the behavior entries list (School → Behavior → Behavior Entries). When an admin clicks the delete action icon, the system shows a confirmation page.

What the delete confirmation page shows

• Date of the behavior entry

• Student name

• Behavior category name

If the behavior entry is currently processed and linked to a resolution or referral, the system displays a danger warning alerting the admin that they are about to delete a processed entry.

What happens on confirmation

• The behavior entry is soft-deleted — marked as deleted with the user ID and timestamp recorded for audit

• The entry is NOT automatically unlinked from its resolution — the resolution still exists and still references this now-deleted entry

• The resolution's point totals, consequence counts, and other calculated data are not recalculated

Delete permissions

The delete action has two permission levels:

Reset Behavior Entries

Navigation: School → Behavior → Reset Behavior Entries

Resetting behavior entries deactivates older entries before a selected date. It does not delete them. This is an administrative cleanup action used when a school wants to stop older entries from continuing to contribute to progression or future processing.

Because resets affect progression, they should be part of a clear school policy. Some schools reset quarterly or by semester. Others intentionally avoid resets so progression continues longer.

What a reset does

• Deactivates eligible entries before the chosen reset date

• Changes the entry's processed status to Voided (internal value: 2) — distinct from active/unprocessed (0) and processed (1)

• Prevents those entries from being used in future consequence or reward calculations

• Preserves the historical record for reporting and audit purposes

Reset options

Schools using recognitions can control what kind of entries are reset.

Reset warnings and restrictions

Resets can overlap with run periods, so Radix includes warning messages to help prevent unexpected results.

If the selected reset date is earlier than the latest run date, the system warns that some entries may not be deactivated because they were already used in a run period. Review the date carefully before continuing.

This matters because run periods may already have converted those entries into resolutions. A reset does not rewrite the school's processing history retroactively.

Past Resets

The Past Resets page provides the audit trail for reset actions. Use it to confirm what was reset, when it was done, and what type of entries were included.

How reset entries appear in reporting

Reset entries are not deleted from the system. Instead, they remain part of the historical record and appear as Voided in behavior reporting.

• Behavior entry reports label reset items as (Voided).

• Behavior overview reports can include total voided points.

• Some sites may choose whether voided entries appear on overview reports through plugin settings.

• In the behavior entries list, voided entries show as “Yes (Voided)” in the processed column.

Recommended admin workflow

1. Review recent behavior entries and make sure data entry is complete.

2. Create and run the next Run Period — check your email for the summary showing resolution and referral counts.

3. Open Behavior Resolutions filtered by the run period end date.

4. Review each resolution — check the student's consequence count, reward count, and last consequence for context.

5. Assign the correct Admin Decision and complete scheduling, served status, and notification fields.

6. Print letters or send notifications as needed — use bulk operations for efficiency.

7. Only perform a Reset Behavior Entries action when your school is intentionally clearing progression.

8. Use Past Resets and run period history to confirm what has happened over time.

If your school wants progression to carry across longer periods, avoid frequent resets. Many schools find the best balance by running behavior weekly but resetting only at quarter, semester, or year-end checkpoints.

Best practices

• Use a consistent processing schedule so staff know when consequences or rewards will be reviewed.

• Filter behavior resolutions by run period end date to avoid mixing cycles.

• Check the student's last consequence and consequence count before assigning a new one to support consistency and fair progression.

• Review admin decisions and letter templates regularly so notifications do not fail unexpectedly.

• Use Private Comment for internal notes and Comment for anything that may appear in letters or reports.

• Treat resets as a policy decision, not just a cleanup task — discuss with school leadership before clearing progression.

• If a run or reset does not seem to behave as expected, review the sequence of actions first: run date, reset date, and any undo or re-run activity.

• Use bulk operations (Edit Selected Records, Print Selected Letters) to save time when processing large numbers of resolutions.

Permissions

Related pages

• Behavior Forms Setup

• Discipline Matrix & Major Offenses

• Administrative Decisions & Letter Templates

• Creating Behavior Entries & Parent Contact Log

• Referrals & Major Incident Reports