Difference between revisions of "Staff Exit Procedure"
Jump to navigation
Jump to search
Line 29: | Line 29: | ||
* Review whether we need to change [[Keyholders|locks]]/passwords (Richard) | * Review whether we need to change [[Keyholders|locks]]/passwords (Richard) | ||
* Recollect infrastructure equipment/other FG property they might have (extra laptop or other special hardware, credit card, etc.) | * Recollect infrastructure equipment/other FG property they might have (extra laptop or other special hardware, credit card, etc.) | ||
+ | ** ID card (with or without trimet sticker) | ||
+ | ** Zone G parking permit | ||
** If they were a credit card holder, make sure all recurring transactions based on that card are transferred to another card, or other arrangements made. | ** If they were a credit card holder, make sure all recurring transactions based on that card are transferred to another card, or other arrangements made. | ||
* Remove access code from the alarm system: | * Remove access code from the alarm system: |
Revision as of 11:23, 19 January 2013
If an NPA or a Collective member is leaving, please use: Exit Procedure for NPAs or Exit Procedure for Collective Members
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.
Checklist
- Name of exiting staff member: ____________________
- Name of person completing checklist: _____________________
- Date checklist started: _____________________
Staff exit procedure | Date |
---|---|
As far in advance as possible:
| |
Two weeks before scheduled last day (or ASAP): Announce it to the community:
| |
Security:
| |
Social Media Accounts: Remove access to (when applicable):
| |
RT:
| |
In the database:
| |
Replacement and communications:
| |
Pay:
| |
E-mail:
| |
On the wiki:
| |
In scheduling software:
| |
Get feedback for the organization:
|