Difference between revisions of "Exit Procedure for Collective Members"
Jump to navigation
Jump to search
(moved around ordering of checklist items so that it makes more sense) |
|||
Line 16: | Line 16: | ||
|- | |- | ||
|| '''Two weeks before scheduled last day (or ASAP):''' Announce it to the community: | || '''Two weeks before scheduled last day (or ASAP):''' Announce it to the community: | ||
− | + | * Regulars e-mail list (this should include paidworkers by default) | |
− | * Regulars e-mail list | ||
* Directors e-mail list | * Directors e-mail list | ||
|- | |- | ||
Line 31: | Line 30: | ||
|- | |- | ||
|| In RT: | || In RT: | ||
− | * Determine and note their status: for example, ''resigned / laid off / fired'' | + | * Determine and note their status: for example, ''resigned / laid off / fired''* |
* Update the RT Personnel Files. | * Update the RT Personnel Files. | ||
|- | |- | ||
Line 62: | Line 61: | ||
* Remove from the [[SFreekiWiki:Contact Info|contact list]] and [http://www.freegeek.org/about/staff/ staff page] on website. | * Remove from the [[SFreekiWiki:Contact Info|contact list]] and [http://www.freegeek.org/about/staff/ staff page] on website. | ||
* Remove from the [[Staff Collective Members]] page on the wiki. | * Remove from the [[Staff Collective Members]] page on the wiki. | ||
+ | * Remove from the [[Determining Seniority Policy| seniority list]] on the wiki. | ||
|- | |- | ||
|| In scheduling software, remove from future shifts, standard shifts (used to generate future schedules), and any meetings. || | || In scheduling software, remove from future shifts, standard shifts (used to generate future schedules), and any meetings. || | ||
Line 68: | Line 68: | ||
− | + | :<nowiki>*</nowiki> Document decision and supporting evidence in their personnel file on RT. If they resigned (left of their own accord) request a letter of resignation including last day of work, last day on payroll, reason for leaving. (This documents that Free Geek did not terminate them, and helps keep our unemployment payments low.) | |
== Ongoing == | == Ongoing == |
Revision as of 13:31, 2 April 2011
Collective Member Exit Procedure
Because situations will vary, some of these steps will be more critical or time-sensitive in different cases. Documentation, however, is a must.
- Name of exiting collective member: ____________________
- Name of person completing checklist: _____________________
Collective member exit procedure | Date |
---|---|
As far in advance as possible: Ask them if they want to continue their health care with COBRA. If they are interested, have them speak with Laurel. | |
Two weeks before scheduled last day (or ASAP): Announce it to the community:
| |
Security:
| |
In RT:
| |
In the database:
| |
Replacement:
| |
Pay:
| |
E-mail: Remove from restricted email lists and server groups
Does s/he moderate any email lists? If so, then pass them off to another. | |
On the wiki:
| |
In scheduling software, remove from future shifts, standard shifts (used to generate future schedules), and any meetings. |
- * Document decision and supporting evidence in their personnel file on RT. If they resigned (left of their own accord) request a letter of resignation including last day of work, last day on payroll, reason for leaving. (This documents that Free Geek did not terminate them, and helps keep our unemployment payments low.)
Ongoing
- Calls about former employees should go to members of the HR committee.
- Information about unemployment should go to HR as well.