Update Leave Policies
Why is this change being made?
Two changes are being recommended.
- GitLab's Unpaid Personal leave be removed from GitLab's leave offerings and,
- Allow team members the option to avail GitLab's PTO policy after Parental Leave.
GitLab's Unpaid Personal Leave is not a heavily utilized leave option since both pay and benefits are suspended and oftentimes the business is unable to support a team member's request. My recommendation is that this leave policy be removed as an available offering, and instead, team members utilize our other time away policies such as Time Off, Sick Time, Statutory leave offerings, etc.
Team members returning from Parental Leave were required to return to work for 7 calendar days before they could utilize GitLab's PTO policy. Utilizing Parental Leave is not the same thing as utilizing PTO, so the recommendation is that this requirement be removed. Instead, team members can coordinate PTO usage with their manager following the same guidelines outlined in the PTO policy (i.e. double the amount of notice as the amount requested), and if critical deadlines will be missed managers can ask them to choose different dates.
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-