Sabbatical

Fifteen days of annual leave is less a resource for resting than a resource for rescheduling life. Taken a day at a time, or strung together, it comes to a week. A week is exactly long enough that opening your inbox on the first morning back returns you to where you were.

So people who have been somewhere four or five years start saying the same thing. It isn't that the work became unpleasant; it's the sense of the same work repeating, and there is no gap in the policy long enough to break that sense. An engineer leaving Pagedeck after four years put it directly: they wanted a month off and then to come back, and with no such option available, quitting was the version that existed.

When the company works out what that cost, the number is large. Refilling the seat took three months of hiring, and three more before the new person carried their own weight. For half a year that seat produced about half of what it had, and the hours colleagues spent bringing someone up were on top of that. A one-month gap got traded for a six-month one.

A sabbatical builds that option into policy ahead of time. It opens a third box so that someone who needs a break isn't choosing between resigning and carrying on. Fixing the eligibility and the length as numbers is the shape of the policy — written any looser, each case becomes an individual negotiation, and only the people willing to ask end up using it.

Writing five numbers into a document is essentially the whole policy.

1. Eligibility. Four or five years of service is the common threshold. Written as recurring — every five years, say — someone who stays a long time can plan a second one.
2. Length. Four to eight weeks is typical. Shorter than four and it behaves like the week described above; longer than eight and the range of work someone else has to pick up and finish grows considerably.
3. The relationship to annual leave. State explicitly that this is separate. Built as a deduction from annual leave, it's a new name for taking existing days in one block.
4. Paid or unpaid. Paid means the company carries both the salary and whatever coverage the absence needs. Written as unpaid, it stays in the handbook and almost nobody uses it, because only people who can absorb a month without income can — which quietly turns a tenure benefit into a benefit for whoever has savings.
5. Return conditions. Say that the person comes back to the same role on the same terms. Some companies attach a minimum period of service after returning; stretch that past a year and the policy starts to read as a contract.

One condition is harder than any of the numbers. Vacating a seat for a month requires that someone else can pick up what that person holds. Where an area only one person understands remains, they can meet every eligibility rule and still not go, and the policy lives only on paper. Companies where this actually runs are generally companies that already have documentation and distributed ownership.

Three places. The first is holding onto people who have been around a while. Employee retention is the work of making people want to stay, and what a fourth-year employee needs differs from what a first-year one needs. Early on, the question is whether there is something to learn. At four years, the question is whether this pace is sustainable for five more. This policy is one of the available answers to the second question.

The second is heading off burnout — the depleted state that follows sustained overload — before it arrives. Once someone is in that state, a few days off doesn't return them. A policy where eligibility arrives automatically means someone already worn down doesn't have to raise their hand; their turn simply comes. A policy that requires raising a hand gets used only by people who still have the energy to raise one.

The third is exposing where the organization is concentrated. Take one person out for a month and everything that had pooled around them becomes visible: release permissions held by a single account, one person who knows a particular customer's history. In this respect a sabbatical differs in kind from a time-based policy like flexible hours, where each person sets their own start time and no handover is required at all. A month away is impossible without one.

"Two people are eligible next quarter and they're on the same team. Let's see if one can move to the quarter after."

Having the policy doesn't help if everyone takes it at once, which is why eligibility and scheduling get handled as separate questions.

"There's still something in my area that only I know, so I can't go yet."

Eligible on paper, blocked by handover in practice — and the blocker is the company's to fix, not the person's.

"Unpaid means nobody uses it. Either make it paid or drop it."

An argument against writing policy that only exists in the handbook.

Pagedeck created the policy after that engineer left. Four weeks at four years of service, paid, separate from annual leave. The item Grace spent longest on wasn't the length — it was the handover.

Three months before the first eligible person went, their area got split in two and another engineer started covering one half alongside them. The four weeks passed without a serious problem, and in week two it surfaced that release permissions sat with one account only, which got widened then. That was one of the effects the policy produced: preparing for the leave created a state where the company ran without that person.

The most common reading is that a sabbatical is a perk. It occupies one line in the benefits list on a job posting, so that's how it scans. But running it requires a handover structure to exist first. Without one, eligible people never go, and someone who joined because the posting mentioned it finds that out after starting. A benefit that exists only on paper is worse than no benefit, because it also costs the company credibility on everything else in the list.

The other mistake is assuming people will use a policy because it exists. The first eligible person usually hesitates — worried that a month away burdens the team, worried the role will look different on return. What removes that hesitation isn't wording; it's a precedent. Once a manager or a long-tenured colleague goes, comes back, and resumes the same job, applications start arriving. A policy nobody uses in its first year won't be used in its second either.