Overview

openSIS comes with a set of default behavior fields that are essential for recording and managing student behavior incidents. These fields ensure that behavior records remain consistent, complete, and compliant across the system.

This article explains what each default behavior field is used for and why these fields cannot be removed.

What Are Default Behavior Fields?

Default Behavior Fields are system-defined fields that appear automatically when recording a behavior incident. They are designed to capture the minimum required information for effective behavior tracking and administrative decision-making.

These fields:

• Are available by default

• Cannot be deleted

• Maintain standardized behavior documentation

List of Default Behavior Fields and Their Purpose

Below is an explanation of each default behavior field available in openSIS:

Student Involved

• Identifies the student(s) involved in the incident

• Supports selecting multiple students if required

Witness

• Records any witnesses present during the incident

• Helps provide additional context

Date of Incident

• Captures the exact date when the incident occurred

• Used for timeline tracking and reporting

Time of Incident

• Records the time of the incident

• Useful for scheduling analysis and supervision review

Possible Motivation

• Indicates the suspected reason or trigger for the behavior

• Helps identify recurring patterns

Location

• Specifies where the incident took place

• Supports location-based behavior analysis

Problem Behavior – Major

• Used for serious behavior violations

• Typically linked to disciplinary action

Problem Behavior – Minor

• Used for less severe behavior incidents

• Helps track early warning signs

Details of Incident

• Allows staff to describe the incident in detail

• Provides narrative context for administrators

Assigned To

• Specifies the staff member responsible for follow-up

• Ensures accountability

Reporting Staff

• Identifies who reported the incident

• Supports transparency and verification

Administrative Decision

• Records the administrative action or outcome

• Important for discipline records and audits

Why Default Fields Cannot Be Deleted

Default Behavior Fields are required to:

• Preserve data integrity

• Maintain consistent discipline workflows

• Ensure accurate historical records

• Support system-wide reporting

Removing these fields could compromise behavior tracking and reporting.

---

Can Default Fields Be Modified?

• Titles and core behavior fields are system-controlled

• Some display properties may be locked

• Customization should be done using Custom Behavior Fields

---

Best Practices

• Use default fields as the foundation for all behavior incidents

• Avoid duplicating default fields as custom fields

• Add custom fields only when additional information is required