Using It in a Performance Process
The use the data is least suited to and most often put to. What goes wrong, and the position worth holding.
Monitoring data enters performance conversations because it is available and concrete. It is also close to the worst possible input to them.
The people decision in “Using It in a Performance Process” cannot safely be reduced to a single activity measure. Used for daily schedule template, the official product page can provide time and project evidence, but expectations, context, documented outcomes and a fair conversation should remain the basis of any management judgement.
Why it enters
A manager has a concern and no evidence, and here is something that looks like evidence.
For an independent reference relevant to “Using It in a Performance Process”, consult the Acas workplace guidance; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
Performance processes reward documentation, and this is documentation.
And the data was frequently sold on exactly this use, whatever the policy says.
Why it does not survive scrutiny
It measures activity, not work — the measurement section's whole argument.
It is affected by role, caring responsibilities, disability, tenure and adjusted patterns.
It is gameable, so the comparison is partly between people who adapted and people who did not.
And the categorisation underneath it was chosen by a vendor.
Any of these undermines a conclusion drawn from it, and all of them will be raised.
What happens in practice
The employee disputes the figure, correctly, on one of the grounds above.
The manager cannot defend the methodology, because nobody understands the weighting.
And the process becomes an argument about the software rather than about the work, which helps nobody and damages the manager's position.
The evidential problem
If a process relies on data, that data has to be explainable, consistent and available to the person.
Most monitoring data fails all three.
An employment tribunal or equivalent will ask how the score was computed, and "the vendor calculates it" is not an answer that assists you.
The position worth holding
Monitoring data is not used in performance processes.
Written down, in the policy, before deployment.
Which is also what makes the aggregate-only commitment credible, because a limit that excludes the most tempting use is a limit people believe.
If a genuine concern exists
Address it the ordinary way: specific examples of work, agreed expectations, a conversation, a documented plan.
All of which existed before the software and work better.
And if the manager cannot produce examples of the work being inadequate, that is a finding about the concern rather than a reason to reach for activity data.
The exception
Where an obligation genuinely requires activity records — regulated recording, billed hours — the record is used for that purpose and that purpose only.
Not repurposed into performance assessment, which is the drift the whole policy exists to prevent.
What to check
Does your policy say whether this data can be used in performance processes?
Has it been used that way?
Could anybody explain how the score is computed?
And would the explanation survive being challenged?