A cross-border hire can look routine on an org chart and still produce a contract that is wrong for the place where the person actually works. The practical lesson is simple: do not start with a global template and ask whether local counsel can “approve” it. Start with the facts that decide which rules may apply, then build the document around those facts.

For an employer, the nine questions below are a triage tool, not a substitute for local advice. They are designed to expose the parts of a hiring plan that can change the contract, onboarding record, payroll setup, termination process, or dispute route.

1. Where will the person physically work most of the time?

The work location is not a cosmetic address field. It can affect minimum employment standards, payroll registration, working-time rules, leave, health and safety duties, and which courts or agencies can hear a dispute.

A U.S. offer letter, for example, should not be treated as a universal model merely because the employer is incorporated in the United States. The U.S. Department of Labor explains that the Fair Labor Standards Act establishes federal minimum wage, overtime and recordkeeping rules, while states may impose additional standards. When both federal and state minimum-wage laws apply, the employee is entitled to the higher minimum wage.

The same “place first” logic matters elsewhere. In Great Britain, section 1 of the Employment Rights Act 1996 requires a written statement of employment particulars and specifies information that must be supplied. In the EU, Directive 2019/1152 sets transparency and predictability requirements that Member States implement through national law.

Local check: identify the city, state/province and country where work will actually be performed, not only the employer’s headquarters.

2. Who is the legal employer, and is that entity allowed to employ there?

A group may have a parent company, sales subsidiary, payroll company, professional employer organisation, employer-of-record vendor, and local branch. The name on the contract must match the real employment arrangement.

Before drafting compensation language, verify which entity will hire, pay, supervise and terminate the worker. A mismatch can cause tax, payroll, benefits, immigration, corporate-presence or litigation problems that no elegant clause can cure.

A useful file should include the legal entity name, registration details, local payroll pathway, authorised signatory and the reason that entity was selected.

3. Is the person truly an employee, or could classification be disputed?

Job titles do not decide legal status. The underlying relationship matters. Control over work, economic dependence, integration into the business, opportunity for profit or loss, provision of equipment and other factors can matter depending on the jurisdiction and legal test.

This is why a “contractor agreement” cannot safely convert a relationship into independent contracting by label alone. If the business expects fixed hours, close supervision, exclusivity and ongoing integration, classification deserves a separate review.

Decision point: if the commercial team cannot explain why the proposed status fits local law without relying on the label in the document, stop and review classification before signature.

4. What must be in writing, and when must it be delivered?

Written-information rules differ materially.

In Great Britain, the Employment Rights Act 1996 states that specified particulars must be provided in a written statement, with core particulars supplied no later than the beginning of employment. The required information includes matters such as the parties, start date and remuneration.

EU rules add another layer. EU-OSHA’s summary of Directive 2019/1152 notes a duty to provide workers with essential aspects of the employment relationship in writing, with much of that information due very early in the relationship. National implementing rules still need to be checked.

A global contract should therefore have a jurisdiction checklist that asks: which terms must appear in the main document, which can sit in policies, what language is required, whether electronic delivery is accepted, and what deadline applies.

5. Which pay, hours, leave and benefits rules are mandatory?

Compensation cannot be reviewed only as “salary plus bonus.” Mandatory rules can sit underneath the negotiated package.

For each location, test at least base pay, overtime or working-time treatment, pay frequency, commission timing, expense reimbursement, statutory leave, holiday pay, sick leave, pension or social-insurance obligations and legally required benefits. Also verify whether a bonus described as “discretionary” may still create obligations because of plan language, repeated practice or local law.

Avoid copying a U.S. exempt/non-exempt concept into another country as though the same labels carry over. Likewise, do not assume a monthly salary eliminates overtime questions.

A good contract file separates three columns: negotiated economics, mandatory floor, and policy-dependent benefits.

6. Which restrictions can actually be enforced?

Confidentiality, intellectual-property assignment, non-solicitation and post-employment restrictions often receive the most aggressive template language. They are also highly jurisdiction-sensitive.

The safe drafting question is not “How broad can we make this?” It is “What legitimate interest are we trying to protect, and what is the narrowest locally supportable mechanism?”

For a sales employee, customer information and trade secrets may be the real concern. For an engineer, invention ownership and source-code access may matter more. For a senior executive, fiduciary duties, garden leave or narrowly tailored restrictions may be relevant. The available tools vary by jurisdiction.

Do not assume a choice-of-law clause will rescue a restriction that conflicts with mandatory local employment rules.

7. How can the relationship end, and what process is required before termination?

Termination language is one of the clearest reasons cross-border contracts cannot be treated as interchangeable.

Some systems permit broad at-will termination in many private-sector relationships; others require notice, statutory severance, consultation, a fair reason, a fair process, or combinations of these. Collective consultation, works-council rights or protected-status rules may also matter.

The contract should not promise a termination mechanism that local law does not allow, nor should it omit mandatory rights because the global template is shorter.

Before finalising the clause, map: ordinary resignation, performance termination, misconduct, redundancy/reorganisation, long-term absence, protected leave and change of control. The answer may be different for each.

8. What happens when the worker crosses borders after hiring?

A contract can be locally correct on day one and become incomplete when the employee relocates, works remotely from another country, spends extended periods abroad or changes reporting lines.

Build a trigger process. The employee should know that a material location change must be disclosed before it happens. HR should then recheck immigration, payroll, tax, social insurance, local employment rights, data access and benefits.

This is especially important for “work from anywhere” arrangements. A manager’s informal approval is not the same as a legal, payroll and security review.

A practical contract can reference the mobility policy without pretending the policy overrides mandatory law.

9. Which forum, language and dispute route will matter in practice?

Contracts often end with governing-law, jurisdiction, arbitration and language clauses. Those clauses are important, but they should be tested against mandatory local rights and actual enforcement.

Ask where the employee could file an administrative complaint, where court proceedings may be brought, whether arbitration is permissible and enforceable for the dispute type, whether a local-language version is required or prudent, and which version controls if translations differ.

The goal is not to pick the forum most convenient for headquarters. It is to avoid a clause that creates false confidence.

A chronological hiring workflow

Before approval: confirm work location, legal employer, proposed classification and immigration/work-authorisation pathway.

Before offer: map mandatory pay, hours, leave, benefits, written-information rules and any collective or sector-specific obligations.

Before signature: review restrictions, IP/confidentiality, termination, dispute clauses, language and required notices.

Before start date: deliver required documents, complete payroll and benefit registration, capture acknowledgements and store the signed record.

After start: treat relocation, promotion, compensation changes, material duty changes and entity transfers as triggers for a fresh local review.

What evidence should sit behind the contract?

Keep a decision file, not just a signed PDF. At minimum, preserve the job description, work-location confirmation, classification analysis, compensation approval, policy versions incorporated by reference, required notices, signed contract, amendments and delivery/acknowledgement evidence.

If a later dispute arises, the question is often not only “What did the contract say?” but “What was the actual arrangement, which rules applied, and can the employer prove what it provided and when?”

The boundary that matters most

Cross-border employment law changes quickly and often operates through mandatory local rules that a private contract cannot waive. This guide is a practical issue-spotting framework, not jurisdiction-specific legal advice.

Before relying on a clause for a real hire, obtain local advice for the worker’s actual location and current facts. That is especially important for classification, restrictive covenants, termination, works-council or collective rights, immigration, payroll and dispute-resolution terms.

Sources

Related Reading