1. Goals of this Session:  Allow networking between existing users for them to learn from each other, understand each other’s environments  Preview newest features  Talk about challenges  Blueprint features necessary for continued advancement of this module  Allow Q and A from districts who are not currently using for them to gain confidence and have a chance to know more about the leave process and CIMS. H/R Leaves

2.  Who is using?  Mystery Lake – All absences including same day sick. Union Press uses committee voting to pre-approve union related leaves  Turtle Mtn – All absences including same day sick  Seven Oaks – Unique PD committee based voting  River East-Transcona  Kelowna  Fort McMurray  Success Statements/Discussion  Eliminate all paperwork?.. Or still second form for sick/other?  More efficient and timely approval?  More convenient for employee?  Better information at school admin level?  More efficient reconciliation with payroll H/R Leaves

3.  LEAVES July 2011 – June 2012 (to date) H/R Leaves #Leaves#Leave Codes SD72-- DELTA-- SD232,25418 FMPSD5,00633 BSD-- TMSD2,51239 PLPSD-- MLAKE4,35749 RETSD3,69064 SOAKS1,38785 WSD-- Using for ALL absences!

4.  Leave Walkthru  Online access by employee (teacher, support, maintenance, EA) to request leave  Help them to add the appropriate leave (clear leave types, good instruction, NEW How to select leave document)  Amazing how employees try to cheat – emulate what they could abuse on paper (all holy days on one leave request, cannot input.5, multiple leave types on a single leave form,)  Online access by school admin to request leave on behalf of employee.. Most districts have an auto-email admin if they have not approved their leaves … make sure your district does!!!  Recommendation by school admin/maint: **Not ‘just SIGN HERE’ **  Important to qualify sub required info  Important to qualify #employees out of the building that day  Important to consider employee previous leaves/considerationsImportant to care?!  Final approval – concerns that their duties may not involve overages.. Cims should show balance right there?! H/R Leaves

5.  Leave Flow  Online Leave form is inputted  Copies – school (for Input/check), payroll, union, approvers  School Clerical feel a bit naked – EIS.538 is their answer. They are not interpreting the leave to turn it into a valid SUB record.  School Admin are ‘pressing buttons’ – our expectation is that they are looking at quantity, employee balances, sub information, and thinking about employee overall leaves plus school overall leaves as approval checklist of things to consider …  Approvers may have previously found it easier to ‘sign’ and expect their staff to confirm the details? Could work the same by using the complete but ultimate is that approver is responsible? H/R Leaves

6.  Implementation Considerations  What Groups to start with  How to structure leave types and documents so users understand and can select confidentally  How many leave type entries are incorrect?  How to engage the recommenders and Approvers in qualifying and looking at all the aspects. Our expectation is that in their OK the absence should occur. In reality we are beginning to believe that in reconciliation – the school sec, the user themselves, payroll changed the leave to be the correct sub entry – question exactly what the approved leave form actually did … yikes! H/R Leaves

7.  Latest Features and Gotchas  Sub Required response now mandatory also new NAM,NPM – more complete picture of exact absence, Sub Details  New auto-approval for certain leave types PAY.114  Front Screen Location Order determines location to appear for staff like custodians  Recommendation by School or by Maintenance Department Only  Image ‘*’ appears on EIS.538 to help with med note type leaves  EIS.538 and completion codes to identify special cases to payroll for pay consideration.  Enhancements to ProD expense reports, ProD create Req features  CIMS options used to look just at the first leave date only..enhanced  A Leave should never have more than one leave type. When you need to cheat – make sure you are using completion type, comments etc. to justify your change. H/R Leaves

8.  Latest Features and Gotchas  EIS.564 Payroll Compare Leaves to Sub Absences: New ability to auto-email employees to remind them that they are missing a leave entry! H/R Leaves New second page of EIS.564

9.  Enhancements to force entry into Sub Field, subtype (when applicable) to help approver with quality information  New Total #leaves for that location out today (to assist with decision)  Ability to branch to that employees absence balances  Authorization rules  Cannot approve at any future level without completing the approval at the lower level !!!!! H/R Leaves

10.  Challenges and Future Features  Get to 1 request and approval for being away (not 2,3,4 different pieces of paper and/or systems for Employee to fill out)  Issues with Sub-Call Systems and still having to do things twice – the leave and the call to sub-system. Which first? Does order make a difference, ie: Force Job# in leave request?  Auto-integration to workshop and Sub Entry … If you complete a leave should it  At time of recommendation or approval? – auto generate a Sub Entry?  New Workshop ID field.. Should it auto-generate a Workshop registration?.. If we were to automated this is your district ready? Is the quality of information you get from the leave ready? H/R Leaves