Skip to content

Added verbiage, clarified tasks and removed duplicate wording from relocation process

Sarah Hensiek requested to merge sh-relo-process-clarified-us-tasks-duplicate-removal into master

Why is this change being made?

Hi @ameeks

  • I added more context on the requirements needed for relocating for team members like discussed
  • removed duplicate wording regarding the address changes process and linked to the process in our internal HB instead
  • Included a link to the relo issue
  • Clarified the wording of some tasks
  • @alex_venter While updating I realised we also had this MR open regarding the US tasks and I copied the wording in, we can iterate on this as we test the process :)
  • We can add HR Savvy in copy via DocuSign and therefore save the step of encrypting the contract before sharing it with them
  • We previously confirmed that we don't need to use the personal email address when sending documents as this often resulted in delays and missed emails
  • I removed the "Relocating from the United Kingdom to the Netherlands" section as this process is followed for all entity to entity transfers and already mentioned here
  • I removed the mention of the AP issue since this is not required anymore with Navan

The next iteration would be to move the People Connect steps to our internal handbook to make this page easier to read, but wanted to get these updates out already as a first step.

FYI @gl-people-connect-team

Author Checklist

  • 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
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Sarah Hensiek

Merge request reports