Behavior Fields in openSIS | Configure Behavior Parameters

Understanding Behavior Fields in openSIS

Overview

Behavior Fields in openSIS allow schools to structure, document, and manage student behavior incidents in a consistent and configurable way. These fields define what information is captured when a behavior incident is recorded under the Behavior & Discipline module.

Using Behavior Fields, administrators can ensure that behavior records follow the school’s policies, reporting requirements, and documentation standards.

What Are Behavior Fields?

Behavior Fields are data fields that appear on the Add / Edit Behavior Incident screen.
They capture essential details such as:

  • Who was involved

  • What happened

  • When and where it occurred

  • How the incident was handled

  • Administrative decisions and follow-ups

These fields help maintain accurate records, support discipline workflows, and enable future reporting and review.

Types of Behavior Fields

Behavior Fields in openSIS are divided into two categories:

1. Default Behavior Fields

  • Preconfigured system fields

  • Required for core behavior tracking

  • Cannot be deleted

  • Ensure consistency across schools

Examples include:

  • Student Involved

  • Date of Incident

  • Problem Behavior (Major / Minor)

  • Reporting Staff

  • Administrative Decision

2. Custom Behavior Fields

  • Created by school administrators

  • Used to capture school-specific behavior details

  • Fully configurable

  • Can be edited or deleted if no longer required

Examples:

  • Counselor Notes

  • Parent Contact Details

  • Follow-up Actions

  • Custom Incident Notes

Why Use Behavior Fields?

Using Behavior Fields allows schools to:

  • Maintain standardized behavior documentation

  • Capture complete and structured incident details

  • Align behavior records with school policies

  • Improve administrative visibility and accountability

  • Reduce ambiguity in incident reporting

Who Can Configure Behavior Fields?

  • Only Administrators can access and configure Behavior Fields

  • Teachers and staff use these fields, but cannot modify their structure

Where Are Behavior Fields Used?

Behavior Fields are used in:

  • Behavior & Discipline → Add Referral

  • Student behavior history and reviews

  • Administrative discipline workflows

Any changes made to Behavior Fields directly affect how behavior incidents are recorded moving forward.

Important Notes

  • Default Behavior Fields are system-defined and cannot be removed

  • Custom Behavior Fields should be created carefully to avoid duplication

  • Deleting a custom field may affect historical records

    • Related Articles

    • Where Behavior Fields Are Used in openSIS

      Overview Behavior Fields configured in openSIS are actively used across the Behavior & Discipline workflow. Understanding where these fields appear helps administrators see the direct impact of their configuration choices. This article explains where ...

    • How to Access Behavior Fields Settings in openSIS

      Overview The Behavior Fields Settings section in openSIS allows administrators to view and manage all behavior-related fields used when recording student behavior incidents. This article explains where this setting is located and who can access it. ...

    • Default Behavior Fields Explained in openSIS

      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 ...

    • Sorting and Display Order of Behavior Fields in openSIS

      Overview In openSIS, Sort Order controls the sequence in which behavior fields appear on the Behavior Incident form. Proper ordering helps staff enter information efficiently and ensures that critical fields are noticed first. This article explains ...

    • How to Add a Custom Behavior Field in openSIS

      Overview Custom Behavior Fields in openSIS allow administrators to capture school-specific behavior information that is not covered by default fields. These fields help schools document additional details required by internal policies or reporting ...