Commit 5759972e authored by Sarah Rogers's avatar Sarah Rogers 🐶
Browse files

Update info re contract templates and changes

parent 73c21907
Loading
Loading
Loading
Loading
+5 −20
Original line number Diff line number Diff line
@@ -5,30 +5,15 @@ description: "GitLab contract information and associated procedures."

## Contract Templates

GitLab's Team Member contract templates are accessible (for reference) within GitLab only [(here)](https://internal.gitlab.com/handbook/people-group/people-operations/people-operations/employment_contracts/#employment-agreements). The DRI for all GitLab Team Member contracts is the People Operations Team. Any changes to any contracts should be requested to the People Operations Team and will require approval from our Senior Director of Legal, Employment.
GitLab's Team Member contract templates are accessible (for reference) within GitLab only [(here)](https://internal.gitlab.com/handbook/people-group/people-operations/people-operations/employment_contracts/#employment-agreements). The DRI for all contract templates is the Legal, Employment team. Contracts are audited and updated on a regular basis. Any suggestions or requests for changes to employment templates should be made to the Legal, Employment team and will require approval from the VP of Legal, Employment. You can read [*how* to connect with Legal, Employment](/handbook/legal/employment-law/#connect) in the Handbook.

## Process for Suggesting Changes to the Contract Templates
## Team Member's Individual Contracts

Contracts are audited and updated on a regular basis. All suggested changes should be added to the current [Global Employment Contract Audit issue](https://gitlab.com/gitlab-com/people-group/people-operations/General/-/blob/master/.gitlab/issue_templates/global-employment-contract-audit.md). If **immediate** changes are needed to any one of the contract templates, follow the process below:
The DRI for individual team member contracts (once a team member is hired) is the People Operations Team. Any queries about a team member's contract should go to the People Operations Team by HelpLab ticket, and the query will be directed or escalated as appropriate.

1. Create a Contract Update Issue - The template can be found [here](https://gitlab.com/gitlab-com/people-group/people-operations/General/-/blob/master/.gitlab/issue_templates/Contract-Update-Add.md).
1. Open the relevant contract template, which automatically redirects to its original editable Google Doc.
1. If you have editing rights in the doc, change the document view to "Suggesting" mode (top right corner). If you do not have editing rights, you are able to make a comment on the doc or alternatively ping the People Operations Team member for assistance with having the suggestions added to the contract for approval.
1. Any edits that are made will then be made as a suggestion to the contract.
1. Once you have made the required changes, please tag the Senior Manager, People Operations as well as our Director of Legal, Employment to view and approve the relevant changes.
1. Once the changes have been approved, it is important to notify the Candidate Experience Specialist Team to update the contracts in Greenhouse.
**Approved changes or edits to the contract templates will be flagged to the CES team**

**No changes or edits should be made to the contracts without the required approval.**

The Senior Manager, Global Enablement reviews if all Greenhouse tokens are correct

1. See [here](https://drive.google.com/file/d/1rq4qTV5WYABDLMaAx76UqmjNwb008qVw/view?usp=sharing) for current set of tokens
1. Update tokens on the contract if applicable
1. Review in Greenhouse if all tokens are available (admin access is needed for that):
    - Log in to Greenhouse > click on: Settings (Gear Icon) > Offer Templates > click on: Upload New > Template Name: Country Name (OTE or no OTE) > Make sure `All Offices` `All Departments` and `All Employment Types` are all selected > Upload contract template as .doc file only > Save Template
    - Click on Test > Make sure all tokens have blue checks meaning the tokens are valid
1. If you are updating a contract that is already in use (not for a brand new entity), you need to be sure to delete the old version of the contract out of Greenhouse.
1. Delete the uploaded contract again, if it was just a test and final legal approval is still required
The Director, Talent Brand & Talent Acquisition Enablement will support a review to ensure all Greenhouse tokens are correct before an updated version of the template can be added to Greenhouse for use.

## Correcting an error in an issued employment contract