Absence policy: what to include and how to manage absence across Europe

A manager approves two weeks off for someone in Munich. A month later, HR notices that a regional public holiday within those two weeks was charged as annual leave. Another employee resigns, and nobody can confirm their leave balance without going through three old spreadsheets.

An absence policy prevents both situations. It explains how employees book time off and report sickness, how that time is paid, and what the company records.

Most HR teams already have some version. The trouble usually starts when the company grows into new countries, rules differ by location, and leave is still tracked by hand.

A ready-to-use structure for your leave policy sits below, followed by the rules to localize for each country, who owns each step, and what your software needs to do.

Key takeaways

• A policy only works when local rules are built into how leave is calculated.

• Public holidays and carryover deadlines differ by country and region, so one company calendar creates errors.

• Offboarding is where inaccurate leave data shows up, because the final balance feeds into final pay.

• Assign an owner to every step before you choose or automate a tool.

• Test software against your hardest real cases, like a German regional holiday or a Dutch carryover deadline.

Absence policy template: what to include

Use this structure as the skeleton of your policy. Replace the text in square brackets with your own details, then add a country appendix for each location (see the framework further down).

The sections below explain how to define each part of your policy and adapt it to different locations.

What an absence policy covers

Absence falls into two broad groups. Planned absence, like vacation or parental leave, is booked in advance; unplanned absence, like sickness or a family emergency, happens at short notice. Both can be authorized (agreed or correctly reported) or unauthorized (the employee is away without permission or explanation).

Your employee absence policy should name every type of absence you handle and say what happens for each one.

You can put all of this in one document or split it into a time off policy and a separate sick leave policy. Either works, as long as employees can find the rule they need.

EU law sets the minimum, and national law or collective agreements often add more. Under the EU Working Time Directive, every worker is entitled to at least four weeks of paid annual leave per year. Many countries go further, so your paid time off policy should start from the local rule for each location.

What to include in an absence policy

Every clause should say who does what, by when, through which channel, and what happens next.

The checklists below cover the clauses most policies need. Public holidays, carryover, sick leave, and leaving the company have their own sections later, because they're where multi-country teams run into the most trouble.

Requesting and approving planned leave

• Notice period for short and long breaks

• Who approves, and how quickly they respond

• How you handle clashes when several people in one team want the same week

• Blackout periods, like a year-end close in finance

Requests should be easy to make. When employees can book time off themselves, HR stops acting as the go-between for every request.

Reporting unplanned absence and sick leave

• Who employees contact when they can't come in, by what time, and through which channel

• When medical evidence is needed (this varies by country)

• How you'll keep in touch during a longer absence

• What the return-to-work conversation covers

Frame the return-to-work conversation as support. Hold it on the first day back, check whether the person needs anything as they return, and record the date they came back. Check local rules on what a manager may ask about the illness.

For unauthorized absence, name who follows up and how quickly. Include the first step a manager takes when an employee hasn't arrived or called in by 10 AM.

Repeated short absences need a defined route too. Say who reviews absence patterns, how often, and what the first conversation looks like. What you may record and ask differs by country, so check local rules before you set any triggers.

Entitlement, accrual, and proration

• Annual allowance per employee type

• Whether leave is granted on 1 January or accrues monthly

• Proration for part-time staff and for people who join or leave mid-year

Proration is where manual calculations tend to go wrong. Someone who starts on 15 August needs a different number than someone who starts on 1 September. Calculating this automatically for every mid-year joiner removes a recurring source of errors.

Pay during absence

• Which absences are paid, and at what rate

• Who confirms the details to payroll, and by which cutoff

• Where the local sick pay rules are written down for each location

Records, privacy, and access

• What you record for each absence: type, dates, approver, and supporting documents

• Who can see the reason for a sick leave

• How long you keep absence records

The European Commission lists health-related data as sensitive personal data under the GDPR, so specific processing conditions apply. Review who has access at least once a year.

Keeping absence records in central employee records with role-based permissions makes those access rules easier to enforce than a shared folder.

What varies by country in a European absence policy

Keep one shared policy for the process and add a country appendix for the rules that change by location. The table lists the areas to check for every country you employ people in.

Fill in one appendix per country and give each a named owner who checks it when the law changes. Four of these areas are especially important for multi-country teams, so each gets its own section below.

Public holidays by country and region

A holiday policy for Europe can't rely on one company calendar. Public holidays differ by country and, in some places, by region.

In Germany, the Federal Ministry of the Interior says the Day of German Unity is the only national holiday set by federal law. The federal states set all the others.

So a team with people in Munich and Hamburg will have different days off in the same year.

Your policy should link each employee to the public holiday calendar for their work location. It should also say that public holidays falling inside a leave request aren't deducted from the employee's allowance.

That second rule matters for fairness. Two people taking two weeks off in different months should use the same number of days, even if one period includes national holidays. Marieke Drees, VP of People at Tellent, describes how an HRIS handles it.

Carryover and expiry rules

Year-end is when unclear rules turn into disputes. Your leave policy should state how many days can carry over, until when, and what happens to unused days.

Local law often sets part of the answer. In the Netherlands, statutory leave expires six months after the end of the year it was accrued, according to the Netherlands Enterprise Agency. Non-statutory days expire after five years, and the six-month limit doesn't apply to employees who couldn't reasonably take their leave.

Applying one global carryover rule to every country will be wrong somewhere. Manual year-end resets add a second risk, because one missed formula affects every balance after it. Build the rules into your system and automate them, so a missed deadline doesn't turn into a compliance problem.

Add a reminder step, too. An employee who hears in May that their days expire in June can still plan a week off. One who finds out in July can't.

Sick leave rules that need extra care

Sick leave carries more legal and financial exposure than most other absence types, especially for long-term illness. Dutch employers, for example, must pay sick employees at least 70% of their wages for up to two years, according to the Netherlands Enterprise Agency. They must also help the employee return to work, which involves a series of reintegration steps with their own deadlines.

Deadlines like these shouldn't depend on one person's calendar. If the HR manager who tracks them goes on vacation, the step slips. Automated reminders tied to the sickness case are more reliable, and they show everyone who needs to act next.

You'll also need reporting on sick leave over time, by team and by location. Building that in Excel every quarter takes hours and is hard to keep up. Setting up absence and sick-leave reports once means the numbers are ready when leadership or an auditor asks.

Smaller and mid-sized employers face these pressures too, including audits, documentation requests, and labor-law obligations.

Unused leave when someone leaves

Offboarding tests your absence data more than any other moment. The final leave balance feeds into final pay, benefits, and the leaver's paperwork, so a wrong number causes problems in several places at once.

As soon as you know of a departure, confirm the employment type, notice period, last working day, and reason for leaving, including whether the person works through the full notice period or is on garden leave.

Resignation, dismissal, garden leave, and retirement follow a similar structure. The departure type changes the timing, the case's sensitivity, and the documents you need.

Joanna Augustyn, People Operations Specialist at Tellent, describes what comes next.

Your policy should say which option applies and who decides. EU rules say employers can't replace annual leave with payment unless the employee's contract ends before all their leave is taken. Payout is therefore an offboarding decision, and it depends on an accurate balance.

If balances only exist in old spreadsheets, that accuracy is hard to reach. Rebuilding a leaver's balance from historic data by hand is slow and error-prone.

When you export leave data to payroll, the payout figure goes into the final payroll run without being retyped.

Who owns absence management?

Handoffs are where absence processes go wrong. A manager approves leave, but payroll never hears about it, or finance needs a payout figure that HR hasn't confirmed. Leave data spread across the HRIS, spreadsheets, payroll files, email, and chat makes this worse, because nobody knows which version is current.

Give the whole process one end-to-end owner, usually People Operations. Managers, payroll, finance, and IT still own their own steps. The owner makes sure each step has a trigger, a deadline, and a named person.

Plan for the owner's own time off as well. Joanna Augustyn explains how her team handles it.

Sort out ownership before you look at software. Joanna Augustyn is direct about the order.

Signs your absence management has outgrown spreadsheets

Spreadsheets can work for a small team in one country. These signs suggest it's time to change.

• Employees message HR to ask how many days they have left.

• You employ people in more than one country or region.

• Year-end carryover takes days of manual checking.

• Leaver balances have to be rebuilt from historic files.

• Payroll corrections keep tracing back to leave data.

• Managers approve leave in chat or email, and HR finds out later.

Balance questions are often the first sign HR notices. Marieke Drees used to answer them herself.

If you see only one of these signs in a single-country team, tightening the spreadsheet and ownership rules may be enough for now. If you see three or more, the guide to moving from spreadsheets to an HRIS walks through the trade-offs.

When you're ready to compare options, look at an HRIS built for growing teams that keeps leave rules, approvals, and balances in one place.

What to look for in absence management software

Start with your policy. Each clause you wrote above becomes a requirement the software has to meet. Sort them into must-haves and nice-to-haves before you book any demos, so the feature list doesn't set the agenda.

Take specific questions into each vendor conversation.

• Can you show a vacation request for an employee in Bavaria that spans Corpus Christi, and how the deduction is calculated?

• How would an admin set a carryover rule that expires on 1 July for Dutch employees only?

• Can the accrual rule be changed for everyone in one country at once?

• Who can see the reason for a sick leave, and how is that access set?

• How does leave data reach a payroll provider, and how often?

• What does setup involve, how are current balances migrated, and what does it cost in total?

During a trial, test your hardest real cases. A demo usually shows a single-country company with standard rules. Load a handful of real employees with messy histories, then check that the balances match what you expect.

How Tellent supports your absence policy

Once your policy defines the rules, your HR system needs to apply them consistently. Tellent HR Manage helps growing teams manage leave rules, requests, approvals, balances, and reporting in one place.

• Create your own leave types and assign different leave policies by employee and location.

• Apply each location's public holidays, grant or skip specific holidays, and add your own.

• Automatically calculate accruals and customize annual leave carryover.

• Approve requests in one click or set up automatic approvals.

• Let employees request leave from the Tellent HR mobile app.

• Sync a shared absence calendar with Google Calendar, Outlook, or iCal.

• Export monthly leave records for payroll and build custom absence reports.

Tellent's own People team runs its absence policy this way. When the company moved its French-based employees to Tellent HR, Marieke Drees needed to change their days off.

Tellent HR connects with payroll and other HR tools through its integrations marketplace and a flexible API. It may not be the right fit if you need a heavily customized enterprise setup with complex union-negotiated leave schemes across many entities. In that case, evaluate configuration depth carefully.

Putting your absence policy to work

An absence policy works when people can follow it without asking HR. Use the shared structure as your base, add a country appendix for each location, and give every step an owner. That covers most of what goes wrong as a team grows: regional public holidays charged as annual leave, carryover deadlines that pass unnoticed, and leaver balances nobody can confirm.

Start with the parts that carry the most risk. Check the local rules for each country you employ people in, assign an owner to every appendix, and document who acts when someone is sick for a longer period or leaves the company. Those are the situations where a gap in the policy turns into a legal or payroll problem.

Then look at your tools. If balances, approvals, and holiday calendars still live in spreadsheets, the policy depends on people remembering to apply it. Choose software that applies those rules for you, and test it on your hardest cases before you commit: a German regional holiday, a Dutch carryover deadline, a leaver with a half-used balance.