Point Removal Overview

Overview

This feature allows you to automatically remove X penalty points from your student's for not having any discipline incidents for Y days. Student Point removal can be found on the Conduct>Setup>Settings screen where you will be able to create rules for this process. Genesis uses the rules to analyze your students and to figure out which students qualify for point removal. If they qualify for point removal, a discipline incident with a negative point total is created for the student. This way you see how, when, and why the point(s) were removed.

TABLE OF CONTENTS

• Setup
• Infraction and Action Codes
• Student Point Removal Rules
• Understanding how the Rules are Analyzed

Setup

Infraction and Action Codes

The first step to using this feature is to assign an infraction code and an action code that the Point Removal routine will use to create the incident. In order to setup the infraction code, go to Conduct>Setup>Conduct Codes>Infraction Codes and hit the modify icon for the infraction code that you want to use. Once on the modify screen, switch the "Default Infraction for Auto Point Removal" field to Yes.

In order to setup the action code, go to Conduct>Setup>Conduct Codes>Action Codes screen and modify the code that you want to use. Switch the "Default Action for Auto Point Removal" field to Yes.

You can also setup infraction codes to not be included in the rule analyzing by setting the "Include In Auto Point Removal" to No. if you do this, then the infraction will be ignored when the routine is analyzing how many days since the last incident. This can be useful if you remove X points after and Y points after 14 days. This scenario is unusual so the defaults for this field is Yes.

You are now ready to create your rules.

Student Point Removal Rules

The rules are very simple to create. You only need to fill out the number of days since the last incident, and the number of points to remove. An example rule would be that after 14 days without an incident, the student would have 2 points removed. For that, you would enter 14 under the "# of days without infraction" column and and 2 under the "Points to Remove" column. Note that the point should be a positive value.  By default, the system counts the number of calendar days since the last incident.  If you would like the system to just count school days, simply check the "Check to use school days instead of calendar days in Point Removal logic" check box.

Another feature is the Recur checkbox. This allows you to setup 1 rule that is applied every X days. As long as the student has not received an infraction in X days, the rule will be continually applied until the student has 0 points. For instance if you set up a rule to remove 1 point every 7 days that recurs, students will be continually analyzed using this rule. If a student has not received an infraction in 7 days, then 1 point will be removed. If the student still has not received another infraction 14 days after their original infraction, another 1 point will be removed from the student. If you are using a recurring rule, you should not create additional rules. Multiple rules when you have a recurring rule can lead to a lot of confusion when trying to analyze the data.

Understanding how the Rules are Analyzed

The first thing this routine will do is to check the student's current point total. If the student already has 0 points, then the student will be skipped. Student point totals are not allowed to go below 0. If the student does have a point total of greater than 0, then the routine will progress.

In order to analyze a student for point removal is to grab all rules for the student's current school in order of the number of days descending (meaning that if you have multiple rules, the first rule analyzed will have the greatest number of days since last infraction). The student's last incident (with an infraction code that has "Include In Auto Point Removal" set to Yes) is then checked to see how many days it has been since it was given. If the number of days between the incident and today is not equal to the rule's number of days, then the rule is skipped. If there are no more rules, then the student is not given a new incident for point removal. If there are more rules, then the next will be analyzed.

If a rule is found that the student qualifies for, Genesis will then create a Discipline Incident using the Infraction code and Action Code that you have already defined in the setup. This incident will have a negative value of the number of points in the rule that qualified this student. For instance, if the rule has the "Points to Remove" as a 2, then the incident will award the student -2 points in the incident.

When the incident is created, the student's point total is automatically updated to reflect the new incident's point total. Genesis will not allow a student's point total to go below 0. So if the rule calls for 2 points to be removed but the student only has 1 total point, the new total will be 0, not -1.