In my role as a Global Mobility Manager, after my first week, I found myself wondering, “Is there not a system that can help me manage the workload?”.
During the interviews, I assumed a system was in place - like an applicant tracking system or a case management system. There’s no way all this work is managed in Excel… And yet, for so many mobility teams, that’s exactly what’s happening.
Over the years – both as a practitioner and now working with programs of all sizes, I’ve heard the same questions come up again and again.
Questions about tracking workload → About reporting → About proving value → About whether there’s a better way.....
Navi was built to help answer those questions. So, if you’re curious about what that looks like in practice, here are a few of the questions I’m asked most often – and the answers.
This is usually where someone says, “Ok, but what does it really do?”....
I get it. I’ve lived the spreadsheets. I’ve rebuilt assignment letters at 9pm. I’ve pieced together reports from five different places just to answer one simple leadership question.
At its core, Navi helps you plan moves, manage ongoing allowance compensation, and actually see your mobility program clearly. Here’s what that looks like in practice:
Plan smarter. Build multiple scenarios, compare policies side-by-side, and understand cost impacts before a move is approved. Not after.
Generate compensation statements and offer letters automatically. No more copying old templates and hoping you didn’t miss a detail. Navi pulls in employee and policy data to create accurate documents quickly.
Manage your entire population in one place. Every mobile employee lives in a centralized table, with a connected employee record that ties together details, benefits, reports, and history.
Gain visibility. The dashboard gives you a real-time view of your program – where people are, what policies are being used, whose move is about to start and whose is ending – all in one place.
So, what can you do with Navi?
You can move from reactive to proactive.
From manual to streamlined.
From scrambling for answers to having them at your fingertips.
And if you’ve ever had to prove the value of your mobility program with nothing but spreadsheets and hope…that shift matters.
This is usually the quiet concern behind the scenes: How much work is moving to Navi going to take?
The good news? You have options, and you don’t have to make everything perfect on Day One.
Add employees one at a time. Create a record for a new move, and that record becomes the central hub for their details, reports, and history.
Import your population in bulk. Use Excel templates to upload multiple employees at once – no manual re-typing required. Once uploaded, they appear in the My Employees table where you can search, filter, and manage them centrally.
Refine as you go. You can partially complete records and update them later.
You don’t have to start from scratch. You can start small. Or bring everything in at once. Either way, everything finally lives in one place.
Let’s be honest – this question comes up almost immediately. And it should. Integration can either make your life easier… or become the next six-month project that never quite gets finished. Clarity matters. Here’s where things are today:
Navi does not run payroll calculations.
It does support ongoing allowance calculations within the platform.
HRIS integrations can be initiated by clients, and system connections are planned to allow information exchange with HRIS platforms.
Vendor initiations and workflow functionality are also planned for future releases.
In other words: Navi today is focused on planning, managing, and documenting mobility, not replacing payroll or becoming a full workflow engine.
This is usually where the conversation gets practical, because at some point – whether it’s the business or the employee – someone is going to ask:
“But what does that mean for their take-home pay?”
Here’s the clear answer:
Yes, Navi displays employee net salary information for permanent transfers within the detailed cost comparison report, including both a high-level summary view and a full breakdown. That might sound simple. But not every system makes net salary visibility easy. Sometimes you’re exporting numbers, building side spreadsheets, or toggling between reports just to piece together the employee impact.
With Navi, net salary is integrated directly into the cost estimate results. So, in one structured report, you can see:
The cost to company
The employee’s net position
And the assumptions driving both
No separate calculations. No unnecessary back-and-forth. And when you’re preparing for a conversation with HR, Finance, or the employee themselves, having that clarity in one place changes the dynamic.
If you’ve ever presented a cost estimate to leadership and someone asked, “Wait – how did we get that tax number?”, you know that confidence can disappear quickly.
Here’s the honest answer:
The tax calculations in Navi are not a black box. They are built on AIRINC’s underlying tax and cost methodologies. The same research and assumptions mobility teams have relied on for over 70 years. But what makes the difference is that the results don’t just appear as one mysterious total. Within a scenario or cost comparison, you can:
See the calculated outputs tied to the specific assumptions used
Review the benefits and compensation inputs driving the tax impact
Generate detailed reports that break down the components behind the estimate
Re-run scenarios if inputs change, so you can see exactly what shifted and why
In other words, you’re not just given a number. You can trace it back to the inputs and policy structure that created it. That matters.
Mobility isn’t just about calculating taxes; it’s about explaining them. To Finance. To HR. Sometimes even to the employee.
When someone challenges a figure, being able to say, “Here’s what’s included. Here are the assumptions and how it was calculated”, changes the conversation entirely. Transparency builds credibility.
If you’ve ever managed allowances manually, you already know why this question matters. Because “update season” usually means opening one spreadsheet…then another…then realizing three employees were missed because their data lived somewhere else.
Automatic allowance updates are designed to take that off your plate.
Here’s how it works in practice:
Allowances are tied to your policies and the underlying data that supports them. When new data is released - for example, updated cost assumptions – Navi can automatically recalculate eligible allowances for the employees connected to that policy. Instead of updating one employee at a time, you can apply updates across a group which means:
No rebuilding calculations manually
No copying formulas forward
No wondering whether everyone was included
Since everything is connected back to the employee record and benefits tab, changes are tracked and time-stamped. You maintain control. You can also:
Lock specific values if needed
Override amounts for individual cases
Review updates before finalizing reports
So, it’s not a blind “push update and hope” process. It’s structured automation with oversight.
If you’ve ever created assignment letters manually, you already know this routine.
Open last year’s version ⇒ Save as ⇒ Search and replace the name ⇒ Update the dates ⇒ Hope you didn’t miss a number buried three pages down....
That works just fine…until it doesn’t. Here’s how it works in Navi:
Assignment letters are generated using a dynamic document template that pulls directly from the employee’s record and their assigned policy. The template will be created using company branding – company specific language, fonts, color schemes or logos.
That means:
Employee details come from the record
Benefits and allowance reflect the policy setup
The document builder automatically inserts the right data into the right place
You can use a standard template or customize your own. Once generated, the letter can be downloaded and shared.
So, instead of recreating the letter each time, you’re generating it from structured data that already lives in the system. You’re not pulling numbers from memory or a separate spreadsheet. The letter reflects what’s actually been calculated and approved. This means fewer manual errors. Fewer version-control headaches. And far less last-minute scrambling before sending it out.
Yes and this is one of those features you don’t think about…until you really need it, because at some point someone will ask:
“When was this updated?” “Who changed that value?” “Can we see the original report?”
Navi includes a History tab within each employee record that logs changes and stores previously generated reports. That means:
Updates to the record are time-stamped
Prior reports can be viewed and downloaded
You have a documented trail of what changed and when
On the Benefits tab specifically, changes are also tracked, supporting visibility into overrides, adjustments, and policy exceptions. No longer are you relying on email chains or version names like “Final_v3_Updated_ReallyFinal.xlsx.”. You have a structured, system-based record. In mobility, where compensation, allowances, and tax assumptions evolve over time, that kind of traceability isn’t just helpful. It’s protective.
Well this is one of my favorite questions. Because Navi wasn’t designed in a vacuum. It wasn’t built by a generic software team trying to “enter the mobility space.” It was shaped by people who have actually lived the spreadsheets, the inbox archeology, the end-of-year reporting scramble.
Navi was designed this way because mobility teams were spending too much time:
Rebuilding cost estimates
Manually updating allowances
Copying and pasting assignment letters
Trying to prove the value of their program with disconnected data
At it’s core, Navi was built to help mobility teams make good decisions from the start; not just execute once everything is approved.
This is why:
Scenario planning sits at the center
Policies drive structure and consistency
The employee record acts as a single hub for everything tied to a move
The dashboard provides program-level visibility, not just individual transactions
It’s intentionally structured, not to add complexity, but to remove the chaos that creeps in when data lives in five different places. Maybe, most importantly, it was designed to be usable by mobility professionals, not just IT.
The goal wasn’t to create another system for you to manage. It was to create one that actually makes your job easier.
And if you’ve ever sat at your desk wondering whether there had to be a better way to manage all of it – that’s exactly why Navi exists.