A Baltic onboarding checklist should end with permission to start

Define what ready means

An employee should not discover on the proposed first day that the internal onboarding checklist meant something different from the legal employer’s readiness check. For Estonia, Latvia and Lithuania, create a shared readiness record with separate country confirmation. It should identify the employment arrangement, agreed terms, required registrations and the individual’s right to work.

Your IT team can provision equipment and your manager can plan introductions while employment readiness remains unresolved. Keep those workstreams visible without allowing a completed laptop task to turn the whole hire green. The People lead needs a clear decision about whether the employee may start, not a reassuring percentage of completed tasks.

Give country requirements an accountable owner

Estonia’s employment-register guidance requires commencement to be recorded by the moment work starts. Do not reuse that wording as a deadline for Latvia or Lithuania. Ask each country’s employer or adviser to confirm its own requirements and the evidence that the step is complete.

Maintain one row per condition with owner, required date and status. The provider should confirm the country employment steps within its scope; the company should confirm business approvals and equipment access. If a registration depends on a signed contract or employee information, show the dependency. That allows People to chase the missing input instead of repeatedly asking whether onboarding is done.

Treat mobility as an individual assessment

Latvian OCMA guidance distinguishes Union citizens and third-country nationals. Lithuania’s Migration Department describes its own residence-permit requirements and exceptions. A worker’s permission in one Baltic country is not a substitute for checking the proposed work and employment arrangement in another.

Ask for a current assessment of citizenship, residence status, physical work location and any employer-linked conditions. Country service coverage alone does not establish sponsorship capability for every person. Agree who will communicate the outcome to the candidate and how the team will respond if the proposed start date must change. Keep sensitive documents inside the approved secure process.

Make the final handover explicit

Before the first day, confirm the legal employer’s readiness, payroll entry, employee communication and manager plan. Record any remaining condition and who has authority to resolve it. If the start cannot proceed, send a clear revised plan rather than leaving the employee to infer what a delayed platform status means.

After the first payroll, close the onboarding record by confirming the employee can access their documents and knows where to ask questions. A good onboarding handover prepares ordinary employment support as well as the first morning.

Teamed is worth evaluating when a small People team wants a named person coordinating these dependencies. Use the checklist to test how the contact works with each country specialist, what confirmation People receives and who covers absence. The desired outcome is a reliable decision at the right time, with the employee and manager receiving the same accurate message.