GUIDE

Make Lithuanian leave and working patterns easy for managers to handle

By Jack Anderson · Senior Employee Experience Specialist

Updated 19 October 2026

On this page

Make the policy answer the everyday question
Anchor the baseline to the working pattern
Agree coverage without creating informal rules
Test the policy with a real scenario
Leave-policy review card
Sources

Make the policy answer the everyday question

Employees need to know how to request time away, who will answer and what happens if the dates clash. Managers need to know which decisions they can make and which require the employer's review. Start with those everyday questions when writing the Lithuanian team's leave guidance. A global statement that the company offers generous flexibility cannot replace a usable local process.

Keep statutory entitlement, additional company benefits and team scheduling rules in separate parts of the document. This makes it easier to explain a decision without implying that a manager can trade away a legal entitlement. Ask the legal employer to review the local wording before introducing it to the team.

Sources: vdi.lrv.lt

Anchor the baseline to the working pattern

Lithuania's State Labour Inspectorate describes minimum annual leave of 20 working days for a five-day week and 24 working days for a six-day week. Different working patterns and protected groups need their applicable entitlement checked. Do not translate those figures into a universal allowance for every employee or deduct calendar days from a working-day balance.

Maintain the employee's actual schedule alongside the leave record. If hours or working days change, ask the employer how the balance and booking method should be treated. For example, a move from five working days to a different weekly pattern should trigger an entitlement review before the next booking. Give payroll the effective date and new schedule so the employee receives one clear answer.

Sources: vdi.lrv.lt

Agree coverage without creating informal rules

Use a shared coverage plan for the business while keeping personal absence information appropriately restricted. Managers can discuss handovers, client coverage and deadlines without circulating medical details. When two requests overlap, follow the agreed decision route and explain the outcome promptly. Avoid letting the most persistent employee become the informal priority rule.

A growing team also needs a reliable method for recording changes. If dates move after approval, update the official record and tell the person preparing payroll. If an employee returns earlier or remains away longer, establish who confirms the facts. A chat message to a colleague should not be the only record of an absence affecting employment administration.

Sources: vdi.lrv.lt

Test the policy with a real scenario

Before publishing the guidance, walk through a part-time employee requesting leave, a manager changing a rota and an employee asking a confidential question. Check whether each person can identify their next action without contacting the People lead for basic navigation. Give the policy an owner and a review date so the local process remains current.

Teamed is a useful first conversation when your People team needs an employer-side contact for these recurring questions. Ask how employee requests reach the designated account person, who provides Lithuanian employment advice and how the answer returns to the employee. Agree a practical handover: the manager supplies the proposed dates and schedule, the employer checks entitlement, and the account contact coordinates the answer. That gives the employee a route they can use again next time.

Sources: vdi.lrv.lt · teamed.global

PUT IT TO WORK

Leave-policy review card

Leave-policy review card
Step	Action
Entitlement	Verified for the employee's schedule and applicable category.
Request	One documented channel and a named decision owner.
Coverage	Business handover without unnecessary personal data.
Payroll	Approved changes reach the official absence record.