Writing a leave policy for a small, global team

A leave policy answers three questions for every person on the team: what kinds of time off exist, how much of each you get, and how you ask for it. Write those down clearly once and you stop having the same conversation over and over. This guide walks through the decisions a small team has to make, with the extra care a global headcount needs, and points to where local law has to override anything you copy from a template.

One warning before the detail. Leave sits close to employment law, and the specifics differ by country and sometimes by region within a country. Everything below is a way to think about the structure. For statutory minimums on annual leave, sick pay, and parental leave, confirm the real figures for each location with a qualified local adviser or your payroll partner. Do not publish numbers you have not checked.

Define your leave types first

Before you set any allowances, decide which categories of leave you recognise. A small team usually needs a short list:

• Annual leave (holiday, vacation, paid time off). The main allowance people plan around.
• Sick leave. Time off when someone is unwell. In many countries a statutory scheme sits underneath this, so define the concept and confirm the entitlement locally.
• Parental leave. Maternity, paternity, adoption, and shared arrangements. This is heavily governed by law and varies more than any other type, so treat your policy text as a frame and fill in the country-specific rules with advice.
• Public holidays. Not really an allowance, but they belong in the policy because they interact with everything else.
• Unpaid leave. A catch-all for longer absences that fall outside the paid types, granted case by case.

You can add others later, such as compassionate leave or study leave, but resist the urge to invent a dozen categories on day one. Every type you create is something you then have to track, approve, and explain.

Accrual versus a fixed allowance

This is the decision that trips people up most. There are two honest ways to grant annual leave.

A fixed annual allowance gives everyone their full year of leave up front. It is easy to understand and easy to communicate. The downside shows up when someone leaves partway through the year having already taken more than they had earned, which you then have to reconcile.

Accrual earns leave gradually, usually a fraction each month worked. It protects the company on early leavers and handles mid-year joiners cleanly, because a person who starts in July has simply accrued less. The trade-off is that it is slightly harder to explain, and people sometimes feel they cannot book a longer trip early in the year.

Neither is more correct. Smaller teams often begin with a fixed allowance for simplicity and move to accrual once they have hired and lost enough people that mid-year maths matters. Whichever you pick, state it plainly in the policy so nobody is surprised.

Carry-over

Decide what happens to unused leave at the end of the year. The common options are to allow none (use it or lose it), to allow a capped amount to roll into the next year, or to allow carry-over with an expiry date by which it must be used. A cap is the usual middle ground: it discourages people from hoarding leave while not punishing someone who had a heavy year. Note that some countries set legal rules on carry-over and on paying out untaken statutory leave, so check before you set a hard “lose it” rule.

Public holidays across countries

For a team in one country, public holidays are simple. For a global team they are the part people get wrong most often. The clean approach is to assign each person the holiday calendar of the country they work in, and to keep annual leave entirely separate from it.

That way a person in Nigeria, a person in Portugal, and a person in Brazil each see the days their location observes, and none of them lose annual leave to a holiday they were always going to have off. Trying to average this into one shared list creates quiet resentment. If you use a tool that supports per-country holiday calendars, this becomes configuration rather than a spreadsheet you maintain by hand.

Three details decide whether a holiday calendar is actually useful, and they are worth checking in whatever tool you use. The first is where the calendar attaches: in Capstan’s core a calendar belongs to a location and an employment inherits it through its location, so you configure a country once and assign it to every office in it rather than setting a calendar per person. The second is the working week. A calendar carries its own working-week pattern, which matters the moment you hire somewhere that does not run Monday to Friday, and a leave request that spans a non-working day counts it as zero rather than silently charging someone for it. The third is optional holidays. Some countries observe a list from which each person picks a few; a calendar marks those as restricted rather than public and caps how many an employee may take, which is the difference between modelling the country and approximating it.

One practical note on setup. Capstan ships bundled public-holiday sets for a short list of countries, importable for a year in one click and editable afterwards, and everywhere else you enter the dates yourself. There is no file import for holidays, so if you are standing up calendars for several countries at once, budget an afternoon rather than assuming an upload.

Approvals

Keep the approval path short and predictable. For most requests, one approver, usually the person’s manager, is enough. Write down three things:

• Who approves. Normally the direct manager, with a named fallback for when they are away.
• How much notice you expect. A reasonable window for planned leave, with the understanding that sick leave cannot be planned.
• What happens to a request that is not actioned. Decide whether silence means approved or pending, and make it explicit so nobody books flights on a maybe.

Avoid multi-stage approval chains at small scale. They add delay without adding judgement, and they signal a lack of trust you probably do not intend.

Put it in writing, then automate it

A policy that lives only in someone’s head is not a policy. Once you have made these decisions, write them into a single document every employee can find, and have people acknowledge it so there is a record they read it. For most small teams that document is the employee handbook, with leave as one chapter of it rather than a policy floating on its own. From there, the mechanical parts (accrual maths, balances, holiday calendars, approval routing) are exactly the kind of work software should do for you rather than you tracking it in a sheet.

If you want a fast starting point, Capstan’s free leave policy generator produces a first draft you can edit for your team and your locations. Use it to skip the blank page, then apply the local checks above before you publish. When you are ready to run leave for real, the same rules live in the core HRIS, which is free up to twenty active employees.

For the wider picture of what a small team needs from HR tooling, the HR software for startups guide sets out the priorities, and the employee onboarding checklist covers where a new hire’s leave record should start.