Time Away Philosophy

On this page you will find GitLab’s philosophy to time away from work, communication guidelines, and information about Workday, our primary system for all time away management.

GitLab’s Philosophy to Time Away from Work

Why Time Away Matters

Time away from work isn’t just beneficial—it’s just as important as your work ethic and can contribute to productivity. At GitLab, we understand that regular breaks from work serve multiple important purposes:

  • Maintaining mental health and preventing burnout
  • Refreshing creativity and problem-solving abilities
  • Strengthening personal relationships and family connections
  • Gaining new perspectives that enhance your contributions
  • Demonstrating our commitment to sustainable, efficient and results-focused performance

GitLab encourages managers and leadership to model this by taking time off when needed and ensuring their reports do the same, fostering a healthy work-life balance across all levels.

When you return from time away, you bring renewed energy and fresh perspectives that benefit both you and GitLab. This makes time off not just personally restorative but prepares you to do your best work ever!

A Culture of Results and Sustainability

At GitLab, we measure impact, not activity. Our approach to time away reflects this fundamental value:

  • Flexible working hours mean you can step away when needed without guilt.
  • Regular life activities like going to the gym, taking a nap, grocery shopping, or helping loved ones are part of normal work-life integration.
  • No glorification of overwork – not taking time off is viewed as a weakness, not a strength.

Not taking time off is counter to GitLab’s values because:

  • It creates single points of failure – When team members don’t take time away, they become the only ones who understand their work. This makes the organization vulnerable when that person is eventually unavailable and prevents others from learning.
  • It hinders documentation and knowledge sharing – Regular absences create natural opportunities for documenting processes and sharing knowledge. Without these breaks, important information often remains in one person’s head rather than being accessible to the team.
  • It limits growth opportunities for others – When team members take time off, colleagues have valuable opportunities to step up, develop new skills, and demonstrate capabilities they might not otherwise have a chance to show.

We encourage all team members, especially managers and leadership, to set the example by taking time away when needed. By doing so, you create a culture where everyone feels empowered to disconnect and recharge.

Encouraging Meaningful Time Away

We believe that how you spend your time away matters too:

  • Health and wellbeing come first – We encourage taking time off for both physical and mental health needs proactively rather than waiting until you’re depleted. Taking care of your health is a legitimate and important reason for time away.
  • Public holidays – we encourage all team members to use their public holiday balance, and as a company that values Diversity, Inclusion & Belonging, team members have the flexibility to elect different dates and celebrate what’s important to them.
  • Extended breaks are encouraged – we recommend taking time off throughout the year in order to rest and recharge while also ensuring that you have communicated with your manager and have a plan for coverage while you are taking a break.
  • Community involvement is valued – whether volunteering, voting, or supporting causes aligned with GitLab’s values.

Transitioning Back Mindfully

Returning from time away can feel overwhelming, but how you re-enter work is just as important as how you leave. Consider these approaches to preserve the benefits of your time off:

  • Expect a transition period – It’s normal to need time to catch up after returning. Don’t feel pressured to work extra hours before or after your time away.
  • Return with intention and insights – When returning from time away, resist the urge to immediately catch up on all messages. Instead, begin by applying any reflections or insights gained during your break to high-impact work. This approach, articulated by John Fitch—working on your projects before working in them—allows you to make meaningful contributions while managing the natural adjustment period. Consider blocking time for strategic thinking or creative work before diving into tactical responses.
  • Reconnect intentionally – Schedule informal coffee chats with colleagues to reconnect, share experiences, and ease back into work relationships. In our all-remote environment, these connections require deliberate attention.

The way you return to work can determine how long the benefits of your time away last. A mindful transition helps you integrate rest and reflection into your ongoing work, rather than immediately negating those benefits.

Note: While this page focuses on our philosophy regarding time away, you can find detailed policies on all Time Off types (Paid Time Off, Sick Time, etc.) and Leave types (Parental Leave, Sick Leave, etc.) in their respective handbook sections.

Communicating (& Preparing for) Planned Time Away

At GitLab, we believe in taking time to recharge. This guide helps you prepare for time away while maintaining our values of collaboration, results, efficiency, diversity, inclusion & belonging, iteration, and transparency.

Communication Essentials

Timely & Transparent Communication

Timely & Transparent Communication

It’s expected that you provide your manager and team members who may expect to work with you with as much advance notice as possible about your planned time off. When requesting planned time off (i.e. PTO, Public Holidays, Volunteer time), provide at least twice as many days of advance notice as the duration of your planned absence. For example, a 3-day absence requires at least 6 business days of advance notice.

In line with our value of transparency, communicate broadly when you will be away. This helps team members manage time efficiently, ensures projects don’t slip through the cracks, and allows you to fully disconnect while away.

Important Note: Absence for 72 hours without notification could be deemed job abandonment.

Communication Checklist

Communication Checklist

  • Add an out-of-office automated Gmail response including your away dates and identify someone to contact in your absence.
  • Consider sharing your planned time off as an FYI in your team’s Slack channel(s), especially if you lead a team.
  • Schedule reminder messages in Slack to notify your team about pending items while you’re away
  • If your team has a specific scheduling calendar, update it with your time off plans.
Calendar and Meeting Management

Calendar and Meeting Management

  • Time away entries flow into Time Off by Deel and sync with your Google Calendar and Slack app, however, you will still need to decline any meetings you will not attend so organizers can make appropriate arrangements.
  • Cancel, move, or find coverage for any meetings you organize.
  • If you are an interviewer, review your calendar to address any scheduled interviews. Please review this handbook page and work with the recruiter and CES partner to reschedule or find a replacement interviewer.

Knowledge Transfer and Work Continuity

Documentation and Iteration

Documentation and Iteration

  • Document your knowledge and share it with others to help prevent Key-person-risk. This is especially true for “subject matter experts” or SME, people with specialized knowledge of a project, tool, or subject.
  • Create and share a Google Doc listing all important projects/customer interactions with relevant details:
    • Assign a covering team member for each project/customer.
    • Specify which calls/meetings require attendance during your absence.
    • Highlight high-priority topics and relevant issues.
    • Include a section for comments by covering team members.
Documentation Tips

Documentation Tips

  • Use symbols (e.g., ✅, ❗️) to help others quickly identify important entries.
  • Don’t rely solely on color coding, as this may create accessibility issues for people with color blindness.
  • Share documentation during team calls and asynchronously in Slack ahead of your absence to allow team members to review and ask clarifying questions.
Work Transition

Work Transition

  • Designate a backup individual for emergencies and brief them on key projects.
  • Transition and reassign in-progress work to another team member whenever possible.
  • Practice asynchronous communication by documenting decisions and updates in issues rather than relying on synchronous handoffs.

On-Call Coverage

Please see the On-Call page for information on how to handle scheduled leave for someone from the On-Call team.

Summary of Best Practices: Results-Focused Approach

  • Share PTO plans 2-3 weeks in advance or more when possible
  • For global remote teams, coordinate with others to ensure adequate coverage during busy periods and ensure that your team is able to cover your workload while you are away by providing documentation and transition plans in advance
  • Give team members advance notice at least twice as many days as your planned time off
  • Remember that at GitLab, we measure results, not hours—taking time to recharge is essential to doing your best work

Communicating Unplanned Time Away

Unplanned time away encompasses various situations that require immediate or unexpected absence from work, including illness, bereavement, emergencies, or other unforeseen circumstances.

If an unexpected emergency occurs please contact your manager via Slack or email as soon as possible if you will be unavailable or unable to work. This will allow your manager to confirm your safety and reassign any critical work during your absence. Please make sure you’ve added at least one emergency contact in Workday. We will only contact your emergency contact if we are unable to reach you via Slack, email or phone.

After notifying your manager, and as soon as reasonably practicable, please ensure you have:

  1. Entered your time off in Workday. If you aren’t sure how to classify your time-off within Workday (i.e. Out Sick, Bereavement, Emergency Leave), please reach out to the Absence Management team.
  2. Update your Slack and Google Calendar. If you have the Time Off by Deel integration this should occur automatically after entering your time into Workday. Note: the OOO event will not auto-decline your meetings.
  3. Set an out-of-office automated Gmail response including your away dates and identify someone to contact in your absence.
Types of Unplanned Time Away

Types of Unplanned Time Away

Please click on each of the time-off types listed below for more information.

  1. Sick Time Policy
  2. Bereavement Policy
  3. Emergency Leave Policy
Manager Responsibilities

Manager Responsibilities

If a team member has contacted you with an unexpected or emergency situation, you should:

  1. Confirm their safety and offer support
  2. Develop communication strategy with the team member
  3. Reassign or develop a coverage plan for the team member’s work as appropriate

For more information about manager’s responsibilities related to absence management, please visit the Manager Toolkit for Absence!

Workday: Single Source of Truth for Absence

Overview

All team members and managers (including those employed under a PEO and independent contractors) must log time away requests (PTO, Public Holiday, Out Sick, etc.) in Workday.

Workday and Workday Slack are the primary systems for all time away management. While integration with Time Off by Deel continues, all data flows from Workday to Deel.

It’s expected that you provide your manager and team members who may expect to work with you with as much advance notice as possible about your planned time off. When requesting paid time off, provide at least twice as many days of advance notice as the duration of your planned absence. For example, a 3-day absence requires at least 6 business days of advance notice.

For Workday questions, please use the HelpLab portal.

Key Features

Workday to Time Off by Deel Integration

Workday to Time Off by Deel Integration

Google Calendar Sync: Time away entries flow into Time Off by Deel and sync with your Google Calendar.

  • Calendar invites are sent to managers to track team absences (based on calendar dates, not adjusted for timezones).
  • Managers can decline and manually create correct calendar entries without affecting the time off request.
  • More information is available on the Team PTO Calendar handbook page.
Time Off by Deel Features

Time Off by Deel Features

  • Automatic Status Updates: Sets OOO status in Slack and activates “Do Not Disturb” settings (requires individual permission setup).
    • Important: This will not auto-decline all meetings on your Google Calendar.
  • Roles and Task Handoffs: Assign responsibilities to co-workers during absence. Accepted roles appear in Slack away messages.
    • Important: Request permission before assigning a #channel to a role to avoid creating excessive notifications.
  • Monthly PTO Reminders: Optional subscription to monthly prompts encouraging you to plan time off.
    • Sent on the first working day of each month.
    • To manage subscription: Go to Time Off by Deel app in Slack → Home tab → Notifications dropdown → Subscribe/Unsubscribe.
  • Note: Time Off by Deel syncs with Workday, Slack, and Google Calendar but it does not sync with GitLab.com. For absences over 48 hours, update your GitLab.com status with your out of office dates by clicking on your profile picture and selecting “Edit Status” (e.g., ‘OOO Back on 2025-04-28’). This status is publicly accessible and helps you get skipped by reviewer roulette.
Checking Team Availability

Checking Team Availability

To see who is out of office:

  1. Open Time Off by Deel in Slack
  2. Select “Who’s Out?” from the Home section dropdown
  3. Click “new search” to view absences by #channel, @usergroup, or @username
Additional Manager Requirements

Additional Manager Requirements

As a people manager, you may receive tasks through Workday. If you are going to be away from work for a prolonged period of time, you should set up a delegate in Workday to approve transactions during your absence. Please follow the instructions here, and remember to remove the delegate after returning to work!

Editing Time Off Entries

Editing Time Off Entries

  • Team members can edit future and past-dated entries up to 30 days in the past.
  • Entries that are more than 30 days ago will require a submission to the People Connect team via HelpLab.
  • Note: Not all requests will be approved; team members are responsible for maintaining accurate time away records.
Submitting Feedback about Workday

Submitting Feedback about Workday

If you have constructive feedback or recommendations related to Workday and Time Off by Deel, please submit it here.

Last modified October 14, 2025: Remove trailing spaces (3643eb9e)