Restating Some DE/IDS Policies

After getting updated info from HR I thought it wise to take a moment to clarify or restate DE/IDS policies that you're probably already aware of. I'm summarizing what is stated in greater detail/more sophisticated parlance on the HR Web site. However, I don't want everyone to fret; just consider whether any of these apply to you, and alter your behavior if necessary:

1. Personal leave time must be requested and approved of your direct supervisor; sick leave requires notification of a responding human being at the time of leave. See IDS Out of Office Policy and IDS Leave Policy for more details.


2. For FT employees, all leave time must be entered in Banner through UVLink during the pay period in which it was taken.


3. For "exempt" employees there is neither overtime nor comp time; "non-exempt" employees must have any overtime or comp time pre-approved in writing.


4. Office/work hours may only be spent on DE projects. FT exempt and non-exempt employees get paid breaks, but lunch hours are on your own.


5. No use of College equipment for personal or side projects.


6. Each team member's work areas should be clean, organized, and professional looking especially so if it is visible to our clients or stakeholders.

Thanks for reading, and let me know if you have any questions!

Task Protocol: Reply on Completion

Just a few reminders/requests:

Everyone:

1. If an ID e-mails a task or a request directly to you please e-mail (reply all) when that task is completed. If it is a significant task you should ALSO add it to your Google Docs Task List.



2. It would also be helpful if you e-mail the responsible party upon completion of tasks in your Google Docs Task List in addition to marking them as "done" with the due date.



3. If you receive a request directly from an instructor or another DE unit (e.g. Design Center or Service Center) please CC the ID/staff member who is responsible for that course or project (Janel, Marc, Ken or myself).

IDs:

When an instructor request is completed don't forget to reply to the instructor directly.

1. I also recommend that when we reply to confirm completion of requests that come in from another DE unit (e.g. Design Center or Service Center) we CC the instructor to ensure they get the information.



2. Finally, when a developer has completed a task successfully, please verify this on their Google Docs Task List by cutting/pasting it to the Completed Tasks sheet.



3. If you have other ideas/alterations to help us keep instructors in-the-loop, please Comment here.

Out of the Office Policy

John e-mailed out a memo to the DE Directors this afternoon indicating that all absences should be

1. approved by your supervisor
2. reported to those who work under you

This is not much different from the existing IDS Leave Policy, but John does reiterate that team members should notify their staff of any unscheduled absence out of common courtesy.

Even if you don't have staff who report directly to you, the IDS Leave Policy asks that you inform "all team members who may be affected by your absence" if you're not going to be in as scheduled.

For my own part, I want to remind all IDS & DC team members that my weekly schedule, which does include frequent meetings and events both on- and off-campus, is nearly always up-to-date and shared with all of you in the Groupwise calendar. While it is not feasible for me to notify everyone each time I leave the office, you can discover my whereabouts by looking at my Groupwise appointments if you need me. If my Groupwise calendar is not accessible to you, or you don't know how to view my schedule in Groupwise, please let me know.

Additionally, you can count on me letting Travis and Janel know if I ever close up for the day unexpectedly.