Adding Headcount Validation Process to Handbook
Why is this change being made?
Adding the Headcount Validation Process to the handbook in order to launch as a TA led process in partnership with PBP, Finance and business leaders within the areas of the business without a strategy team (R&D, Marketing and G&A).
Collaborated with PBPs and FP+A in this google document to try and build a process in order to ensure TA has the details we need for all roles, can share with FP+A to update Adaptive proactively before a recruiter is allocated to the requisition.
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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 Ursela Knezevic