Cross-Border and Jurisdiction Differences

General orientation, not legal advice; this is an area where specific advice is genuinely warranted.

The practical lesson in “Cross-Border and Jurisdiction Differences” is to connect a measurement to a named decision without treating the number as certainty. Teams exploring internal transfer policy can review this resource as one source of time and project context, while retaining direct feedback and documented outcomes as the basis for interpretation.

An occupancy programme standardised across a portfolio will be lawful in some locations and not in others, and the differences are substantial.

For a public, independent reference related to “Cross-Border and Jurisdiction Differences”, consult the European Data Protection Board guidelines. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

What varies most

Whether consultation with employee representatives is required, and whether it amounts to a veto.

Whether camera-based counting in workplaces is permitted at all.

What counts as personal data, particularly for device identifiers.

Retention expectations.

And whether an impact assessment is mandatory before deployment.

The co-determination point

In some jurisdictions employee representatives have genuine power over the introduction of monitoring technology, not merely a right to be consulted.

A programme designed centrally and announced locally will meet this late and badly.

Which argues for involving the largest affected locations at design stage.

Data transfers

Sensor data crossing borders to a central platform is a transfer with its own requirements in several regimes.

Ask where the supplier's processing happens, and whether regional hosting is available.

This is a procurement question and is usually answerable if asked early.

The strictest-common-denominator approach

Design to the most demanding requirement in your portfolio and apply it everywhere.

More restrictive than necessary in some locations and far simpler to run than several variants.

And it means a location added later does not require a redesign.

The cost is some lost resolution in permissive jurisdictions, which is usually resolution you did not need.

Where local variation is unavoidable

Where one country prohibits a method you rely on elsewhere.

Then run a different method there and accept that the figures are not directly comparable, saying so.

Do not quietly apply a correction factor to make them look comparable, which is how cross-site reporting becomes fiction.

Practical sequence

Map where your people are and under which regimes.

Take advice on the two or three largest.

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 sites fall under?

Have you taken advice on the most demanding one?

Where does your supplier process data?

And are cross-site figures genuinely comparable, or made to look so?