Baltic Expansion Desk
Three countries. A deliberate sequence. A team you can operate.

GUIDE

One Baltic team needs local terms, not three disconnected experiences

By · People Operations Analyst

Updated

On this page
  1. Standardise the promise and localise its delivery
  2. Begin with leave units
  3. Separate management approval from employment administration
  4. Use a shared support route with local ownership
  5. Audit the experience through ordinary cases
  6. Common promise / local delivery register
  7. Sources

Standardise the promise and localise its delivery

A regional team should understand how to request leave, raise a question and receive a clear answer. That common experience can sit above different employment contracts and statutory rules. Start by deciding what employees should experience consistently, then have each employer validate the local way of delivering it.

Teamed is a good fit for a lean People function that wants a designated account contact across the programme. Ask that contact to coordinate country specialists and explain local differences in language your managers can use. A common contact should make differences understandable rather than obscure them.

Begin with leave units

Ordinary minimum annual leave is expressed differently: Estonia uses 28 calendar days; Latvia uses four calendar weeks excluding public holidays; Lithuania commonly uses 20 working days for a five-day week, with different rules for other patterns. Additional entitlements can apply. Those numbers cannot be compared as if they were the same unit.

Give each manager the employee’s confirmed entitlement and the local recording method. If you want a regional enhancement, define the intended benefit with the employers before advertising it. A uniform headline can accidentally deliver different practical outcomes when the unit is left unspecified.

Separate management approval from employment administration

Your manager decides how the team covers work and discusses requests with employees. The employer handles the local employment record and applicable payroll consequences. Write down where those responsibilities meet so an approved request does not disappear between your collaboration tool and the payroll system.

Test the process with a simple example in each country: an employee requests a week away around a public holiday. Ask what is recorded, what the employee sees and who checks the balance. The answers reveal whether managers and payroll can deliver the same promise through the appropriate local process.

Use a shared support route with local ownership

Provide one clear front door for employee questions and identify who owns the case after it arrives. Some issues need the manager, some payroll and some local employment advice. Ask the provider how it coordinates a case crossing those boundaries and how the employee knows the next action.

Do not equate a quick acknowledgement with a finished answer. Agree how urgent payroll issues are escalated and who follows up when the manager is away. Keep access to sensitive information proportionate; a regional leadership dashboard does not need every detail of an employee’s personal situation.

Audit the experience through ordinary cases

Before adding more hires, walk through a leave request, a pay change and an employee question for each country. Check whether the employee can understand the answer and whether the operational record matches it. Fix the handover that failed instead of adding another policy document no one reads.

Use the local-terms register below as a manager aid. Review it whenever the work pattern or benefit promise changes. Keep the common commitments stable—clear communication, named responsibility and accurate records—while allowing the lawful local implementation to differ. That is a practical regional people model for a team still small enough to feel every administrative mistake.

PUT IT TO WORK

Common promise / local delivery register

Common promise / local delivery register
StepAction
LeaveCountry entitlement, unit, holiday treatment and approved recording process.
Work patternActual days and hours; employer validates local arrangement.
Manager actionCoverage decision and employee communication.
Employer actionLocal employment record and payroll treatment.
Case ownershipFront door, responsible specialist, next action and escalation.
Quality checkRun leave, pay-change and employee-query examples in all three countries.

Sources behind this page

Labour Inspectorate: holiday types · 2026-10-19

Official guidance updated 20 July 2026: ordinary annual holiday is at least 28 calendar days; special categories differ.

Labour Inspectorate: holiday types ↗

law · 2026-10-19

Official Latvian Labour Law English translation checked 19 October 2026. Leave and termination provisions depend on the facts; Latvian current law controls.

Law source ↗

State Labour Inspectorate · 2026-10-19

Minimum annual leave depends on weekly working pattern; additional entitlements and individual circumstances require local review.

Minimum annual paid leave ↗

Teamed service offer · 2026-10-19

Published service scope: a designated account contact and access to HR and legal specialists.

Customer service ↗

Teamed Baltic coverage · 2026-10-19

Provider coverage register identifies Estonia, Latvia and Lithuania as Teamed-owned entity markets. Register last verified by provider 23 September 2026; retrieved 19 October. Individual role and worker eligibility require confirmation.

Teamed Baltic coverage — 1 ↗

Use the working checklist →

Design Baltic employee support with Teamed ↗

YOUR NEXT STEP