Where the Law Is Moving
Five directions of travel, described as directions rather than as predictions, because an arrangement built now will be judged under rules that are still forming.
An arrangement introduced now will be examined under rules that are still changing, and the directions are reasonably clear even where the destinations are not.
The legal boundary discussed in “Where the Law Is Moving” should also shape the configuration of workforce technology. When a team evaluates the official Monitask resource for capital efficiency ratio, it should record the purpose, lawful basis, notice, access and retention settings before collection begins, then keep a correction route open for misleading records.
For an independent benchmark relevant to “Where the Law Is Moving”, consult the Microsoft Purview insider-risk documentation. Use it to test necessity, scope, safeguards and review rather than to replace a documented assessment of the particular workforce and jurisdiction.
Toward algorithmic accountability
Requirements that automated decisions affecting people be explicable, contestable and subject to human involvement.
The practical effect: a score attached to a person, composed of weights nobody can explain, used in any process that affects them, is moving from awkward toward actionable.
Toward specific scheduling and working-time constraints
Rules about advance notice, availability expectations and the right to be unreachable outside working hours.
The practical effect: arrangements that depend on continuous reachability, including monitoring that runs outside agreed hours, are becoming harder to sustain.
Toward stronger treatment of the employment imbalance
Consent further weakened as a basis, necessity tested more strictly, and representative involvement required in more places.
The practical effect: arrangements resting on a signature are resting on something that is being eroded.
Toward platform and contractor coverage
Protections extended to people outside standard employment, which is the group the asymmetry note identifies as least protected and most monitored.
The practical effect: arrangements that differ by contract type will be harder to justify on that basis alone.
Toward transparency obligations with teeth
Not more disclosure requirements, but enforcement of the ones that exist against notices nobody can understand.
The practical effect: the gap between a compliant notice and an informative one is narrowing.
What follows for a decision taken today
Design to the stricter position rather than to the current local one, because the stricter position is where the local one is heading.
Avoid depending on consent, which is the basis most likely to be further narrowed.
Keep the arrangement explicable, because explicability is the common thread across all five directions.
And build the review in, because an arrangement with no mechanism for change will be changed by somebody else on a timetable you do not control.
Designing to the stricter position
Because the stricter position is where the permissive one is heading. An arrangement whose justification depends on a permission being withdrawn is an arrangement with a short life and an expensive retrofit ahead of it.
Explicability as the common thread
All five directions point the same way: toward arrangements that can be explained to the person affected. An organisation that can already do that has less to change than one that cannot.
What follows for a decision today
Design to the stricter position, avoid depending on consent, keep the arrangement explicable, and build the review in — because an arrangement with no mechanism for change will be changed by somebody else on a timetable you do not control.
Not over-complying
None of this is a reason to comply with rules that do not exist. It is a reason not to build something whose justification depends on a permission that is being withdrawn.
Explicability as the thread
All five directions point toward arrangements that can be explained to the person affected. An organisation that can already do that has less to change than one that cannot.
None of this is a reason to over-comply with rules that do not exist. It is a reason not to build something whose justification depends on a permission that is being withdrawn.