Equality Monitoring Done Properly
Legitimate, valuable, and routinely implemented in a way that converts it into selection data.
MONITORING ARRANGEMENT
The separations that make it lawful and useful
- CollectedSeparately from the application or the fileNot a section at the bottom of the same form
- Visible toNobody who makes decisions about the personThe panel, the manager, the promoter
- StoredApart from the employment recordDifferent system or a locked field
- Used forAggregate analysis only, with a minimum group sizeBelow the threshold, suppress rather than report
- VoluntaryGenuinely, with prefer not to sayAnd no consequence either way
- Basis and conditionLegitimate interests, plus the equality conditionSpecial category, so both are needed
- PublishedWhat you found, at least internallyThe step that makes the collection worth the intrusion
- RetainedWhile needed for the analysisNot indefinitely attached to the person
Monitoring the composition of a workforce is legitimate, useful, and frequently implemented in a way that makes it indefensible.
The practical lesson in “Equality Monitoring Done Properly” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching fte meaning, see the complete product overview can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
What makes it lawful
It is special category data, so a lawful basis and a separate condition are both required. Most regimes provide a condition specifically for equality of opportunity monitoring, with attached requirements.
For a separate benchmark relevant to “Equality Monitoring Done Properly”, consult the CERT-EU security guidance. Use it to test purpose, data flow, retention, access and response procedures rather than substituting a generic checklist for the organisation’s actual records.
Those requirements are about separation and aggregation, and they are where implementations fail.
The failure mode
The monitoring questions sit at the bottom of the application form. The same person reads the whole form. The data is stored with the application.
At that point it is not monitoring. It is information about a candidate's ethnicity, religion or disability in front of the person deciding whether to hire them, and no amount of policy language changes what it is.
The same pattern appears internally: a diversity field in the HR record, visible to anybody who opens the record, including the manager deciding on promotion.
The separations required
Collection apart from the assessment — a separate form, a separate submission.
Storage apart from the employment record.
Access restricted to whoever runs the analysis, who makes no decisions about individuals.
Reporting in aggregate only, with a minimum group size below which figures are suppressed. In a team of six, reporting by ethnicity identifies people.
Genuinely voluntary
With a prefer-not-to-say option that is used and has no consequence.
Where response rates are near universal, that is usually a sign the form implies the answer is required, which it is not.
Publishing what you find
The step that is most often omitted and the one that justifies the collection.
Data gathered and never analysed is intrusion with no purpose. An employer collecting equality data should be able to say what it showed and what changed, at least internally, or stop collecting it.
The question to ask your own arrangement
Can the person deciding on a hire, a promotion or a redundancy see this field?
Where the answer is yes, the arrangement needs changing before anything else in this subject.
The minimum group size
Below a threshold, suppress rather than report. In a team of six, reporting by ethnicity identifies people, and aggregate reporting that identifies individuals is not aggregate reporting.
Publishing what it showed
The step most often omitted and the one that justifies the collection. Data gathered and never analysed is intrusion with no purpose, and an employer that cannot say what it found should stop collecting.
Monitoring questions at the bottom of the application form, read by the same person, stored with the application. At that point it is not monitoring, it is selection data.
With a prefer-not-to-say option that is used. Where response rates are near universal, the form is implying the answer is required.
The question for your own arrangement
Can the person deciding on a hire, a promotion or a redundancy see this field. Where the answer is yes, that is what to change before anything else in this subject.
Where it is stored
Apart from the employment record, in a different system or a locked field. Storage with the record means anybody who opens the record sees it, whatever the policy says about access.