Skip to main content
Skip table of contents

Discipline Incidents Setup

Contents

California specific Incident Management types, codes and subcodes must be set up prior to creating discipline incidents. See Enter District Info for information about loading the California specific Incident Management configuration file.

Incident Rules

Incident Type

State reportable incidents must be associated with the incident type CA State Reporting.

Offenders

At least one student must be assigned the role of offender for each incident. If there is more than one offender in the incident, then the incident is reported once for each offender.

Behaviors

At least one behavior must be defined for each incident. After you create a behavior, you must click and drag the behavior to the offender to associate the two elements. If there is more than one behavior in an incident, then you must select the Primary Behavior checkbox for one of the behaviors.

The primary behavior is reported for each student offender in the incident as the "Incident Most Severe Offense Code." The primary behavior is also reported as the "Student Offense Code" for the student assigned the primary behavior.

For student offenders whose behavior is not marked as primary, their non-primary behavior is reported as the "Student Offense Code."

To use CRDC Behavior codes for CRDC reporting, the Incident Management: CRDC Behavior Codes must be added in the District Setup > Discipline and Log Entries: Incident Management page.

Additional behavior types may be defined for local use, but are not reported.

Actions

In most cases, the final action must be defined for each incident. To be reported, the final disciplinary action taken for the offender must be Suspension, In-School Suspension, or Expulsion, and may not be the action that was originally recommended. After you create an action, you must click and drag the action to either the offender or the behavior. After the action is associated with the offender or behavior, it no longer appears under Incident Elements.

Additional action types may be defined for local use, but are not reported.

The following exceptions apply:

  • Incidents with student offenders involving a firearm offense are reported regardless of the action taken.
  • Incidents involving special education student offenders are reported regardless of the action taken. A special education student is defined as a student who has an active CALPADS 144 Program on the date of the incident. The CALPADS 144 Program end date must be blank or occur after the incident date.
  • Incidents with a student offender who was truant during the reporting year are reported regardless of the action taken.
    Note: If there is no action assigned, then for special education students, and students with an offense code of 100, 101, or 102 (firearm), the report extracts a value of 300.

Reporters, Victims, Witnesses

Reporters, victims and witnesses are not reported in CALPADS Discipline incidents, but may be defined for local use. Behaviors and actions may be assigned to reporters, victims, and offenders, but are only reported for offenders.

Objects

Objects must be defined for each weapon involved in the incident. After you create an object, you must click and drag the object to the appropriate offender.

Attributes

Attributes can be defined for local use, but are not reported.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.