Difference between revisions of "Staff Exit Procedure"
Jump to navigation
Jump to search
(Google is great!) |
|||
Line 3: | Line 3: | ||
*'''On last day''' | *'''On last day''' | ||
** Get keys | ** Get keys | ||
− | ** Recollect infrastructure equipment they might have | + | ** Recollect infrastructure equipment/other FG property they might have (laptop, credit card) |
− | ** Determine status: for example, ''quit/laid off/fired''<br/> document decision and supporting evidence in their [[personnel file]] | + | ** Determine status: for example, ''quit/laid off/fired''<br/> document decision and supporting evidence in their [[personnel file]]<br /> if applicable, request a letter of resignation including last day of work, last day on payroll, reason for leaving |
− | *'''Later communication with the individual''' | + | *'''Exit interview or Later communication with the individual''' |
** Get them their last paycheck & discuss vacation reimbursement<br /> if there's vacation backpay or other payment issues, be sure this is clear and documented in the personnel file | ** Get them their last paycheck & discuss vacation reimbursement<br /> 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? | ** If applicable, figure out logistics of transition to new hire: can they do training? | ||
*'''First possible opportunity (or HR meeting, if not pressing)''' | *'''First possible opportunity (or HR meeting, if not pressing)''' | ||
− | ** | + | ** Notify Paychex |
+ | ** Review whether we need to change [[locks]]/passwords | ||
** Remove from restricted email lists and server groups | ** Remove from restricted email lists and server groups | ||
** Announce it to the community | ** Announce it to the community | ||
+ | ** Remove from contact list in fgstaff and staff page on website | ||
*'''Ongoing''' | *'''Ongoing''' |
Revision as of 14:07, 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/other FG property they might have (laptop, credit card)
- Determine status: for example, quit/laid off/fired
document decision and supporting evidence in their personnel file
if applicable, request a letter of resignation including last day of work, last day on payroll, reason for leaving
- Exit interview or 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)
- Notify Paychex
- Review whether we need to change locks/passwords
- Remove from restricted email lists and server groups
- Announce it to the community
- Remove from contact list in fgstaff and staff page on website
- Ongoing
- Calls about former employees should go to members of the HR committee
- Information about unemployment should go to HR as well