Global mobility teams have long operated in a world of PDFs living in shared drives, policy documents buried in inboxes, and no reliable way to tell which version of a policy is actually the current one.
For HR leaders managing international assignments, this is not just an operational inconvenience. It is a material compliance risk. One outdated policy tier applied to the wrong relocation can mean tax miscalculations, incorrect benefit packages, and regulatory exposure that surfaces long after the employee has landed.
Topia Horizon's AI-Assisted Policy Agent is built to solve exactly that. It transforms static, unstructured policy documents into structured, editable, and living benefit configurations without manual re-entry. This post covers how the feature works, what it means for global mobility teams in practice, and why it represents a meaningful shift in how organizations govern mobility policy.
The Problem with How Policy Has Always Been Managed
Ask any global mobility professional how they manage relocation policy today, and the answer usually involves some combination of Word documents, email chains, and institutional knowledge that lives in one person's head. Policy documents are often carefully written and legally reviewed, and then immediately filed somewhere they rarely get used. They almost never make it into the systems that actually calculate costs and run compliance checks.
The downstream consequences are predictable.
- No version control. When a tax law changes and a policy is quietly updated, there is often no audit trail showing what changed, when, and by whom. The "current" version and the "live" version drift apart without anyone noticing until it is too late.
- No structured benefit data. A policy document might describe housing allowances eloquently in paragraph form, but that description cannot be pulled into a cost simulation. Someone has to manually translate it, and that translation introduces its own errors.
- No visibility into tier logic. Which tier applies to a given assignment? When policy lives in documents rather than systems, that judgment call often happens informally, inconsistently, or both.
- Reactive compliance. Without policy rules encoded into the platform, there is no way to automatically flag when a simulation or assignment is out of policy. Gaps get discovered after the fact.
Topia Horizon addresses each of these gaps in a single, AI-powered workflow.
How Topia's AI-Assisted Policy Agent Works
The core mechanic is document ingestion and structured parsing. You upload an existing policy document in whatever format your team currently uses, and Horizon's AI reads it, extracts the benefit components, and converts them into editable, structured data within the platform.
A paragraph describing a housing allowance calculation becomes a configurable benefit line. A section on tax equalization becomes a selectable tax approach. The tier structure that distinguishes what a senior executive receives versus a junior employee becomes a navigable policy tier configuration rather than something buried in paragraph three of page eleven.
From there, the workflow is straightforward.
- Upload. Import your existing policy document directly into Horizon. The AI does the initial parsing work and produces a draft structured representation of the policy.
- Review and edit. The parsed output is fully editable. Mobility teams can review each benefit component, correct any extraction errors, and add context the document did not capture. Nothing gets locked in automatically. The AI produces a starting point; humans refine it.
- Configure tiers. Horizon supports Gold, Silver, and Bronze policy tiers. Each tier can carry distinct benefit structures, tax approaches, and allowance configurations. Once configured, tiers can be linked directly to individual simulations and assignments.
- Set tax approach. Tax equalization, tax protection, laissez-faire, and other approaches can each be configured per tier. This matters a lot in cost modeling. The choice of tax approach can move total employer cost substantially, and having it encoded in policy prevents ad-hoc decisions during simulation.
- Publish. Policies move through a Draft to Published status workflow, so only approved, reviewed policies get linked to live simulations. Previous versions stay accessible for audit purposes.
Why This Matters for Cost Simulations
The Policy Agent does not exist in isolation. It feeds directly into Horizon's cost simulation engine, and that is where its real value compounds.
When a policy is configured and published in Horizon, it can be linked to any simulation. The benefit package driving a cost estimate is not invented at run time by whoever is running the calculation. It is pulled from the organization's approved, versioned policy. The simulation for a US-to-Germany relocation will reflect the actual Gold tier allowances, the actual equalization approach, and the actual cost-of-living adjustment methodology the company has approved.
This closes a gap that plagues mobility teams operating with disconnected tools: the policy document says one thing, the simulation spreadsheet assumes another, and the actual package offered to the employee sometimes reflects neither.
With Horizon, the policy is the simulation input. Changes to policy automatically surface in subsequent simulation runs. And because the platform maintains a field-level audit trail across all policy changes, capturing before-and-after snapshots of every modification, teams always know what changed, when, and who approved it.
Built-In Intelligence Beyond Document Parsing
Beyond the initial document ingestion, Horizon's AI capabilities extend into policy management in several other ways.
- The AI Agent answers policy questions. From any page in the platform, users can query Horizon's AI Agent about the implications of a specific policy configuration. If you are considering expanding into a new destination and want to understand the tax and immigration considerations before building out a policy tier for it, the AI draws on Topia's proprietary tax engine and immigration library to provide a reasoned answer. The responses are grounded in Topia's underlying compliance data, not general internet knowledge.
- Policy-linked simulations surface out-of-policy scenarios. Because simulations are tied to specific policy tiers, it becomes immediately visible when a proposed package diverges from approved policy. That kind of automatic flag does not happen in a spreadsheet world. It requires deliberate platform design.
- Conversation notes keep policy context alive. Each policy record in Horizon supports inline notes with @mention support, meaning the reasoning behind a policy decision can live alongside the policy itself rather than in a separate email thread that nobody can find six months later.
The Governance Architecture Underneath It All
One of the less visible but structurally important aspects of Horizon's Policy Agent is the governance infrastructure it enables.
Every change to a policy record, every modified benefit line, every tier adjustment, every status transition from Draft to Published, is captured in Horizon's field-level audit log. The log records what changed, when, and by whom, with full before-and-after snapshots. For organizations subject to regulatory scrutiny or internal compliance requirements, this is not a nice-to-have. It is the documentation that makes a policy defensible.
Role-based access control governs who can create, edit, and publish policies. Superadmins and Admins have full access. Analysts and Viewers have read permissions appropriate to their roles. Policy configuration is not open to uncontrolled modification; changes require appropriate authorization, and all changes are logged regardless of who makes them.
The multi-tenant architecture also matters for large organizations or consulting firms managing mobility programs across multiple clients or subsidiaries. Policy configurations can be maintained at the organization level or at the sub-tenant level, with appropriate access boundaries between them.
Who Benefits Most?
- Global mobility teams get a single source of truth for policy. One place where the current, approved version of every tier and benefit structure lives, accessible to anyone running a simulation. No more hunting through email for the latest policy document.
- HR and finance leaders get confidence that cost simulations reflect real, approved policy rather than assumptions made by whoever is running the numbers. When a simulation goes to finance for approval, the policy inputs are documented and auditable.
- Compliance and legal teams get the audit trail they need. Every policy change is documented with full before-and-after visibility. If a regulatory question arises about what policy was in effect for a given assignment at a given time, that answer is retrievable.
Topia Horizon in the Broader Mobility Landscape
The AI-Assisted Policy Agent is one component of a platform designed around the full lifecycle of global mobility. Horizon also handles pre-travel risk assessments with traffic-light compliance scores across immigration, tax, social security, and permanent establishment exposure, remote work management with structured approval workflows, and a cost simulation engine capable of handling everything from individual assignments to group project-based moves.
What differentiates Horizon from point solutions is not any single feature. It is the integration. A policy configured in the Policy Agent feeds directly into cost simulations. The same employee record links to their simulation history, their pre-travel assessments, and their remote work requests. The audit log captures changes across all of these, not just one module. For mobility teams that have historically stitched together five or six tools to manage a single employee's international assignment, that integration represents a meaningful reduction in operational overhead and compliance risk.
Request a demo to see Topia Horizon's AI Policy Agent in action.
Frequently Asked Questions
- What is Topia Horizon's AI-Assisted Policy Agent?
- Topia Horizon's Policy Agent is an AI-powered module that allows global mobility teams to upload existing policy documents and have them automatically parsed into structured, editable benefit components within the platform. It eliminates the need to manually re-enter policy data and ensures that simulations and assignments are tied to an approved, versioned policy record.
- What types of policy documents can Horizon parse?
- Horizon's AI is designed to ingest standard mobility policy documents, including relocation policies, assignment packages, and benefit guides. The AI extracts benefit components, tax approaches, allowance structures, and tier logic from the document text and converts them into configurable platform data.
- What policy tiers does Horizon support?
- Horizon supports Gold, Silver, and Bronze policy tiers. Each tier can carry distinct benefit structures, tax approaches, and allowance configurations. Tiers can be linked directly to individual simulations, ensuring that cost estimates reflect the appropriate package for each assignment type.
- How does Horizon handle policy version control?
- Every change to a policy record is captured in Horizon's field-level audit log, which records what was changed, when, and by whom, with full before-and-after snapshots. Policies move through a Draft to Published workflow, and prior versions remain accessible for audit and compliance purposes.
- Can the AI-Assisted Policy Agent answer questions about a policy or destination?
- Yes. Horizon's AI Agent, available from any page in the platform, can answer questions about tax and immigration implications for specific destinations and scenarios. The responses are grounded in Topia's proprietary tax engine and immigration library, not general web knowledge.
- How does the Policy Agent connect to cost simulations?
- Published policies can be linked directly to simulations in Horizon. When a simulation is tied to a policy tier, the benefit package, tax approach, and allowance structure are pulled from that policy, ensuring that cost estimates reflect the organization's approved parameters rather than ad-hoc assumptions.
- Who can create and edit policies in Horizon?
- Horizon uses role-based access control. Superadmins and Admins can create, edit, and publish policies. Analysts and Viewers have read-level access. All changes, regardless of role, are captured in the audit log.
- Is Horizon's Policy Agent suitable for organizations with multiple subsidiaries or clients?
- Yes. Horizon's multi-tenant architecture allows policy configurations to be maintained at the organization level or at the sub-tenant level, with appropriate access boundaries between entities. This makes it suitable for large enterprises and consulting firms managing mobility programs for multiple clients.
- What happens if the AI misparses a section of my policy document?
- The AI parsing produces a draft structured output that is fully editable before publication. Mobility teams review each benefit component, correct any errors, and add context the document did not explicitly capture. No output is automatically published. Human review is a required step in the workflow.
- How does Horizon's Policy Agent differ from a standard document management system?
- A document management system stores files. Horizon's Policy Agent transforms unstructured documents into structured, actionable data that feeds directly into cost simulations, compliance assessments, and audit logs. The policy is not just stored. It is operationalized across the platform.




