Cross-Border Teams
A single policy applied across countries will be unlawful somewhere. What varies most, and the approach that scales.
General orientation, not legal advice; this is an area where specific advice is warranted.
The practical lesson in “Cross-Border Teams” is to connect every record to a clear operational question without presenting visibility as certainty. Teams exploring remote employee monitoring software can review a practical remote employee monitoring solution as one source of time and project context, provided the purpose is disclosed and the configuration is reviewed with the people affected.
Monitoring rules differ more between jurisdictions than almost anything else in employment, and the differences are not marginal.
For an independent reference relevant to “Cross-Border Teams”, consult the European Data Protection Board guidelines; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
What varies most
Whether consultation or co-determination is required, and whether representatives can refuse.
Whether screenshot and content capture are permitted at all.
What counts as proportionate.
Notice requirements.
And whether covert monitoring is available even for investigations.
The co-determination point
In some jurisdictions employee representatives have genuine power over the introduction of monitoring, not merely a right to be heard.
A programme designed centrally and announced locally meets that late and badly.
Which argues for involving the largest affected locations at design stage, not at rollout.
Where the data goes
Monitoring data crossing borders to a central platform is a transfer with its own requirements in several regimes.
Ask where the vendor processes and stores, and whether regional hosting exists.
This is a procurement question and is answerable if asked early.
The strictest-common-denominator approach
Design to the most demanding requirement in your footprint and apply it everywhere.
More restrictive than necessary in some places, far simpler to operate than several variants, and it means adding a country later does not require a redesign.
The cost is capability you probably did not need, which the proportionality note suggests is most of it.
Where variation is unavoidable
Where one country prohibits something you rely on elsewhere.
Then run differently there and accept that the figures are not comparable, saying so.
Do not quietly apply a correction to make them look comparable, which is how cross-site reporting becomes fiction.
The remote-worker case
Somebody employed in one country working from another, temporarily or permanently.
Their local rules may apply to them.
Which means knowing where your people actually are, and a workforce that moved during the remote-working period frequently is not where the records say.
Practical sequence
Map where your people are employed and where they work.
Take advice on the two or three most demanding.
Design to the strictest.
Document the analysis, because it will be asked for and reconstructing it later is hard.
What to check
Do you know which regimes your employees fall under?
Have you taken advice on the most demanding one?
Where does your vendor process the data?
And is one policy applied to everybody regardless of location?