Harrison

[shreythecray]

With members coming and going, our platforms and applications remain cluttered with inactive members. We are unsure of who is still a member and who has left. This outline is to ensure a smooth transition for both the offboarding member and the people team when members decide to leave.

DRI: @winniezhang-23 @[username of member that needs to be offboarded]

• DRI please review the eduflow for more clarification

Director/Manager Tasks

• [ ] Director/Manager inform PEA of who is leaving
• [ ] Update the PEA via private message about their current assigned task and if the member has offered an explanation to their decision to leave.

People Experience Associate Tasks (PEA)

Day 0:

• [ ] Reach out to member to confirm of the member's decision to leave (view sample message on eduflow). In message include they should set up a meeting with you the next following day.
  • [ ] Member sets meeting with DRI

Day 1-2:

During the meeting, please discuss the following questions:

• [ ] Document this in meeting repo under the offboarding folder, but if they would not like their name to be mentioned, please respect their wishes

• [ ] Ask the general questions

• [ ] Ask the specific questions

• [ ] Closing statement

• [ ] Any previously assigned work must be completed before the member is officially offboarded

  • [ ] Once they completed their assigned tasks and completed meeting with DRI, please start removing them from the following work space
  • [ ] Slack
  • [ ] GitHub
  • [ ] Google Calendar
  • [ ] Airtable
  • [ ] And any other platforms: Hubspot and etc.

Day 2:

• [ ] Inform director/manager and update the situation
• [ ] Change status under the Bit Project Directory Airtable to "Cancelled"
• [ ] PEA close this issue once the offboarding is complete