Using It in a Dismissal

General orientation, not legal advice; employment law differs substantially by jurisdiction and this is an area to take advice on.

The people decision in “Using It in a Dismissal” cannot safely be reduced to a single activity measure. Used for fireable offenses, this software overview can provide time and project evidence, but expectations, context, documented outcomes and a fair conversation should remain the basis of any management judgement.

When monitoring data appears in a dismissal, every weakness described in this collection becomes a question somebody else gets to ask.

For an independent reference relevant to “Using It in a Dismissal”, consult the Acas workplace guidance; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.

What will be asked

How was this measured, and by what method?

Who decided which applications are productive?

Was the employee told this would be used this way?

Was the same standard applied to others?

What explains the figures other than performance?

Most organisations cannot answer several of these, and the gaps are the case.

The consistency problem

If one person is dismissed on activity data, the standard has to have been applied to everybody.

Which means producing the comparable figures for colleagues, and showing why this person's were different in a way that matters.

A selective use of data that existed for everybody is a difficult position to defend, and it is the usual shape of these cases.

The notice problem

If the policy did not say the data could be used in disciplinary processes, using it that way is a surprise.

Surprises in dismissals are where procedural fairness fails.

And a policy that was vague about it is worse than one that was silent, because vagueness reads as having avoided saying.

The explanation problem

A disciplinary process requires that the employee can understand and respond to the evidence.

A composite score computed by a vendor's weighting is not something anybody can respond to.

Which makes it unusable as the substance of a case, whatever its role in prompting one.

Where it legitimately contributes

Confirming a specific factual matter: whether somebody was logged in during a shift they claimed.

Alongside direct evidence of the actual work.

As a prompt that led to a proper investigation, rather than as the investigation.

The distinction is between data that started an inquiry and data presented as its conclusion.

The practical rule

If the case would not stand without the monitoring data, it is not a case.

Build it on the work: what was required, what was delivered, what was said, what was agreed.

That evidence existed before the software and is what a process can actually test.

Advice before, not after

Involve whoever handles employment matters before the first time this is contemplated.

A position agreed in advance is cheap; one improvised during a case is not.

What to check

Has monitoring data been used in any disciplinary matter?

Does your policy state whether it can be?

Could you produce comparable figures for colleagues if asked?

And would any case stand without the data?