We didn’t open a new office.
We didn’t acquire another company.
We didn’t launch a new division.
A small team simply started working permanently from another state.
At first, it sounded like an operational detail.
The employees could do their jobs remotely, their managers stayed the same, and the team itself wasn’t changing.
Then we started asking questions.
That’s when I realized we hadn’t simply changed where a few laptops were located.
We had expanded where our company had people working.
The First Move Seemed Too Small to Matter
One employee relocated.
Then another person asked whether they could do the same.
A new candidate already lived in another state.
Before long, what began as an exception was becoming a workforce pattern.
That was the moment I stopped treating each request as an isolated management decision.
I needed to understand the bigger picture.
“Remote” Isn’t a Location
This sounds obvious, but it changed the way I kept records.
Saying:
“This person works remotely.”
doesn’t answer the important geographic question.
Remote from where?
Missouri?
Texas?
Colorado?
New York?
Two people can have identical job titles, report to the same manager, and work entirely online while still performing their jobs from different jurisdictions.
The physical location of the company office doesn’t tell the whole story anymore.
I Created a Workforce Map
Nothing sophisticated.
I wanted a simple view showing:
- Where people actually work
- Which teams have people in multiple states
- Which managers supervise distributed teams
- Which locations are temporary
- Which moves are permanent
That immediately made our workforce look different.
On an organizational chart, everyone belonged to familiar departments.
On the map, we were becoming a multi-state employer.
I Stopped Approving Moves as Purely Managerial Decisions
Previously, a manager might think:
“I don’t care where they work as long as performance stays good.”
Operationally, that may be reasonable.
Administratively, it isn’t the only consideration.
I wanted relocation requests to trigger a review before someone permanently changed their work location.
The manager still had a role.
But “my manager said it’s fine” was no longer the entire process.
Different States Can Mean Different Requirements
This was the part that turned a simple relocation into a larger project.
Employment requirements can vary by state.
Depending on the circumstances and location, I may need to consider differences involving areas such as:
- Leave requirements
- Required workplace notices
- Wage-and-hour rules
- Workers’ compensation
- Hiring practices
- Final wage requirements
- Other state or local employment obligations
I don’t assume that a policy written around one state automatically covers every future location.
Our Handbook Suddenly Needed Another Look
We had policies written when almost everyone worked in the same geographic area.
That assumption was embedded in places we hadn’t noticed.
Once people spread across states, I started asking:
Does this policy still work for everyone?
Sometimes the answer was yes.
Sometimes a state-specific difference needed attention.
The important part was identifying the question before a real situation forced us to answer it.
Managers Didn’t Need to Become Compliance Experts
I didn’t expect every manager to memorize employment requirements across the country.
That would be unrealistic.
What I did expect was for managers to recognize when a location change needed another review.
The rule became simple:
Don’t guess.
If an employee is permanently changing where they work, route the change through the appropriate process.
Managers could focus on whether the arrangement worked for the team.
The administrative side could be reviewed separately.
Temporary Travel Created a Different Question
Not every change in location meant someone had relocated.
People travel.
They visit family.
They work somewhere else temporarily.
That meant we needed to distinguish between:
Business travel
Temporary remote work
Permanent relocation
New hire in another state
Those scenarios may look similar on a video call.
They aren’t necessarily the same administratively.
I Needed Better Advance Notice
The worst version of the process was discovering a move afterward.
An employee casually mentions:
“By the way, I’ve been living in another state since last month.”
Now we’re reacting.
I wanted the process to happen before the move whenever possible.
That gave us time to understand the implications instead of reconstructing them later.
Recruiting Started Expanding the Map Too
Relocations weren’t the only reason we became multi-state.
Remote recruiting did the same thing.
A manager might find an excellent candidate and think:
“Great. They can work from anywhere.”
But “anywhere” can create additional considerations for the company.
So we added location earlier in the recruiting conversation.
Not to automatically reject someone.
To know what we were agreeing to before making the decision.
I Started Tracking States as an Operational Variable
Once several locations were involved, geography became something leadership needed visibility into.
I wanted to know:
How many states are we operating in from a workforce perspective?
Where are we adding people?
Are there states with only one person?
Are particular teams becoming highly distributed?
Could our current administrative structure support further expansion?
Those are business questions, not just HR questions.
Workers’ Compensation Was Part of the Conversation
A distributed workforce also made me think more carefully about workers’ compensation arrangements.
I didn’t want to assume that because someone worked from a home office, location stopped mattering.
When our workforce geography changed, I wanted the appropriate coverage and administrative considerations reviewed as part of that change.
The Company’s Policies Needed a Core and Exceptions
I didn’t want twenty completely different handbooks.
At the same time, pretending every location was identical wasn’t realistic.
The approach that made more sense was:
Core company policies
plus
location-specific requirements where necessary.
That preserved company-wide consistency without ignoring legitimate differences.
Where Trion Solutions Becomes Relevant
This is exactly the kind of situation where a PEO relationship can become more valuable as a company expands.
Trion Solutions provides HR outsourcing and administrative support for client organizations.
For a business with people working across multiple states, having additional HR resources can help leadership evaluate workforce processes as geographic complexity increases.
The company still needs to know where its people are working.
Outside support can’t help with a location nobody reported.
That’s why internal communication and external HR support have to work together.
My Location-Change Process
When someone wants to permanently work from another state, I now want to know:
1. Where will the person actually work?
Specific state and location.
2. Is the move temporary or permanent?
Don’t assume.
3. When does it begin?
Advance notice matters.
4. Does the manager support the arrangement?
Operational question.
5. What administrative review is required?
Separate from managerial approval.
6. Do company policies need any location-specific consideration?
Check before assuming.
7. Is the workforce map updated?
Keep leadership’s picture current.
Mistakes I Try to Avoid
❌ Treating “remote” as though it were a geographic location.
❌ Letting permanent moves happen without advance review.
❌ Assuming a manager’s approval answers every question.
❌ Copying one state’s practices everywhere automatically.
❌ Discovering employee locations months later.
❌ Treating temporary travel and permanent relocation as identical.
❌ Hiring nationally without considering where people will actually work.
❌ Expecting managers to interpret every state-specific requirement themselves.
We Didn’t Open Another Office, but the Company Still Expanded
That was the surprising part.
There was no ribbon cutting.
No new building.
No lease.
No moving trucks.
Yet from a workforce perspective, our organization had entered new places.
Once I understood that, remote relocation stopped looking like a simple personal arrangement between an employee and manager.
It became part of how we manage company growth.
A distributed workforce can give a business tremendous flexibility.
But flexibility works better when the administrative structure grows with it.
Now, when someone says:
“It’s only one person moving to another state.”
I don’t assume it’s a massive problem.
But I also don’t assume it’s nothing.
My next question is simply:
“What changes for the company when we officially have someone working there?”
That’s usually where the real conversation begins.