Main Menu

SIS 2000+ Behavior History


Last update: 08/05/2000 jmm

Sec. 3, Add an Incident to the Master List

The Behavior History program tracks the conduct of individual students by recording behavioral "incidents". When a behavioral problem first occurs, it is recorded as a date-sensitive behavioral incident in the Behavior Incidents master list. Once it is recorded in the master list it can then be referenced by any number of student behavior records and used to create individual student "involvement records" for those students involved in the incident (See Sec. 4). The flowchart below illustrates the way the procedure is organized.

Flowchart:


Fig. 16

This design allows for multiple students, such as perpetrators, witnesses, victims, etc. to be associated with a single behavioral incident. The master list will store the universal attributes for each incident whereas individual student Behavior records will contain only data pertaining to their personal involvement in an incident.

3.1 Find Student (optional)
The Behavior Incidents master list can be accessed from any student Behavior record (Fig. 17). However, if the user knows at least one student name who is involved in the incident to be added, a step can be saved by going to that record first and then accessing the Behavior Events master list from there. See Sec. 1 for details on the Find a Student procedure.


Fig. 17 - student Behavior record

3.2 Open and view Behavior Incidents master list
Click on the Add command button at the bottom of the Behavior History main screen

The Behavior Events master list (Fig. 18) displays a list in the upper half of the screen of all recorded behavioral incidents in ascending chronological order. This list can only be scrolled - it cannot be sorted. When an incident is selected in the grid the Faculty Involved and Students Involved fields in the lower half of the form will display which faculty members and students have been affiliated with the incident (if any).


Fig. 18

Check the list to verify that the event to be added has not been already recorded. Incidents can be distinguished from one another in the grid primarily by the combination of the Date field and the Description field. However, if there is more than one incident with the same data in these fields then the attributes in the other fields must be used to distinguish between the incidents. If further verification is needed, use the horizontal scroll bar to view the Notes field in the right side of the grid (Fig. 19) .


Fig. 19 - right side of grid

3.3 Add the Incident to the master list

After verifying that the incident to be added is not already in the master list, click on the small Add command button at the bottom of the Behavior Incidents form. This action opens the 'Add Incident' form Fig. 20. Use the Tab key to move from field to field. Enter data as follows:


Fig. 20

Click on the Save command button to save the data and return to the Behavior Incidents master list. The new incident will now be displayed in the list in ascending chronological order according to the Date entered (Fig. 21).


Fig. 21 - new incident added to the list

3.4 Add Faculty involved
If any faculty member was involved in the incident, such as a witness or victim, click on the Add command button below the Faculty Involved field to open the 'Add Faculty Incident' form (Fig. 22). Use the Tab key to move from field to field. Enter appropriate data and Save.


Fig. 22

After the Faculty data is saved the view will return to the Behavior Incidents form. The faculty members that have been associated with the selected incident will be displayed in the Faculty Involved field (Fig. 23). These records can be edited later (See Sec. 7).


Fig. 23

3.5 Continue or exit
At this point in the process the user has five choices for action using the command buttons at the bottom of the 'Behavior Events' form:



< Previous Section | Next Section >