Data & AssessmentBehavior For AdminBehavior Code Management

Behavior Code Management

Prior to using the Behavior Module it will need to be configured for district use. Configurations are setup within Code Management. It is helpful to also visit the Behavior FAQ beforehand.

For DNA clients only, configurations will vary and focus mainly in support of using Minor Incidents. Please review any and all footnotes.

Where to Start

Where to Start

1. Click the Gear.

2. Next, click Code Management.

Codes

Codes

There are a variety of Behavior areas that will need to be set up to meet the needs of the district. Click on the one that you will work with and click Load.

During the initial setup many of the Behavior Codes are empty and will produce a blank list.

Add Code

Add Code

For most Behavior Code Management Setup, click on Add Code and make sure to fill in the following:

  1. Code Key - This is a unique alphanumeric identifier created by the district.
  2. Code Translation - This is the Name of the code.
  3. Select the site that this code will be used by. In most cases, it will be used by all of the schools in the district and the district name should be selected.
  4. If this is an active incident code, keep this at the default Yes/True setting. This is particular important for ISI clients who are importing previous or past Behavior data into the system, using codes previously used for incidents.
  5. Select the Incident Type, which will determine where the type is available as part of creating a minor and/or major incident report

All other fields can be left blank and are for internal use. Click Save when finished (6).

DNA Only Clients

Incident Types must be selected as Both -Major or Minor Incident OR Minor. Any setup configurations setup as Major will not be available in the available features of the Behavior module.

Code Table configurations that focus mainly on using Minor Incidents include the following:

  • Behavior Consequence Codes
  • Behavior Consequence States
  • Behavior Incident Descriptions, and
  • Behavior Locations

Behavior Code Table Examples and Samples

When working with blank code tables it is sometimes helpful to see samples. The following are samples for Behavior codes that are not populated by Illuminate. These samples are intended to help you decide what you should fill in for each category to best meet the needs of your district.

The following tables are just a few examples within Code Management:

Behavior Consequence Codes

*In support of both Major and Minor Incidents

Behavior Consequence Status

*In support of both Major and Minor Incidents

Behavior Incident Descriptions

*In support of both Major and Minor Incidents

Behavior Locations

*In support of both Major and Minor Incidents

Behavior Violations

Behavior Violation Codes are populated by Illuminate as they contain the universal Ed. Codes.  You will need to verify that several of the fields are set appropriately to meet the needs of the district.  

  1. Suspend - This field determines if the violation is a suspend-able offense.  All violations set to true will display in the Suspension Report found in the Behavior module.
  2. Expel - This field determines if the violation is grounds for expulsion.  All violations set to true will display in the Expulsion Report found in the Behavior module.
  3. Is Active - If this field is set to true then it will be available for use by anybody entering behavior incidents.

*In support of Major Incidents only

Behavior School Day Typical Duration

Behavior School Day Typical Duration

Example of a School Day Typical Duration of 6.3 hours changed to 6.1 hours using State mappings. Also note that currently 6.3 is set as the default based on CA averages.

*In support of Major Incidents only.

Next Steps

Now that your Code Management has been configured, lets create some Behavior Form Letters!