Data Protection Impact Assessment and Article 9 analysis
The scored index is ordinary personal data. The optional monitoring section is special category data and runs under a named statutory condition. Both positions are set out below in full.
Scored data
Ordinary personal data. Article 9 not engaged.
Monitoring data
Special category. Article 9(2)(g) with a Schedule 1 condition.
Automated decisions
None. Article 22 not engaged.
Individual outputs
None produced under any configuration.
001
Which data is special category, and which is not
( Classification )
Article 9
The scored index is ordinary personal data
Every variable contributing to the background index is ordinary personal data under the UK GDPR. Parental occupation, parental education, free school meal eligibility, childhood housing tenure, household financial circumstances, school type and class size are none of them within the Article 9 categories, and none of them is a protected characteristic under the Equality Act 2010.
This is the central design property of the instrument. It means the scored index can lawfully inform workforce policy under Article 6 alone. The lawful basis is Article 6(1)(f), legitimate interests, being the employer's interest in understanding and correcting structural inequity in its own pay and progression systems. A legitimate interests assessment is completed with each client during onboarding.
A point that is frequently misunderstood
Sex is not special category data. Article 9 covers racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used for identification, data concerning health, and data concerning sex life or sexual orientation. Sex itself is not in that list and is processed under Article 6 in the ordinary way. Disability is not a listed category either, and is processed as data concerning health, which is listed.
The classification in full
| Field | Classification | Basis |
|---|---|---|
| Parental occupation, parental education, free school meals, housing tenure, household finances, school type, class size | Ordinary personal data | Art 6(1)(f) |
| Sex, age band, region of upbringing, country of birth, caring responsibilities, relationship status | Ordinary personal data | Art 6(1)(f) |
| Ethnic group | Special category | Art 9(2)(g), Sch 1 para 8 |
| Religion, where included | Special category | Art 9(2)(g), Sch 1 para 8 |
| Disability or long term health condition | Special category | Art 9(2)(g), Sch 1 para 8 |
002
Substantial public interest, and the condition we rely on
( The Article 9 gateway )
Schedule 1, para 8
Article 9(2)(g) permits processing of special category data where it is necessary for reasons of substantial public interest, on the basis of domestic law which is proportionate to the aim pursued, respects the essence of the right to data protection, and provides suitable and specific safeguards.
In the United Kingdom that domestic law is the Data Protection Act 2018. To rely on Article 9(2)(g) a controller must meet one of the substantial public interest conditions in Part 2 of Schedule 1. The condition relied on here is paragraph 8, equality of opportunity or treatment.
Schedule 1, paragraph 8(1)
This condition is met if the processing is of a specified category of personal data, and is necessary for the purposes of identifying or keeping under review the existence or absence of equality of opportunity or treatment between groups of people specified in relation to that category with a view to enabling such equality to be promoted or maintained.
Paragraph 8(2) specifies the categories and the groups they must be considered against. Racial or ethnic origin data is specified in relation to people of different racial or ethnic origins. Religious or philosophical belief data is specified in relation to people holding different beliefs. Health data is specified in relation to people of different states of physical or mental health. Sexual orientation data is also specified, and PRISM does not collect it.
PRISM's monitoring processing sits squarely inside this condition. It exists to identify and keep under review whether equality of opportunity exists between those groups, with a view to enabling equality to be promoted. That is the only purpose the data is put to.
003
Three exceptions defeat the condition. The product is built around all three.
( Statutory exceptions )
8(4) and 8(5)
Exception one, paragraph 8(3)
The condition is not met if processing is carried out for the purposes of measures or decisions with respect to a particular data subject.
This explains a design choice that otherwise looks like excessive caution. PRISM produces no individual output of any kind. Individual scores exist only as intermediate values inside the analytical environment. They are never exposed in a deliverable, a dashboard or an export, they are never visible to any manager, and no output is designed or permitted to inform a decision about a named person. A minimum group size of thirty applies to everything reported, rising to fifty where characteristics are crossed with one another.
A product that scored protected characteristics and then recommended individual pay adjustments would fail this exception immediately, and with it the entire lawful basis.
Exception two, paragraph 8(4)
The condition is not met if the processing is likely to cause substantial damage or substantial distress to an individual.
Assessed as satisfied. Because nothing is reported at individual level, no employee can be identified, singled out, ranked or compared through a PRISM output. Participation is voluntary at question level, survey language is tested for tone before deployment, band labels describe origin rather than worth, and no employee ever receives their own score or that of a colleague. The residual risk is the discomfort some people feel at being asked about their childhood at all, which is addressed through the communications approach and by making every question skippable without consequence.
Exception three, paragraph 8(5)
The condition is not met where the data subject has given written notice requiring the controller not to process their data, a reasonable period was allowed, and that period has ended.
An objection route is established at the start of every engagement and communicated to the workforce alongside the survey invitation. Where an employee gives notice, their record is removed from processing within the stated period and excluded from all subsequent analysis. Because the survey is voluntary in the first place this route is rarely needed, but it exists, it is documented, and it is operational rather than theoretical.
004
Appropriate Policy Document
( Schedule 1, Part 4 )
Part 2 condition
A condition in Part 2 of Schedule 1 is met only if the controller has an appropriate policy document in place at the time of the processing. Part 4 sets out what that document must contain, and EconPact maintains one covering every engagement.
| Requirement | How it is met |
|---|---|
| Explain procedures for securing compliance with the Article 5 principles | The document sets out how lawfulness and fairness, purpose limitation, data minimisation, accuracy, storage limitation, integrity and confidentiality, and accountability are each addressed for this specific processing. |
| Explain retention and erasure policies, with an indication of how long data is likely to be retained | Survey responses and the identifier mapping are retained for the agreed engagement period plus a defined review window, after which the mapping is destroyed. Retention periods are agreed in writing before any survey is deployed. |
| Retain the document, review it, and update it as appropriate | Reviewed at least annually and on any material change to the instrument or the processing. |
| Retain until six months after the processing ends, and provide it to the Commissioner on request without charge | Adopted as policy. The document is available to the Information Commissioner on request, and to any client on request. |
005
The impact assessment, structured against Article 35(7)
( DPIA )
necessity, risk
Why an assessment is required
A DPIA is required where processing is likely to result in a high risk to the rights and freedoms of individuals. This processing meets several recognised screening triggers, and we treat the assessment as mandatory rather than discretionary in every case.
| Trigger | Present |
|---|---|
| Processing of special category data | Yes, in the optional monitoring section |
| Data about vulnerable data subjects, including employees | Yes, the employment relationship is imbalanced by nature |
| Data matching or combining datasets | Yes, survey responses joined to workforce records |
| Evaluation or scoring | Yes, at population level |
| Novel application of a measurement technique | Yes |
Systematic description of the processing
Nature.Employees are invited to complete a voluntary questionnaire about parental occupation, parental education, childhood material circumstances and schooling, with an optional equality monitoring section. Responses are pseudonymised at the point of collection. The employer separately provides workforce records covering job level, tenure, compensation, performance rating, function and, where in scope, recruitment and progression history. The two datasets are joined by a pseudonymous identifier inside a controlled analytical environment. Statistical models estimate the association between background and outcomes at population level. Aggregate findings are produced. The identifier mapping is destroyed at the agreed retention date.
Scope.Employees within an agreed population, normally a defined business unit or the whole organisation. Candidate data, where the hiring module is in scope, is collected voluntarily at application and firewalled from every hiring decision.
Context.The employment relationship carries an inherent imbalance of power, which is why the survey is voluntary at question level, why no individual output exists, and why consent is deliberately not used as the lawful basis. Consent obtained by an employer from an employee is rarely freely given, and relying on it here would be the weaker and less honest choice.
Purpose.To identify and keep under review whether equality of opportunity exists within the organisation, to quantify any structural gap, to size what correcting it would require, and to test whether measures taken actually work.
Data flows.Collection through a hosted survey instrument, transfer of workforce records by secure transfer to an agreed template, processing inside a controlled environment with access limited to named analysts, and output as aggregate documents. No data is transferred outside the United Kingdom or the European Economic Area without an agreed transfer mechanism recorded in the client agreement.
Necessity and proportionality
Is the processing necessary?Whether background predicts pay and progression inside a specific organisation cannot be answered without data about background from that organisation. No existing workforce record contains it, and public benchmarks describe the national population rather than a firm's own position.
Is there a less intrusive way?Considered and rejected in three forms. Inferring background from names, postcodes or universities would avoid asking people anything, and is refused outright as both intrusive and unlawful in this context. Using existing demographic data alone would not measure background at all. Sampling a smaller group would reduce the data collected but produce estimates too uncertain to act on, which fails the purpose while still processing personal data.
Data minimisation.The instrument was reduced deliberately. Several variables the underlying research found predictive were removed because their intrusiveness or unreliability outweighed their contribution, including birth circumstances, physical fitness, personality measures and family size. What remains is the smallest set that supports a defensible estimate.
Proportionality of the outputs.Outputs are aggregate only. Granularity is capped by minimum group sizes rather than by what the data would technically permit. Where a population cannot support a breakdown, the breakdown is removed from scope rather than published with wide uncertainty.
Accuracy.Background data is self reported and treated as such. Non-response is recorded rather than imputed, and the proportion appears in every deliverable.
006
Every risk identified, and what is done about it
( Risks and measures )
mitigation
Risks to rights and freedoms, before mitigation
| Risk | Likelihood | Severity |
|---|---|---|
| Re-identification of an individual from a small reported group | Medium | High |
| Function creep, where background data is later used for a decision about a person | Medium | High |
| Employees feel compelled to disclose personal history to their employer | Medium | Medium |
| Distress caused by the subject matter itself | Low | Medium |
| Unauthorised access to combined survey and pay data | Low | High |
| Findings misread as evidence about a named individual's pay | Medium | Medium |
| Excessive retention of the identifier mapping | Low | Medium |
| Group level stigmatisation of employees in a reported band | Low | Medium |
Measures, and residual risk
| Risk | Measure | Residual |
|---|---|---|
| Re-identification | Minimum group size of thirty for any reported figure, fifty where characteristics are crossed. Secondary suppression applied where a suppressed group could be recovered by subtraction from a published total. Suppressed groups shown as suppressed rather than removed. | Low |
| Function creep | No individual output exists in any configuration. Individual scores are not exportable. Contractual prohibition on use for decisions about identified individuals. Access control rather than policy alone enforces the separation. | Low |
| Compelled disclosure | Every question skippable without consequence. Non-response treated as missing rather than filled with a mid point value, so declining carries neither advantage nor penalty. Communications state plainly that participation is optional and that no individual result is produced. | Low |
| Distress | Questions restricted to parents, childhood and schooling. Nothing asked about current finances, beliefs or lifestyle. Intrusive variables removed from the instrument. Objection route published with the invitation. | Low |
| Unauthorised access | Identifier mapping held separately from responses, and held by the client wherever their systems permit. Engagement analysts do not hold the mapping. Access limited to named individuals. Encryption in transit and at rest. | Low |
| Misreading of findings | Confidence intervals on every estimate. Explicit statement in every deliverable that findings are associations at population level and do not establish that any particular decision was caused by any particular person's background. | Low |
| Excessive retention | Retention agreed in writing before deployment. Mapping destroyed at the agreed date, after which the residual dataset is genuinely anonymised. | Low |
| Stigmatisation | Band labels follow the government standard and describe origin rather than worth. Reporting is framed as diagnosis of a structure rather than description of people. | Low |
Automated decision making
Article 22 gives individuals the right not to be subject to a decision based solely on automated processing which produces legal effects or similarly significant effects.
Article 22 is not engaged. No decision about any identified individual is produced by the system, whether automated or otherwise. The outputs are population level estimates informing organisational policy. The scoring that occurs is a step in a statistical estimate rather than an assessment applied to a person, and it never surfaces at individual level. This is enforced by construction rather than by undertaking.
007
Rights, roles, and how findings reach you
( Delivery )
processor, counsel
Individual rights
| Right | Position |
|---|---|
| To be informed | Privacy information provided with the survey invitation, before any question is answered. |
| Of access | Available through the employer as controller while the identifier mapping exists. After the mapping is destroyed the data is anonymous and access no longer applies, which is explained in advance. |
| To rectification | Available while the mapping exists. |
| To erasure | Available on request while the mapping exists. |
| To object | Available generally, and specifically through the Schedule 1 paragraph 8(5) notice route for the monitoring data. |
| Related to automated decision making | Not applicable, as no such decisions are made. |
Pseudonymised, not anonymised
Survey responses are linked to workforce records by a pseudonymous identifier. Because that linkage exists, the data remains personal data and the full regime applies to it.
A great many vendors describe the same arrangement as anonymised, which is inaccurate and misrepresents the client's obligations. Anonymisation arrives only at the point the mapping is destroyed.
Roles
The client is controller for the workforce data and for the survey data relating to its employees. EconPact acts as processor under a written agreement meeting Article 28, and as controller for the anonymised residual dataset retained for population benchmarking after the mapping is destroyed. Sub-processors are listed in the client agreement, and no new sub-processor is engaged without notice.
Delivery through counsel
An engagement may be commissioned by the client's legal counsel, with deliverables addressed to counsel and prepared for the purpose of obtaining legal advice. Clients frequently prefer this, because a structural equity diagnostic produces written findings about the organisation's own pay outcomes and they are entitled to take advice on those findings before deciding what to do with them. Whether privilege attaches in any particular case is a matter for the client's own counsel.
Consultation, sign-off and review
The client specific assessment is completed jointly with the client's data protection officer and reviewed with employee representatives or a works council where one exists. It is signed off before any survey is deployed, and no fieldwork begins without it.
Where high risk would remain after mitigation, the controller must consult the Information Commissioner before proceeding. On the assessment above, residual risk is low across every identified category and prior consultation is not triggered. That conclusion is reviewed for each engagement rather than assumed from this document. The assessment is reviewed annually, and on any material change to the instrument, the analysis or the scope.
If your data protection officer wants to speak to ours before anything else happens, that is the normal order of events here.
Arrange a governance call→