Taking time off#

In general, 2i2c inherits its benefits and paid time off (PTO) policy from Code for Science and Society. These policies are detailed in the CS&S Employee Handbook. This page describes some 2i2c-specific practices that are applied in addition to the CS&S policies.


  • Normalize our PTO policies across countries, so that team members don’t get different PTO depending on their country of residence.

  • Choose PTO policies that minimize the chance that a team member will take fewer days off per year than the minimum in their country.

  • Do not apply hard limits and restrictions, but instead encourage soft minimums and coordination amongst team members.

  • Encourage a focus on contributions to the team and organization over number of days worked.

  • Base our numbers off of objective data where possible.


  • 2i2c does not have a limit on the number of days you may take off each year.

  • We recommend that all 2i2c team members take at least 40 days (8 weeks) annually (pro-rated if you started work mid-way through the year).[1]

  • We do not treat national holidays differently from vacation days.

  • You must open an issue to tell others about your intention to take time off, and you must add your intended time off to the Team Leave Calendar.

Guidelines for taking time off#

  • Don’t ask, do tell. Tell team members as early as possible before you take time off. A good rule of thumb is to tell others in advance twice as long as you’ll be off (so for 2 days, let people know 4 days in advance; for 1 week, let others know 2 weeks in advance, etc).

  • Be mindful of the team. We strive to build team processes that give us the capacity for team members to regularly take time off, but please consider the team’s obligations around the time you’re taking off. For example, during important team meetings, particularly high-stress events, etc.

  • Discuss with others if there are objections. If a team member believes that your time off would be unfairly harmful to the team, they may object via commenting in the github issue for your time off. In general, team members should only object if a person’s time off would significantly harm 2i2c’s ability to accomplish its mission. If there are objections, we should aim to resolve these via discussion amongst the team. However, ultimately it is the decision of the person requesting time off.

  • Weekends and holiday seasons are exceptional. We do not expect team members to work during weekends, and we also expect that many team members may be off simultaneously during heavy holiday seasons (in particular, the end of the calendar year). This may create tension, as we are running services that run 24/7. We signal our intent to protect holidays and weekends by advertising reduced responsiveness with no promises during these times. If we feel obligated to engage with a community “outside work hours”, we should recognize this and ensure the people doing this work feel valued and fairly treated.

Process for taking time off#

Open a GitHub Issue in the 2i2c-org/meta repository using the “Time off” template. Follow the steps in that template.

Dates are inclusive

When you’re specifying an end date for your time off, it should be the final day you’re away. Not the first day that you’re back.

Sick and personal leave#

2i2c team members should always prioritize their own well-being and health. If for any reason you must take a leave for personal reasons, you are encouraged to do so. Follow the process described above in this case - you are welcome to describe your intention however you wish. In this case, our guidelines around letting others know ahead of time are somewhat relaxed, as sick leave may happen unexpectedly. Just do the best you can, and try to balance your own constraints with respect for the team’s bandwidth and planning.

Expected end-of-year time off#

The final 14 days and the first 3 days of the year are “expected time off” for all of 2i2c.

During this time our organization operates at a reduced capacity and with greatly diminished commitments to our service level objectives.

Our support and operational roles are still staffed, but with greatly reduced expectations around responsiveness and resolution. Team members can use this time as they wish (including continuing to work), but we wish to set the expectation with internal and external partners that we will be less responsive.

Here is our policy during this time:

Unknowns to resolve#

  • This process is likely too informal if our team significantly scales in size and complexity.

  • Our process for having group discussion if there’s an objection to time off may be under-specified, and we may need to make it more formal if this creates tension.


2i2c’s PTO policy is inspired by several other remote organizations. In particular, Buffer, GitLab, and BaseCamp.