Contracts, Probation Periods & PIAA

Maintained by:

On this page
Employment and Contractor Agreements
United States Employment Status
Letter of Adjustment
Probation Period
- Important steps during the Probation Period
- Probation Periods of Team Members Employed Through a PEO or an Entity
PIAA (Proprietary Information and Assignment Agreement)
- Approval for Outside Projects & Activities (AKA Exceptions to PIAA)
  - Steps as a current candidate (actively engaged in the hiring process)
  - Steps as a current team member
Contract Renewals
Netherlands Renewal Process
CXC Contract Renewal

This page contains GitLab's Team Member contract templates. The DRI for all GitLab Team Member contracts are the People Operations Specialist team. Any changes to any contracts should be requested to the People Operations Specialist team and will require approval from our Director of Legal, Employment.

Employment and Contractor Agreements

The following contracts are for reference only and are viewable by anyone in GitLab.

United States

Belgium

Netherlands

For team members legally able to work and live in the Netherlands, we should use the GitLab BV contract template. PEO contract templates should be provided by the PEO directly. We should not use GitLab BV or GitLab IT BV contracts for PEO models.

Temporary Employee Contracts:

Indefinite Employee Contracts:

Germany

Australia

New Zealand (subsidary of GitLab PTY Ltd, Australia)

GitLab PTY Ltd, Australia, without OTE
GitLab PTY Ltd, Australia, with OTE As of 1 July 2020, all team members in New Zealand will be employees of GitLab LTD Pty, the Australian entity. New Zealand new hires should use this New Zealand contract, which is governed by New Zealand law, even though the employer is an Australian entity.

United Kingdom

Canada

Japan

Other

Locations where we do not have an entity or Professional Employer Organisation or for anyone hired under Meltano, GitLab IT BV contractor agreements should _always_ be used. Kindly keep in mind that if you were hired under a GitLab IT BV or GitLab BV Contractor agreement, that we are continuously working towards a Scalable Employment Solution in these locations, and your contract will therefore change in future:

Process for Suggesting Changes to the Contract Templates

If any changes are needed to any one of the contract templates, please ping the Director of Legal, Employment, Senior Manager, People Operations or one of the People Operations Specialists to make the change(s). The following process needs to be followed by the People Operations Specialist team:

Create an Issue and tag the CES team with an explanation of what is being amended. This will act as a reference point in the future.
Open the relevant contract template, which automatically redirects to its original editable Google Doc.
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 Ops Specialist team for assistance with having the suggestions added to the contract for approval.
Any edits that are made will then be made as a suggestion to the contract.
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.
Once the changes have been approved, it is important to notify the Candidate Experience Specialist Team to update the contracts in Greenhouse.

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

United States Employment Status

Fair Labor Standards Act: Exempt v. Non-exempt Employees

Nonexempt employees are paid hourly and required to track and report all hours worked. If a non-exempt employee works more than 40 hours during a workweek, they are entitled to overtime pay. Overtime pay must have prior approval from the manager. Nonexempt employees are required to take two paid ten-minute breaks and one unpaid thirty-minute lunch break. As a fully distributed company, nonexempt employees are responsible for taking active ownership in ensuring they take the proper breaks. Please make the People Business Partner aware of circumstances where you feel compelled not to do so.
Exempt employees are paid on a salaried basis, do not need to track their hours, and are not eligible for overtime pay. These employees must not spend more than 50% of their time doing nonexempt duties to remain exempt.
For new positions, managers need to ensure the classification of the role is correct before sending an offer letter to the candidate. For guidelines on how to determine if a role is exempt or nonexempt, please reference the "Exempt vs Nonexempt Checklist" (which can be found on the google drive, but is only viewable to managers at GitLab). For positions that already exist, please verify the classification with People Ops Analysts.

Letter of Adjustment

If a team member changes roles at GitLab and the approval goes through Greenhouse, the process for a Letter of Adjustment is laid out in the Letter of Adjustment section on the CES Contract Processes handbook page. If a team member changes roles at GitLab and the approval goes through BambooHR, the process for a Letter of Adjustment is laid out in the Letter of Adjustment section on the Promotions & Transfers handbook page. For other instances such as a Relocation, the People Experience Associate will create a Letter of Adjustment according to the same parameters as listed in the Letter of Adjustment section on the Promotions & Transfers handbook page.

Probation Period

Upon joining GitLab, some team members (location-dependent, see the below table for detail about each location) will have a probationary period between 3 and 9 months. Common practice is for contracts in each country to have the maximum allowable probationary period. In case of relocation to a different country or change of contract, if a team member has continued service with GitLab (tenure with GitLab has been uninterrupted) and they have already passed the probationary period of their original location or contract, they do not need to go through the probation period of their new location or contract. As per the onboarding process a notification in BambooHR would have been created.

The People Experience Team is responsible for managing the probationary period process internally (communication with the team member, their manager, confirmation of probationary period completion, and updating BambooHR), while the People Operations Specialist Team is responsible for managing relationships with legal counsel externally on a global scale to ensure compliance and iteration. If an exception request is made to end a probation period early, this should be escalated by the team member's manager to a skip-level and the People Business Partner via email. We will then evaluate the risk, performance and overall reason for the request. Further escalation to Legal might be necessary as well as decision making on how to proceed. There should be no expectation of approval.

Important steps during the Probation Period

For Managers

Managers are responsible for monitoring and specifically reviewing performance halfway through the probation period of their direct report.
If underperformance is an issue, or there is any hesitation regarding the successful completion of a probation period, this should be discussed immediately with the relevant People Business Partner.
14 days prior to the end of their direct reports' Probation Period, the manager will receive an email from the People Experience Team, reminding them that their direct reports' probation period is coming to an end.
The Hiring Manager will respond confirming their approval of their direct reports' completion of their probation period, or that they are in discussions with their People Business Partner.

For People Experience Team

The People Experience team will be cc'ed on an email that is sent automatically as per the current email automation
- If the email is not automatically sent out, then the People Experience Associate will need to create an issue and assign it to the People Group Engineer to triage.
From this email, they will log the team members name, manager's name, and probation period end date in the Probation Period tab of the People Exp/Ops Task Tracker
Once the Manager has confirmed that they are satisfied with their direct reports' performance, the People Experience Associate will send a confirmation email to the team member to notify them that their probation period has been completed. The PEA will cc people-exp@ gitlab.com and the manager.
The email thread between the People Experience team and the manager should be uploaded to the Contracts & Changes folder of the Documents tab of the direct reports' BambooHR profile.
If no response is received from the manager after 7 days, the People Experience Team will check in BambooHR if there has been an manager update or change and follow up with a second email and a private message in Slack.
If there is still no response after 10 days, the People Experience team will create a private Slack channel including the manager and relevant People Business Partner to get the needed confirmation.
If for some reason, a manager is not contacted prior to a team member's probation notice completion, the manager must still be contacted to notify them that a team member's probation period is over, using the relevant email template. This thread must be saved in the team member's BambooHR profile, in their Contracts & Changes folder.

Probation Periods of Team Members Employed Through a PEO or an Entity

If the team member is contracted or employed through one of our PEOs or alternatively an entity, the People Experience Associate will also need to reach out to the appropriate point of contact for that PEO to inform them of the team member's probation period completion. That information is listed in the Entity & Co-Employer HR Contacts folder within the 1Password People Ops Vault.
If a manager is requesting an extension of a team members probation period who is employed via a PEO, the People Experience Associate will need to send an email to the appropriate point of contact to request an extention of a probation period.
Save this email to the BambooHR profile.
Update the BambooHR Job Status table with the new probation period.

Current Entities and Co-employers with Probationary Periods:

Country	Probation Period	Notice during probation	Notice after probation
Australia	6 months	1 week	1 month
Austria	1 months	No notice	Less than 2 years is 6 weeks notice. 3-5 years is 2 months.6-15 years is 3 months. 16-25 years is 4 months. 25 years and above 5 months.
Brazil	3 months	No notice, but there are termination costs. Employers must pay team members half of the the time remaining until the end of the probation period. (Example: Start date 2020-04-01, termination 2020-06-20, 10 days remaining until meeting 90-day probation period. Payment due for 5 days.)	30 days for less than one year's tenure. This is increased by 3 days per additional year of service up to a maximum of 90 days. (Ex. A team member with 3 years + 2 months of service needs 36 days' notice.)
China	3 months	3 days	N/A
Denmark	3 months	1 month	1 months’ notice until resignation within the first 6 months after commencement of the employment (probation period included), 3 months’ notice until resignation before the end of 3 years’ employment, 4 months’ notice until resignation before the end of 6 years’ employment, 5 months’ notice until resignation before the end of 9 years’ employment, 6 months’ notice until resignation after the end of 9 years’ employment.
France	3 months	2 weeks	For indefinite term contract: Executive level must have 3 months notice, all others 1 month. For fixed-term contract: No notice.
Germany	6 months	2 weeks	4 weeks
Hungary	3 months	No notice	30 Days
India	6 months	1 week	30 days
Ireland	6 months	1 week	1 month
Italy	6 months	No notice	Executives: 6 months (less than 4 years of service), 8 months (between 4-10 years of service). All other team members: 60 working days (<5 years of service), 90 working days (between 5-10 years of service), 120 working days (more than 10 years of service).
Japan	6 months	One week	30 days
Kenya	6 months	7 days	1 month
Latvia	3 months	1 month	1 month
Mexico	3 months	No notice	No notice
Netherlands	1 months	1 day	1 month before contract end
New Zealand	6 months	N/A	N/A
Philippines	6 months	30 days	30 days
South Africa	6 months	1 week	1 week if the employee has been employed for six months or less. 2 weeks if the employee has been employed for more than six months but less than one year. 4 weeks if an employee has been employed for one year or more.
Spain	3 months	No notice	15 days
Switzerland	3 months	2 days (or no notice if there are grounds)	7 days if during months 4-6. 30 days after 6 months of employment. There can be no notice if there are grounds for an immediate offboarding.
United Kingdom	6 months (For any team member with a contract issued after April 22, 2020. For contracts issued prior to April 22, 2020 a 3-month probation period is applicable.)	1 week	1 month

Countries without Probation Periods:

Country	Notice
Canada	2 weeks
Israel	30 days
South Korea	1 month
Turkey	2 weeks
USA - Federal	2 weeks
USA - Inc	2 weeks

PIAA (Proprietary Information and Assignment Agreement)

GitLab strives to help its team members maintain the ability to work on projects that are unrelated to GitLab’s business, including other open-source projects. Our PIAA does not grant GitLab any rights to any creations that you may make that are not related to GitLab's business or the work you do for GitLab. That is, you are free to develop those creations without requesting approval in advance from GitLab.

If your employment contract was created prior to November 2017, we have created an amendment to the PIAA agreement which can be viewed here. It amends the 2A section of the PIAA. Please email the People Experience team who will complete and stage the document for signatures. The Amendment will first be signed by our Senior Director, People Success and then the team member.

Approval for Outside Projects & Activities (AKA Exceptions to PIAA)

Before beginning work on outside projects, second jobs, additional work - paid or unpaid, that could potentially impair your ability to perform your obligations to GitLab or could be deemed a conflict of interest, you must obtain approval in writing from your Manager, and further approval from your E-group leaders as needed, facilitated by the relevant People Partner for your department. This is also required to those at the offer stage who have yet to start their employment with GitLab.

Steps as a current candidate (actively engaged in the hiring process)

Once the candidate receives their employment agreement, they will list all outside projects and activities in Exhibit A of the PIAA section.
When the Candidate Experience Specialist receives the signed contract, they will review to see if the information was added to Exhibit A of the PIAA or if the candidate entered No or None. If content was entered, CES will notify the People Experience team in the #people-exp_ces private slack channel with the link to the candidate's Greenhouse profile.
The People Experience team will complete the approval process as described in the onboarding processes.

Steps as a current team member

Team member sends their request via email to their direct manager for approval and copies their relevant People Business Partner (PBP). Note: PBPs are not the decision-makers, but can flag any concerns or questions.

Information needed in the email:

Project name (links to relevant website if available)
Goal of the project/organization
GitLab clients and/or team members who are involved in the project and scope of their involvement. (If applicable, please include tech stack used)
Estimated time investment per week (in hours)
Employment status/role in relation to the outside project (if applicable)

The manager will ask any additional questions if necessary. A manager may not approve a request for outside projects or activities for a variety of reasons, including team member performance. If the manager approves, they will then confirm this in the thread and add the applicable Director-level leader to the thread, for their review and approval. If the direct manager is also at a Director-level, they will add the next level leader (VP or C-level as appropriate) to the email thread for review and approval.
If the Director/next-level leader feels additional review and approval is needed, they will then add the next level leader (VP or C-level as appropriate) to the email thread. If this is not deemed necessary, the Director/next-level leader will respond indicating their approval. Note: A minimum of two leaders must approve all outside projects. Direct manager and Director-level are the usual levels. If the direct manager is at a Director-level, an additional level must approve.
If the next level leader (VP or C-level) feels additional review and guidance is needed, they will add the Director of Legal and any other relevant leader to the thread.
If a decision is made to approve and all approvals are documented, the PBP will forward the email to the People Operations Specialist team at peopleops@ gitlab.com for processing.
If a decision is made to deny, the People Business Partner will relay this to the team member, and then will forward the email to the People Operations Specialist team at peopleops@ gitlab.com for processing.
The People Operations Specialist will save the entire thread as a pdf to the team member's BambooHR profile in their Contracts and Changes folder.
The People Operations Specialist team will then respond confirming receipt and state that the entire thread has been saved in the team member's BambooHR profile.
For team members employed in the Netherlands, confirmation will be given in the form of the Authorization Letter. This letter must first be sent to the relevant E-group leader for signature, then to the team member. Once signed, this will be saved in the team member's BambooHR profile in the Contracts and Changes folder.

For any approved outside activity in which the GitLab team member will use their GitLab account, this activity must be stored in a separate, personal project. All other work completed as part of their GitLab employment or contract should be stored in a GitLab namespace with a GitLab copyright.

Contract Renewals

The below process can be used for the following:

Temporary contract to indefinite contract
Temporary contract to temporary contract (after the initial contract expires)
Contract update for invoice purposes due to individual incorporation of an entity Note: In most cases this process will apply specifically for team members in the Netherlands.

When creating a new contract, if it is to be for 12 months, that timeframe is always to be written as (for example):

Jan 1, 2010 to Dec 31, 2010
Feb 20, 2004 to Feb 19, 2005

When renewing a contract, if it is to be for 12 months, the timeframes are at be seen as (for example):

First 12-month contract starts on June 14, 2019. That entails that the contract ends on June 13, 2020.
Second 12-month contract will start on June 14, 2020 and end on June 13, 2021.

Using the Relocation & Contract Renewal's tracker view the upcoming team member contract expiry date. On the sheet you will see the People Operations Specialist owner, if you are the owner be sure to note the end date and start the below process 2 months before the end date.
Take note of the team members details and reach out to the team members manager via email using the following template, be sure to CC the team members People Business Partner.
Once you have received confirmation on next steps from the team members line manager be sure to save the thread under the team members profile on BambooHR.
Using the correct contract template from the templates folder complete with required team member details. These details can be found on the team members BambooHR profile.
Do not keep the Stock Options line in the Key Terms section, unless additional shares are being given.
When you have a completed contract be sure to allow a team member to peer review it for you. This can be done by posting the document link in the People Ops private slack channel. Indicate that you are reviewing it by using the 'Eyes' emoji.
Once reviewed, stage the contract for signing in HelloSign.
Ensure that the GitLab signatory is the first to sign, followed by the team member. This can be done by selecting the assign signing order option.
When signed by both parties, save the contract to the team member's BambooHR profile in the Contracts & Changes folder.
Update BambooHR to reflect the correct Job Information. Ensure the new contract information is added along with an end date if applicable.
Notify the Total Rewards team so that they may audit any BambooHR changes.
DE (Germany) contracts only: If no payroll information is on file, send a payroll questionnaire from HelloSign. Once completed, upload to BambooHR and email nonuspayroll@ gitlab.com to notify.

Netherlands Renewal Process

Two months before the contract ends, the People Experience Associate sends an email to the manager and People Business Partner of the team member, notifiying them that their first 12-month contract is ending.
- Set Due Date to give you 3 weeks to stage contract
Best practice and procedure at GitLab is to supply a second temporary 12-month contract. After two consecutive year-long temporary contracts, if the team member is in good standing, they are given an Indefinite Agreement beginning at the team member's third year with the company.
The Manager has then 3 weeks to evaluate the performance of the team member and discuss the planned course of action with the People Business Partner
At least 1 month before the end of the contract, the manager informs the People Operations team on whether to extend the contract and for what term.
At least 1 month before the end of the contract, the manager informs the team member of the extension or not. The People Business Partner can help with providing guidance on the messaging.
The People Operations team documents the emails in the Contracts & Changes folder in BambooHR.
If the contract extension is approved, the People Operations team creates the contract and stages it via HelloSign for the team member and Senior Director, People Success (on behalf of CPO if there is no current CPO) to sign.
Note: A second probation period should only be implemented if the team member's new contract reflects the start of an entirely new role. If the contract is simply a continuation of employment in the current role, a second probation period should not be applied.
The People Operations Team will then password-protect the signed contract and email to HR Savvy.

Note: A team member cannot have more than three temporary contracts with the same employer in a row. If a fourth contract is offered by GitLab then it must be a permanent one.

Important: Best practice for team members in the Netherlands is to issue two consecutive 1-year Temporary Contracts prior to moving to an indefinite contract. After the completion of two consecutive 1-year Temporary Contracts, we move to the indefinite contract. Should a team member request an indefinite employment contract after the initial 1-year Temporary Contract, approval via email should be requested based on performance from the team member's manager as well as the People Business Partner and a Division leader.

CXC Contract Renewal

CXC contracts are issued on a yearly basis, with contracts expiry after one year. CXC remains the responsible PEO for ensuring the contract renewal is completed for each team member.

CXC will make contact with team members 2 weeks before their contracts are due to expire.
CXC will create renewal contract and send for signing to the relevant team members.
Once signed, CXC will send the renewed contract to GitLab.
The People Operations Specialist or People Experience Associate will update the relevant employment status to the renewed dates in BambooHR and file the renewed contract in the Contracts & Changes folder.

Standard practice is to automatically renew CXC contracts. The offboarding process will apply should a team member be terminated voluntarily or involuntarily.