Difference between revisions of "Staff Exit Procedure"
Jump to navigation
Jump to search
m |
|||
Line 12: | Line 12: | ||
*'''First possible opportunity (or HR meeting, if not pressing)''' | *'''First possible opportunity (or HR meeting, if not pressing)''' | ||
** review whether we need to change [[locks]]/passwords | ** review whether we need to change [[locks]]/passwords | ||
− | ** Remove from restricted email lists | + | ** Remove from restricted email lists and server groups |
** Announce it to the community | ** Announce it to the community | ||
Revision as of 13:03, 13 July 2005
Because situations will vary, some of these steps will be more critical or time-sensitive in different cases. Documentation, however, is a must. These steps are specifically applicable to staff collective members, though most of them will be useful for interns/associate staff.
- On last day
- Get keys
- Recollect infrastructure equipment they might have
- Determine status: for example, quit/laid off/fired
document decision and supporting evidence in their personnel file
- Later communication with the individual
- Get them their last paycheck & discuss vacation reimbursement
if there's vacation backpay or other payment issues, be sure this is clear and documented in the personnel file - If applicable, figure out logistics of transition to new hire: can they do training?
- Get them their last paycheck & discuss vacation reimbursement
- First possible opportunity (or HR meeting, if not pressing)
- review whether we need to change locks/passwords
- Remove from restricted email lists and server groups
- Announce it to the community
- Ongoing
- Calls about former employees should go to members of the HR committee
- Information about unemployment should go to HR as well