Decide whether consent fits the relationship
Consent is appropriate only where the person has a genuine choice. Do not select it simply because asking permission feels cautious. If the business must process information to fulfil a legal obligation, or cannot realistically stop the activity when asked, a different lawful basis may be the correct starting point.
Power imbalances also matter. An employee may not feel free to refuse a request from their employer, even where a form offers a checkbox. Examine the consequences of refusal and whether an alternative is genuinely available. Consent should not disguise a compulsory business process, nor should unnecessary processing be made a condition of receiving a service without careful justification.
Make the choice understandable at the point it is made
The person should understand who is asking, the relevant purposes, what they are agreeing to and that consent can be withdrawn. Avoid combining several unrelated uses into a vague acceptance of a privacy policy. Reading an explanation is not the same action as consenting to every activity described in it.
Our recommended design review begins with the smallest meaningful choice. Could someone accept the optional feature they want without agreeing to something unrelated? Can the explanation be understood without legal vocabulary? Keep supporting detail available, but do not bury the decisive information several links away. Test the wording with someone who did not write it.
Keep evidence that survives a website redesign
The ICO expects records that demonstrate when and how consent was obtained and what the person was told. A timestamp without the corresponding wording can leave a gap. Equally, keeping today’s form does not establish which version was displayed when an older record was created.
A workable evidence model records the person or relevant identifier, purpose, action, time, collection route and wording version. Store a controlled copy of the notice or script associated with that version. For oral consent, a contemporaneous record can be appropriate; recording every conversation is not automatically necessary. Choose evidence proportionate to the processing rather than collecting excessive additional information merely to prove compliance.
Treat integrations as part of the consent system
Consent often passes through a form builder, customer database, mailing platform and reporting system. Establish which is authoritative and how changes propagate. If one tool says “withdrawn” while another still treats the record as active, the person’s choice may not be honoured in practice.
Use invented test records to follow the whole journey. Check imports, manual edits, duplicate records and delayed synchronisation. An imported contact should not become opted in simply because the destination system uses that as a default. Give staff a clear rule for missing evidence: investigate or hold the optional activity, rather than treating an empty field as permission.
Make withdrawal as practical as giving consent
People must be able to withdraw consent easily and at any time. Withdrawal does not retrospectively make earlier lawful processing unlawful, but the consent-based activity must stop. Explain the route before consent is obtained and make sure it works for people who cannot use a particular account or interface.
A useful operational test is to withdraw through the ordinary channel and observe each downstream system. Check whether queued activity stops and whether staff can recognise a plain-language request received by email or telephone. Do not insist on a special phrase. Proportionate identity checks may be necessary, but should not turn an ordinary withdrawal into an obstacle course.
Separate withdrawal, deletion and suppression
Withdrawal concerns the activity supported by that consent. It does not necessarily require immediate deletion of every record the business holds for other valid purposes. For example, transaction records may have a separate retention justification. Explain the distinction rather than telling someone either that everything must disappear or that nothing can be removed.
A minimal suppression record may be needed to avoid contacting someone again. Keep it restricted to that purpose and avoid using it as a hidden marketing list. Our practical recommendation is to document which systems retain what after withdrawal, why they retain it and how long that justification lasts. This prevents routine imports from accidentally reactivating old preferences.
Review changing purposes and aging evidence
Consent is not an unlimited licence for future ideas. A new purpose, new organisation relying on it or material change in the activity may require a fresh assessment and new consent. The relevant question is whether the existing choice still covers what is now proposed, not simply how recently the person ticked a box.
Build review triggers into change management. When the marketing team adds a partner, product team changes a feature or supplier introduces a new use, someone should check the existing permission. There is no universal expiry period that makes all consent valid until a particular anniversary. Retain evidence while it is needed, review it proportionately and stop relying on records that cannot support the intended activity.
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.