Difference between revisions of "Exit Procedure for Collective Members"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | {{CollectivePhasedOut}} | ||
+ | |||
+ | |||
Collective Member Exit Procedure | Collective Member Exit Procedure | ||
Latest revision as of 16:27, 28 February 2013
The Free Geek Collective ceased to exist on February 28, 2013. For information on current staff, please go to Staff. For detailed information about the re-organization of Free Geek's management structure, please go to 2013_Restructuring_Documents.
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: _____________________
- Date checklist started: _____________________
Staff member 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:
|
- * 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.