Attendance to Conduct Overview

Modified on Wed, Feb 28 at 2:15 PM

Attendance to Conduct (ATC)


Genesis provides you with the ability to have conduct incidents automatically created when a student hits certain attendance thresholds. Do you want students to get a detention when they get 5 tardies? No problem! Genesis will allow you to setup rules to tie attendance to the conduct system. We also allow you to do the reverse. Do you want a student's attendance to reflect a suspension for the days it was given to them. No problem! Just tie your actions to an attendance code and you are good to go! Genesis provides you with a Simple, Easy and Effective way to manage your conduct and attendance needs.

The Attendance to Conduct setup is located on the Conduct>Setup>Attendance To Conduct screen.

The screen is divided into 2 sections: The School Setup and the ATC Rules.

School Setup



Allow attendance to create incidents using rules

This field allows you to turn the link between Attendance posting and Conduct creation on. There are 3 different options. The first option is the default and no rules will be applied when attendance is posted, even if rules exist. The second option tells Genesis to only apply the rules if attendance is being posted from the Attendance Checkin screen. The third option will allow the rules to be applied every time there is an attendance transaction applied to the student.

Location Code for Incidents

This is the default location for incidents created by the ATC link.

Convert X tardies to an absence

The 'Convert X tardies to an absence' field on this screen is only used when determining if an ATC rule should be applied. This does not effect actual attendance or credit loss.

Post attendance from conduct actions

This option allows you to configure your action codes in Conduct to post Daily Attendance when created. An example would be if a suspension is given to a student on Friday. That student's attendance for Friday would be automatically updated to reflect that suspension. You can read more about this in the section below.

Automatically remove incidents if student no longer qualifies for ATC rule

This option will remove a student's incident that was created by ATC if an attendance change causes the student to no longer qualify for the rule that the incident was based on.

Use Attendance Count not Attendance Value when summing attendance

This option tells the rule to count the number of attendance transactions rather than summing the attendance value from transactions (default behavior). For example, a half day (.5) absence would be a COUNT of 1 but a SUM of .5. So choosing this option would count that absence as 1 instead of .5 when figuring attendance credit loss.

Start actions in at least X school days

This option allows you to configure a custom value for the "Start Action" field on your ATC Rules. When you fill this out, a 'Custom' option will appear that can be used for when to start your actions.

ATC Rules

ATC Rules can be easily added on the bottom of the Conduct>Setup>Attendance To Conduct screen. 


We will go into some detail to help explain each filed and how it affects the rule.




This controls the order in which the rules are displayed on the screen. There is no other affect.


The code is a unique identifier for the rule you are creating. Try to make this a little descriptive to help you know what the rule is. For instance, if your rule applies a detention after 4 tardies, you could give it a code of DET_4TAR.

In this cycle

This field controls what time period the rule will count up the attendance. If you want to make the rule to only apply to semester 2, you can use the S2 cycle code. When attendance is posted, the rule will only count up attendance from S2 to see if the student qualifies for the rule.

When there are...

This tells you the number of absences or tardies that are needed in the cycle in order for a student to qualify for the rule.

Create Infraction

This is the infraction of the incident that will be automatically created. Only misconduct infractions are shown.

Give Action

The action selected here will be given to the student when the incident is created.

Days for Action

This is the number of days that you will want the action to be applied to the student. For instance, if you want the student to get 2 days of detention, then put a 2 in this field.

Start Action...

This field tells Genesis when to start the action. If Today is selected, then the action selected will try to be applied from today's date for the number of days selected in the the Days of Action field.  If the student already has a conduct action for today, then the next available day for detention will be selected.  Detention days can be configured for specific days of the week on the Conduct>Setup>Settings screen.

Setting up your Conduct Actions to automatically Post Attendance for Students

When student's are given a suspension, it can be difficult to for both the attendance office and the conduct offices to keep each other in the loop. That's why Genesis allows you to tie an attendance code to a specific action code so that the attendance will be automatically updated as the action is updated. An example of this features usefulness is when a student is given an out of school suspension. Once the Administrator has assigned the action, the attendance office will have to be notified so that the students attendance will correctly reflect their suspension. If the suspension is taken away or even changed to another date, once again the two offices will have to coordinate. As most districts can attest to, this can be a major headache.

How it Works

This can be set up in just two simple steps:

  1. Go to the Conduct>Setup>Action Codes screen and modify any code that you want to tie an attendance code to. On the bottom of the form, you will see a field called "Daily Attendance Code". Change this field to the attendance code that should be posted when a student gets this action.
  2. Once you have configured your action codes, switch over to the Conduct>Setup>Attendance To Conduct screen. This screen allows you to turn on the ability to post attendance based on an action. In order to do this, switch the field "Post attendance from conduct actions" to Yes.

Now you are ready to go! Going back to the previous example, any student given a suspension will now also get the suspension for their attendance on any day that the action was given.

If the action date is changed, the attendance will change with it. If the action action is removed, the attendance will be removed.

Location Code for Incidents - This drop down contains the list of Locations specified in the INFRACTION_LOCATIONS codes table.  This table is maintained on the Setup>Codes screen, in the Infraction Location Codes table.


  • Conduct Incident is not created when student gets sufficient Tardies 
  1. Make sure Attendance-to-Conduct is enabled:  Look on the Conduct>Setup>Attendance-to-Conduct screen to ensure that the "Allow attendance to create incidents using rules" parameter is set as intended.   
    1. If it is set to “Inactive Status.  The rules will not be applied”, Attendance-to-Conduct is turned off.  
    2. If it is set to “Only apply rules for Attendance Checkin”,  Attendance-to-Conduct will only work from the Attendance>Check-in screen.  
    3. If it is set to “Apply rules for all attendance transactions”,  Attendance-to-Conduct should always apply, no matter how Daily Attendance is posted.  
    4. Attendance-to-Conduct never applies to Class Attendance codes.  
  2. Make sure there is a Rule for the specific number of Tardies that the student has received.  
  3. Make sure the Rule is for the right Attendance Cycle (i.e. right  part of the School Year).  
  4. Make sure the Rule generates the right Action Code.
  • Daily Attendance is not set  correctly by posting an Action Code for a student’s Conduct Infraction.
  1. Make sure Conduct-to-Attendance is enabled:  Look on the  Conduct>Setup>Attendance-to-Conduct screen to ensure that the Post attendance from conduct actions parameter is set to Yes.
  2. Make sure the Action Code that was posted is correctly  configured to cross-post the right Attendance code:  Go to the  Conduct>Setup>Conduct Codes>Action Codes screen, locate the Action Code causing trouble and verify that it specifies the right Action Code.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article