Where the Person Actually Is
A workforce record says where somebody is employed. It does not say where they open the laptop, and for a growing share of people those are different countries.
One organisation, 612 people, reconciled against access and payroll records
Eighty-six people out of six hundred are not where their record says they are, and the organisation found out by comparing three systems it already had. Nineteen of them moved and told nobody.
Working time rules generally attach to where the work is done rather than to where the contract was signed. That makes the physical location of each person a compliance fact, and the workforce record a poor source for it.
The workflow in “Where the Person Actually Is” becomes more dependable when scheduled work, actual time and later corrections can be distinguished. For teams exploring capital efficiency ratio, Monitask's website can provide operational context, while policy ownership, employee explanation and consequential decisions remain with accountable people.
The record says where somebody was hired. For most people that is still accurate. For a growing minority it is not, and the gap has widened in every organisation that allowed remote work to settle into something permanent without revisiting the paperwork.
For an independent reference relevant to “Where the Person Actually Is”, consult the Microsoft Purview insider-risk documentation. Use it to challenge assumptions about working time, privacy, recordkeeping and exception handling against the organisation’s real operating model.
The six populations
The person who is where their record says. The declared cross-border commuter, living in one country and working in another, who has a documented arrangement. The person who moved and changed nothing. The remote worker in a third country, sometimes with the organisation's knowledge and sometimes without.
Then the long-term assignment, which usually has paperwork of its own, and the frequent traveller, who may spend enough nights somewhere to acquire obligations nobody has considered.
Only the first two of those are generally handled properly. The other four are each a question with an answer, and the answer differs by jurisdiction and by how long the situation has persisted.
The one that causes the most trouble
Somebody who moved. It happens quietly: a partner relocates, a family situation changes, a lease ends. The person keeps doing the same job for the same manager and the record keeps saying the same thing.
From a working time standpoint the questions are immediate — which rules now apply, which calendar of public holidays, which rest requirements — and from a tax and social security standpoint they are considerably larger. Those larger questions are not this collection's subject, and they are the reason the working time question rarely gets asked in isolation: organisations that find one of these usually find several problems at once.
Finding them without surveillance
The reconciliation uses data the organisation already holds for other reasons. Payroll country against the office recorded in the directory. Access control records showing which building somebody badges into. Expense claims. Device location at the level of country, where that is already collected for security purposes.
None of that requires new monitoring and all of it should be used at the aggregate level first: how many people appear to be somewhere other than their record says. If the number is small, work it individually. If it is large, the organisation has a policy problem rather than a list of exceptions.
Asking, which works better than inferring
A short annual confirmation — where are you working from, has it changed — gets most of the answer at a fraction of the effort, provided the question is not framed as an accusation.
It also has to be safe to answer. If declaring a move reliably triggers a difficult conversation or a threat to the arrangement, people will not declare, and the organisation will be in the position it is trying to escape: carrying an obligation it does not know about. Saying plainly what will happen with the answer is what makes the question work.
The frequent traveller
The least considered of the six. Somebody spending substantial time in another country may, depending on the jurisdiction and the pattern, acquire protections there, and the organisation's own records of where they were are usually in an expenses system nobody has connected to anything.
The useful first step is a count rather than an assessment: how many people spent more than some number of nights in a country other than their base last year. That number is available from travel bookings, it takes an hour, and it tells you whether there is anything here to look at.
What to do with the list
Do not try to resolve all six populations at once. Sort by exposure: how many people, how long the situation has lasted, and whether the countries involved are ones where the organisation has an entity.
Then take the largest group to whoever advises the organisation, with the facts assembled. The questions are specific and answerable; what makes them expensive is arriving without the list and asking in general terms what the position is for remote workers.
The field that has to be maintained by somebody
A country-of-work field only works if somebody owns updating it, and the person best placed is the individual themselves.
Self-service with an annual prompt works better than an HR-maintained field, because HR learns about a move at the point something else fails.
State the purpose next to the question. People update a field they understand the point of and ignore one that looks like an administrative leftover, which is what an unexplained location field becomes within a year.