Most global mobility policies are written with two scenarios in mind: an employee relocating from the home country to a host country, and eventually repatriating back home. It is a clean model, and it covers the majority of assignments most companies manage. It also completely misses a growing category of moves that does not fit that pattern at all: the third-country national, or TCN, an employee who is neither a citizen of the company’s home country nor the country they are being assigned to.
A German employee based in Singapore who gets assigned to a project in Brazil is a TCN. So is an Indian engineer working for a US company’s UK subsidiary who gets reassigned to Germany. These moves are becoming more common as companies build genuinely global talent pools rather than hub-and-spoke structures centered on headquarters, and they expose gaps in relocation policy that a home-to-host model was never designed to handle.
Why TCN Assignments Do Not Fit the Standard Playbook?
The core problem with applying a standard international relocation policy to a TCN assignment is that it assumes a clear home base the employee will eventually return to, with tax residency, benefits, and repatriation planning all built around that assumption. A TCN often does not have a single obvious home base in the same sense. They may hold citizenship in one country, tax residency in another, and have spent the last several years building a life in a third.
This creates compliance questions that a standard policy simply does not answer. Which country’s tax treaty applies. Whose social security system the employee continues contributing to, if any. What happens to benefits eligibility when the employee is not moving to or from the country where the company’s benefits plan is actually registered. None of these are edge cases for a company managing a genuinely global workforce, they are routine questions that come up every time a TCN assignment gets initiated without a policy built to handle it.
The Tax and Compliance Layer Gets More Complicated, Not Less
It is tempting to assume TCN assignments are simpler than home-to-host moves because there is no “home” tax authority pulling the employee back for compliance reasons. In practice, the opposite is usually true. A TCN assignment can trigger tax obligations in three jurisdictions at once: the country of citizenship, the country of prior residence, and the new host country, each with its own rules about what counts as taxable presence and how long an assignment can run before residency status shifts.
Getting this wrong is not a paperwork problem, it is a real financial and legal risk for both the employee and the company. This is exactly the kind of complexity where working with a relocation management company that understands international tax pays for itself, since the alternative is discovering a compliance gap only after the employee has already been in the host country long enough for it to matter.
Benefits Continuity Is Its Own Puzzle
Standard relocation benefits, health insurance, retirement contributions, often assume the employee is enrolled in a plan tied to either the home or host country. A TCN moving between two countries where the company has entirely separate benefits infrastructure can fall into a gap where neither plan clearly applies, particularly for short-notice assignments where there is no time to formally transfer enrollment before the move happens.
Companies that manage a meaningful volume of TCN assignments tend to solve this with a global benefits umbrella, typically international private medical insurance and a portable retirement vehicle, that follows the employee regardless of which two countries are involved in a given move. It is more expensive to set up than country-specific plans, but it removes the recurring problem of TCN employees falling through benefits gaps that nobody notices until a claim gets denied.
What a TCN-Specific Policy Should Actually Include?
A policy addendum built specifically for TCN assignments does not need to reinvent your entire mobility program, but it should explicitly address a few things a standard policy leaves ambiguous: which country’s cost-of-living baseline applies when calculating adjustments, how repatriation is defined when there is no single obvious home base to return to, and who is responsible for coordinating tax filings across multiple jurisdictions during the assignment.
Many companies handle this kind of complexity through a mobility consulting engagement rather than trying to build TCN policy internally from scratch, since the compliance stakes are high enough that outside expertise usually pays for itself quickly. It should also address language and cultural support more deliberately than a standard policy does. A TCN moving from Singapore to Brazil is not just adjusting to a new work culture, they may also be operating in a third or fourth language depending on their background, without the informal support network that either a home-country or host-country employee might have through colleagues who share their background.
Recognizing a TCN Assignment Before It Becomes a Problem
The most common mistake companies make with TCN assignments is not recognizing them as TCN assignments in the first place. An HR team processing what looks like a routine transfer between two international offices may not flag that the employee’s citizenship, tax residency, and assignment history put them squarely in TCN territory until a compliance question comes up mid-assignment.
Building a simple screening step into the relocation intake process, checking citizenship, current tax residency, and prior assignment history against the destination country before finalizing the move, catches this early enough to build the right policy structure from day one rather than retrofitting one after a compliance issue surfaces, much like the screening already built into pre-decision services for standard relocations.
What Repatriation Even Means for a TCN?
Repatriation planning assumes a return trip to somewhere. For a home-to-host assignment, that somewhere is obvious. For a TCN, it often is not, and companies that do not address this explicitly tend to default to sending the employee back to wherever they were immediately before the assignment started, regardless of whether that location still makes sense for the employee or the business.
This is where the lessons from a well-run repatriation program apply, just adapted for an employee who may not have a clean “home” to repatriate to. A more useful approach treats the end of a TCN assignment as its own decision point rather than an automatic return trip. That might mean a new assignment in a third location, a transfer to company headquarters, or in some cases a negotiated local-plus arrangement in the country where the assignment took place, particularly if the employee has built meaningful ties there over the course of a multi-year posting. Building this flexibility into policy from the start avoids the awkward scramble that happens when an assignment is ending and nobody, including the employee, actually knows what happens next.
Why This Deserves a Named Owner, Not a Shared Responsibility?
TCN assignments touch tax, benefits, immigration, and cultural support simultaneously, which means they tend to fall into the gaps between departments that each own one piece of a standard relocation but none of them own the whole picture. Global mobility teams that handle TCN moves well almost always have a single named owner for each assignment, someone whose job is to track the full picture across tax jurisdictions and benefits systems rather than assuming each function will coordinate informally.
Without that ownership, TCN assignments tend to surface problems reactively: a tax filing deadline missed because nobody realized a third jurisdiction was involved, or a benefits gap discovered only when a claim gets denied. A named case owner, whether that is an internal mobility manager or an external relocation consultant, catches these issues before they become compliance failures rather than after.
Getting the Structure Right From the Start
TCN assignments are not going away as a category. As companies continue building genuinely global talent structures rather than moving people strictly between headquarters and regional offices, the volume of assignments that do not fit a clean home-to-host model will keep growing, and the compliance risk of managing them with a policy that was never designed for this pattern grows right along with it.
If your global mobility program is starting to see more assignments that do not fit neatly into a home-to-host structure, talk to a GMS relocation consultant about building a policy framework that actually accounts for third-country national moves rather than forcing them into a template that was not built for them.
The companies that get ahead of this now, before TCN assignments become a large enough share of the mobility program to cause a visible compliance problem, spend far less time firefighting later. A policy built for the pattern from the outset costs a fraction of what it costs to unwind a tax or benefits mistake discovered mid-assignment, and it gives employees on these assignments the same confidence in the process that home-to-host employees already expect from a well-run relocation program.
