Skip to content

Update offboarding docs with Workday SSoT

A.J. Romaniello requested to merge workday-ssot-offboardings-1 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

In relation to https://gitlab.com/gitlab-com/people-group/peopleops-eng/employment-automation/-/issues/269, to update our documentation to accurately reflect upcoming changes to the offboarding process. In particular, we are getting rid of the google form and spreadsheet and moving this all into Workday. As well as changing when these issues are opened to be more accurate of the team members current location.

Notable changes that should be reflected in documentation:

  • No offboarding google form / spreadsheet
    • We now check for offboardings from Workday (and should be submitted there)
  • Last day of Work for opening offboarding issue
    • Monday-Thursday @ 4pm team members local time
    • Friday @ 12pm team members local time
  • Slack notification to offboarding channel
    • When any offboarding issue has been created, we send a notification to this channel linking to the opened issue.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by A.J. Romaniello

Merge request reports