Define the activity before choosing the label
“Customer administration” is often too broad to be useful. Fulfilling an order, retaining an invoice, analysing buying habits and sending promotional messages can involve the same person but different purposes. Write them as separate activities before selecting a basis. Otherwise a legitimate operational need can become a convenient explanation for unrelated uses.
The UK GDPR now provides seven lawful bases, including recognised legitimate interest alongside the familiar bases of consent, contract, legal obligation, vital interests, public task and legitimate interests. There is no universal safest choice. The appropriate basis follows the activity and relationship, and should be identified and documented before processing begins.
Contract and legal obligation need a real connection
Contract can apply where processing is necessary to perform a contract with the individual, or take requested steps before entering one. A contractual clause does not make an unrelated activity necessary simply because the business inserted it into its terms. Ask whether the promised service could reasonably be delivered without that use.
For legal obligation, identify the actual requirement rather than writing “required by law” in a spreadsheet. A contractual obligation owed to another business is not automatically this lawful basis. Our suggested decision record captures the relevant rule, the information it requires and the responsible owner. Where no clear legal requirement can be identified, investigate rather than repeating the assertion.
Use the three-part legitimate interests assessment
Ordinary legitimate interests involves considering the purpose, necessity and balance against the person’s interests and rights. A commercial interest can be legitimate, but that does not conclude the assessment. Explain whose interest is served and why the proposed processing is a proportionate way of achieving it.
At the balancing stage, examine reasonable expectations, the relationship, possible consequences and available safeguards. A customer expecting a delivery update is in a different position from someone whose information has been assembled from several unrelated sources. Avoid an assessment that lists only benefits to the organisation. It should explain the effects on people and why the remaining interference is justified.
Make the assessment specific enough to influence the design
A useful assessment changes something when risks emerge. It may lead to fewer fields, a shorter retention period, restricted access or a less intrusive method. If the document could be pasted unchanged into any project, it is unlikely to show the reasoning that matters.
Our practical recommendation is to record alternatives rejected and why. For example, consider whether an aggregate report would answer the management question without a named profile. Describe the proposed controls precisely enough that a developer or colleague can implement them. Reassess if the data, audience, technology or consequences change; approval for one design is not permanent permission for every later version.
Record who approved the assessment and who owns the resulting controls. If approval is conditional on deleting an identifier or restricting access, confirm that change before the activity starts. A signed assessment is not evidence that its safeguards were actually implemented.
Recognised legitimate interest is a separate, narrower route
The recognised legitimate interest basis introduced by the Data (Use and Access) Act concerns specified purposes, including certain safeguarding, emergency, crime-prevention and public-task disclosures. It is not a new general exemption for ordinary commercial activity. The processing must fit the relevant specified purpose and satisfy its conditions.
This route removes the need for the ordinary balancing test where it properly applies, but it does not remove necessity, transparency, security or other applicable obligations. Nor does it give a requesting organisation an automatic entitlement to receive information. A request presented as urgent or official still needs verification of the requester, scope and relevant justification.
Check the rules that sit alongside the lawful basis
A lawful basis under Article 6 does not settle every issue. Special-category information and criminal-offence data need additional analysis. Electronic marketing and device-access technologies may be subject to PECR. You cannot use a legitimate interests assessment to replace consent where a separate rule requires it.
People also have applicable rights. Direct-marketing objections must be respected, and other objections require the appropriate assessment. Make sure the operational team can recognise and act on them. The privacy notice should explain the purpose and basis accurately rather than giving an undifferentiated list of every possible basis.
Do not switch basis merely to defeat someone’s choice
If consent was the basis presented to the individual, withdrawing it is not an invitation to relabel the same activity as legitimate interests. That would undermine the choice offered. A genuine new purpose or changed circumstance needs a considered review, appropriate information and a documented decision, not a quiet change in the database.
Before approving a project, ask whether a colleague could reconstruct the reasoning from the record: what is happening, why this basis fits, which other rules apply and what would trigger a review? That is a more useful standard than filling every box in a lengthy template. Difficult or high-impact processing deserves specialist advice before implementation, not after a challenge.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.