1. STATEMENT: All Districts (except TMSD) are using Workshops.. But to what extent (eg: POS.544 RETSD 3600+ people, 272 workshops): For Internal PD and do you build to F10 or F20, completion certificates? Are you building Leaves/Sub recs? For managing district internal ProD Day(s) excellent POS.545 & max items in POS.320 For extra-curricular Workshops? For Hearing/Flu Test Scheduling ₮Workshop updates since last conference ₮Review of workshops and integration to leaves and G/L charging ₮Reporting, Error checking

2. ₮POS.320 H/R Workshop Maintenance ₮Added option to limit to skill group (EIS.136).. hearing test (PE,MUS,MTC) ₮Added a “sub required” information field ₮Disallow initiators to also be facilitators; redundant ₮Don’t duplicate time/date schedule (text) with date/time fields!! ₮Consider Email message to personalize email for employees as they register ₮Reminder of waitlist Y/N/M ₮POS.542 H/R Workshop Hours/Account Detail Report ₮Added selection by workshop category ₮Added option to print start/stop times vs hours and account ₮Added registrant status to report ₮POS.564 H/R Workshop Attendees vs Sub Absences ₮Exclude workshops with no “standard” absence code defined; assumes no leaves/abs built as outside work day or on PD day ₮POS.544 Workshop Summary Report - for your Superintendents Team

3. ₮Workshop (POS.320) when approved creates a leave (EIS.316) which that night creates a Sub Record (SUB.001/002) ₮A change really means NEW workshop (POS.320) and copy applicants to new (POS.565) and cancel 1 st workshop POS.569 ₮POS.565 ‘P’ means admin will have to approve again versus ‘R’ meaning leaves will autobuild tonight. ₮ ‘D’elete Sub Records ₮PRO.525 to email workshop applicants of new date ₮QUESTION: Should we bypass the cancelling, i.e.: new CIMS option – change leave date, change Sub Records, report on Sub records that have Subs assigned ?????

4. ₮How well are facilitators using their functions.. Do you see this as important and useful for them to do this themselves? ₮Create lists ₮Do attendance ₮Edit Course content (THEY COULD) and/or browse/attach ₮Email ₮Manage waitlists because employees can also withdraw ₮IN-LIST: Allow Workshops to be added/maintained in AdminConnect. Thoughts? So dangerous especially now with integration to leaves … casual users Add??

5. ₮Workshop must have additional leave/absence code lines **describe all Job Codes that might register ₮Workshop must require approval ₮Nightly build looks to Registrant: must be at R status, approved and approval date equal to “today” ₮If workshop registration is marked for 2 locations then splits time in half and builds 2 leaves ₮Checks job codes indicated must match primary assignment, alternate OR employee has active assignment for job code ₮Checks leave record doesn’t already exist for same date, leave type and sub required code ₮Marks leave as recommended, will approve if leave type is defined as recommendation = approval (A)