1. The default value for this field is “None”. Agencies are responsible for manually changing the default value of “None” to “Hired On/After 7/1/2017” for all employees first hired on or after July 1, 2017. 2. If an employee has multiple jobs, consideration must be given to the employee’s first job. If the hire date for the employee’s first job (in CT Company) is on or after 7/1/2017, all job (employment) records (in CT Company) must consistently be populated with the value “Hired On/After 7/1/2017”. 3. When applicable, the field must be populated with the value “Hired On/After 7/1/2017” even if the job is not benefits-eligible.

By ensuring that all employment records are populated when applicable based on first hire date, even if the job(s) are not benefits-eligible, the data is then readily available should the employee eventually be hired into a benefits-eligible job so that benefits are correctly charged.

How to Handle New Hires effective on or after 7/1/2017 that have already occurred:

If the effective date of the New Hire is the same as the effective date of the top row:

1. Add a new row effective the same date as the Hire row (up one sequence) 2. Use an Action/Action Reason of Data Change/General Data Change 3. Change the Benefit Program Date field to “Hired On/After 7/1/2017” 4. Enter a note in Notepad to document the action

If the effective date of the top row is after the effective date of the New Hire:

1. Submit a Footprints ticket for update by Core-CT.

Remember to update all employment records if applicable.

Agencies must populate this field for all new hires that have already been made no later than October 23, 2017. Additional benefit processing will be needed shortly thereafter so it is important to meet this deadline. If correct history is needed, please submit your Footprints tickets by October 9, 2017 to allow us time to process the update. You may include up to 20 employees per ticket.

Information regarding the processing of the Job Data actions in On-Demand Event Maintenance for those hired on or after July 1, 2017 will be forthcoming from the OSC/Central Benefits Unit.

The new field will be added to the CTW_EMPLOYEES table in EPM shortly so that agencies can run reports that include this information. A Daily Mail will be sent when this is complete.

Note: The new security role that provides view-only access to Job Data records is important to conducting the analysis necessary to determine one’s first date of hire across multiple employment records. If this role has not yet been requested for one or more of your agency HR staff, it is important to do so now.