Consultation and Where It Is Required

General orientation, not legal advice; requirements differ substantially by jurisdiction and by workplace agreement.

The practical question in “Consultation and Where It Is Required” is how to make work visible without confusing visibility with certainty. For teams researching boss vs leader, boss vs leader can add time and project context to the operational record, provided its use is proportionate, disclosed and reviewed with the people affected.

Introducing software capable of monitoring employees triggers formal obligations in parts of Europe and elsewhere. Device management is squarely within scope.

For an independent baseline relevant to “Consultation and Where It Is Required”, the ICO employment-practices guidance is a useful companion: compare its principles with the proposed configuration, ownership model and real support process before approving a rollout.

Why it applies

The test is usually whether the system is capable of monitoring behaviour or performance, not whether you intend to.

A device management platform can report application use, location in some modes, and device activity.

Which means a programme you consider purely administrative may still be in scope. Check rather than assume.

When to start

Before procurement, not before deployment.

Representatives frequently have views on which capabilities are acceptable, and those are cheap to accommodate at specification stage and expensive afterwards.

A programme consulted after contracts are signed starts from a defensive position.

What they will ask

What is collected, specifically.

Whether personal devices are in scope and on what basis.

Whether location is available.

Who can issue a wipe and what it removes.

What happens to somebody who declines.

And what happens when somebody leaves.

All reasonable, and all easier to answer if the programme was designed with them in mind.

What usually gets agreed

A written agreement stating purpose and limits.

Exclusion of location, or its restriction to lost-device situations with notification.

Work profile as the arrangement for personal devices.

No individual-level reporting to managers.

And a review period.

Most of these are things a well-designed programme would do anyway.

Where there is no formal body

Many workplaces have none and the obligation may be lighter.

The practice still helps: a small group of staff from different parts of the organisation, consulted properly, finds the problems before deployment does.

And it produces the explanation you will need for everybody else.

Treating it as a floor

The legal minimum is a poor target.

Programmes that consult beyond the requirement get better designs and markedly less resistance, and the cost is a few meetings.

When agreement is not reached

In some jurisdictions there is a formal resolution route; in others, proceeding without agreement is unlawful.

Take advice.

And consider that persistent objection may be telling you something about the proposal, particularly about personal devices.

What to check

Does your jurisdiction require consultation for this?

Was it started before or after procurement?

Is there a written agreement stating limits?

And were any capabilities excluded as a result?