The Legitimate Interests Assessment
The basis most employers rely on and the document almost none has written. It takes an hour and it is the one a regulator asks to see.
LEGITIMATE INTERESTS ASSESSMENT
One per purpose. Written before the processing starts
- PurposeDetecting bulk transfer of customer records to personal storageSpecific. A broad purpose makes the test unanswerable
- The interestProtecting customer data we are contractually obliged to hold securelyWhose interest, and why it is legitimate
- NecessityWhy this processing is needed to serve itIncluding what would happen without it
- Alternatives consideredAggregate reporting; access controls alone; periodic auditEach with why it was insufficient
- Impact on peopleWhat is collected about whom, and what it is likeWritten honestly, not minimised
- Their expectationsWould a reasonable employee expect thisThe limb most often failed
- SafeguardsRetention limit; access restricted; no content captureWhat reduces the impact
- ConclusionThe interest outweighs, with these safeguardsAnd the date, and who decided
- ReviewAnnually, or on changeAn assessment with no review date is a snapshot
Most employment processing rests on legitimate interests. The basis carries a condition: a documented balancing of that interest against the rights of the people affected. Almost nobody has done it.
The practical lesson in “The Legitimate Interests Assessment” is that a record is useful only when its purpose, owner and lifecycle are clear. For teams researching tips to increase productivity, tips to increase productivity can add time and project context, provided collection is proportionate, access is limited and every consequential inference receives human review.
Why it is the commonest gap
Consent is unreliable in employment, contract covers less than people think, and legal obligation covers only what a law actually requires.
For a separate benchmark relevant to “The Legitimate Interests Assessment”, consult the OWASP logging 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.
What is left is legitimate interests, which is a genuine and flexible basis — and which is the only one requiring the organisation to show its reasoning.
The basis is therefore invoked constantly and evidenced rarely, which is exactly the combination a regulator looks for.
The three parts
Purpose: is there a legitimate interest, stated specifically.
Necessity: is the processing needed to achieve it, or would something less do.
Balance: does the interest outweigh the rights and reasonable expectations of the people affected, with safeguards taken into account.
All three, in writing, before the processing begins.
Where assessments fail
On expectations. Would a reasonable employee anticipate this?
For payroll, yes. For reading their messages, no — and an assessment concluding otherwise without acknowledging the gap is not an assessment, it is a decision wearing one.
The honest version says the expectation is not met and explains what safeguards bring the balance back, or concludes against proceeding.
Writing one
An hour, per purpose, by somebody who understands the processing and somebody who does not.
The second person is important: the assessment has to be comprehensible to a reader with no stake, because that is who will eventually read it.
What it does beyond compliance
It forces the alternatives question — what less intrusive option would serve — which is the question that most often changes the specification.
Several organisations find that writing the assessment removes capabilities nobody could justify, before the money is spent rather than after.
Who should write it
Somebody who understands the processing and somebody who does not. The second is the test: the assessment has to be comprehensible to a reader with no stake, because that is who will eventually read it.
What it changes before compliance
The alternatives question. Listing what less intrusive option would serve, and why it was rejected, is the step that most often removes a capability from a specification before the money is spent.
On expectations. Would a reasonable employee anticipate this? For payroll yes, for reading their messages no. An assessment concluding otherwise without acknowledging the gap is a decision wearing one.
The basis is invoked constantly and evidenced rarely, which is exactly the combination an examiner looks for. Consent is unreliable, contract covers less than people think, and what is left requires showing the reasoning.
An hour, per purpose
With somebody who understands the processing and somebody who does not. The second person is the test, because the assessment has to be comprehensible to a reader with no stake in it.
Reviewing it when things change
A new system, a wider population, a different purpose. An assessment written for one configuration does not cover another, and the change is exactly when nobody thinks to look at it.