Internal Management Members: Chief Legal Officer, Chief Executive Officer, Acting CISO
Meeting Process
The Staff EBA to the CFO is the DRI of scheduling the quarterly Audit Committee meeting in conjunction with the Chairperson, Management DRI and their Sr. EBA
All Audit Committee materials being reviewed during the meeting will be uploaded into Boardvantage 5 business days prior to the Committee meeting by the Corporate Paralegal. Committee members will be notified of such by the Management DRI.
Audit Committee meetings are attended by:
Internal Management Members: Chief Executive Officer, Chief Finanical Officer, Chief Legal Officer (equity compliance)
Meeting Process
The Staff EBA to the CEO is the DRI of scheduling the quarterly Compensation and Leadership Developement Committee meeting in conjunction with the Chairperson, Management DRI and their Sr. EBA
All Compensation and Leadership Development Committee materials being reviewed during the meeting will be uploaded into Boardvantage 5 business days prior to the Committee meeting by the Corporate Paralegal. Committee members will be notified of such by the Management DRI.
Compensation and Leadership Development Committee meetings are attended by:
Compensation & Leadership Development Committee Schedule: The 2022 schedule of Compensation & Leadership Development Committee meetings is as follows:
Management DRI: Chief Legal Officer
Meeting Process
The Staff EBA to the CEO is the DRI of scheduling the quarterly Nominating & Corporate Governance Committee meeting in conjunction with the Chairperson, Management DRI and their Sr. EBA
All Nominating & Corporate Governance Committee materials being reviewed during the meeting will be uploaded into Boardvantage 5 business days prior to the Committee meeting by the Corporate Paralegal. Committee members will be notified of such by the Management DRI.
Nominating and Corporate Governance Committee meetings are attended by:
Management DRI: Chief Product Officer
Meeting Process
The Staff EBA to the CEO is the DRI of scheduling the Mergers and Acquisitions Committee meeting in conjunction with the Chairperson, Management DRI and their Sr. EBA
All Mergers and Acquisitions Committee materials being reviewed during the meeting will be uploaded into Boardvantage 5 business days prior to the Committee meeting by the Corporate Paralegal. Committee members will be notified of such by the Management DRI.
Mergers and Acquisitions Committee meetings are attended by:
The board meeting is all remote because hybrid is a bad experience for remote participants, see video calls point 10.
The Staff EBA to the CEO shall ensure that there are separate calendar invites for all attendees within each session, all including exact session start and end times, the appropriate Zoom link, and links to the agenda document. Any supplemental materials are required to be linked in the agenda document for each session:
board@
alias, Board Observers, and the outside legal firm. Any exceptions must be confirmed by the CLO and relayed to the Corporate Paralegal before shipping.This section is updated after every Board Meeting by the EBA to the CFO for the next Board Meeting.
GitLab uses Nasdaq’s Boardvantage (NBV) portal for the electronic dissemination and storage of materials relating to GitLab’s Board Meetings.
For a more detailed overview of navigating the NBV portal, please click here to view the Internal Reference Guide.
The Sales Slides should always include:
The Finance slides are as follows:
The CEO is responsible for submitting a memo to the BoD in advance of the Board meeting. The memo captures GitLab highlights from the previous quarter, CEO OKRs for the coming quarter, and other topics that are top of mind for the CEO. The CoS to the CEO supports the CEO by creating an initial draft and sharing it with the CEO a week before the final draft is shared with E-Group. The memo should have online tests for readability before they are finalized or shared with the CEO. A tool, such as https://readable.com/, can be used.
We usually have a Board Dinner on the evening before a Board Meeting. The EBA to the CEO is responsible for coordinating this dinner. Board Members, Local E-Group members, and the CoS to the CEO are all optional attendees. Bios for attendees of the Board Dinner should be sent by the EBA to the CEO 3 business days in advance of the Board Dinner.
Each quarter, E-Group can choose to invite an additional team member as a Key Talent Guest. If this is desired in a specific quarter, at least a month before the dinner, the CoS to the CEO will gather nominations and ensure that E-Group has identified an invitee. Criteria for consideration includes:
Once the Key Talent Guest has been identified, it is the relevant E-Group team member's responsibility to ensure that managers of this person are aware of the invite. The EBA to the CEO will then confirm that the guest is able to join. If not, the invite will go to the runner up. Once a Key Talent Guest is confirmed, the EBA to the CEO should enter their name in the Key Talent guest list.
GitLab will cover this person's travel expenses. A person's location will not be considered in the selection criteria though the person's travel must be allowed under GitLab's travel policies and guidelines.
As part of joining the dinner, the Key Talent Guest should come prepared to discuss:
Though no formal presentation is required, the Key Talent Guest should advise on how they want to discuss these topics with the Board and E-Group and coordinate with the EBA to the CEO. The EBA to the CEO will ensure that the Key Talent Guest has dedicated time at the dinner.
Past and future Key Talent Dinner Guests are listed below.
Date | Key Talent Guest |
---|---|
2021-09-29 | David DeSanto |
2021-12-13 | Sherrod Patching |
2022-03-21 | Christine Lee |
2022-12-12 | Sherida McMullan |
Board Members often engage with team members on individual topics. Examples include conversations around security, development priorities, or sales pipeline. When this happens, and a subset of Board Members are involved, the E-Group leader responsible for a specific topic should provide a brief, email recap to all Board Members. When the information can be shared with all of E-Group, the individual email addresses of E-Group members should be CCed. When the information cannot be shared with all of E-Group, folks who should have context within E-Group should be CCed. This helps to ensure that all Board Members and relevant E-Group members are kept in the loop.
The Board Recap should include the following:
We don't include links to the handbook or full meeting notes as Board Recaps are designed to give the Board Members a quick overview. Emails can be sent from E-Group Members to board@gitlab.com. Note: a limited group of GitLab team members, including E-Group team members, have the permissions required for reaching the Board through this email alias. The Board cannot email e-group@gitlab.com directly, so individual team member email addresses should be added on Board correspondence.
Board Members may request additional time for a deep dive on a specific topic. This ask often occurs during a Board Meeting. In these instances, the E-Group owner most responsible for the topic is the DRI for preparing for and scheduling the follow up conversation. The Board Members who asked for the meeting should be in attendance. All Board Members should be added to the invite as optional. These meetings should usually be scheduled for 50 minutes. When appropriate, these meetings should be recorded and posted to the NBV portal. The loop should always be closed with a Board Recap to the entire Board.
We will have one Board member per quarter conduct an AMA (Ask Me Anything) session with the GitLab team. AMA’s are 25 minutes and live streamed to GitLab Unfiltered on YouTube. These AMA's are scheduled by the Staff EBA to the CEO.
Assuming GitLab adopts a three class structure, a Director can belong to Class I, Class II or Class III. Some of our Directors will be in Class 1 and will be up for reelection as early as the first year the company is public, while other Directors will not be up for reelection until 2 or 3 years after the company is public. The decision as to which director is in which class is typically made close to when a company goes public. Various factors in making this determination are taken into consideration; for example, some VC Directors may prefer to leave the Board earlier in the public company lifecycle due to the number of commitments or requirements imposed by their respective funds.
Board member onboarding from an internal processes checklist perspective:
To be completed prior to onboarding:
Board member onboarding from a GitLab orientation perspective:
New Director will be be provided with: