Review New Contact Purposes Before Reusing Consent
Compare original and proposed data uses, assess necessity and expectations, and preserve old scope while a new purpose receives qualified review.
10/23/20263 min read
A contact supplied an email address to receive a technical report. Months later, another team wants to use the same address for an unrelated training campaign. The address has not changed, but the purpose has. An old permission field cannot answer the new question unless its original scope and the applicable rules genuinely cover the proposed use.
Create a purpose-change review before moving records into the new workflow. Preserve the original decision and assess the proposed action separately. Editing the old purpose label to match today's campaign would erase the evidence needed to understand the change.
Describe the old and new activities side by side
Record the original collection context, notice, sender, channel, purpose, and basis relied on. Then describe the new activity with equal precision. Include new recipients, providers, profiling, enrichment, or sharing, not just the name of the campaign.
The ICO's lawful-basis guidance connects changed purposes with the purpose-limitation assessment. UK rules and guidance can change, and other jurisdictions require separate analysis. Have a qualified reviewer determine whether the proposed reuse is supported, requires additional steps, or should not proceed.
Do not assume that fresh consent is always required, always sufficient, or obtainable through any channel you choose. A message seeking permission can itself require a lawful and permitted route. The review should establish the right next step rather than presupposing one.
A fictional purpose-change worksheet
Synthetic company Lantern Learning collected details to send a requested equipment-maintenance report. A different internal team proposes promoting leadership courses. Its worksheet contains these entries.
Original purpose: deliver the specifically requested maintenance report.
Original evidence: request record and the notice version shown at collection.
New purpose: promote paid leadership courses by email.
Added processing: audience segmentation by inferred management responsibility.
Recipient expectation question: what evidence suggests this new use would be expected?
Necessity question: are existing contacts needed, or can the team use a separately approved opt-in route?
Decision: hold the reuse and inferred segmentation pending privacy review; retain the original scope unchanged.
The outcome is fictional and deliberately unresolved. The worksheet's job is to expose the differences, not manufacture a legal justification for a campaign already scheduled.
Review the data as well as the message
A new purpose may need fewer fields than the old one, or different information that the organization has no reason to collect. Remove unnecessary fields from the proposed design. Do not enrich personal channels merely because the new marketing team prefers them.
Examine whether historical details remain accurate for the new use. A role recorded during an old enquiry may be stale. Accuracy review does not itself create permission, and permission review does not establish accuracy. Keep these decisions separate in the release record.
Check existing objections, withdrawals, and restrictions before considering the new purpose. Do not treat a change in campaign category as a way around a broad stop instruction. If the instruction's scope is uncertain, pause and ask the responsible owner to interpret it from the actual wording.
Record a decision that cannot be stretched
An approval should name the processing activity, data categories, audience, channel, safeguards, notice requirements, and limits. A rejection or hold should explain the missing evidence and owner. Avoid a general lawful-basis-approved flag detached from the activity it assessed.
Keep the old and new assessments linked but distinct. If the new use proceeds, make sure systems enforce its boundaries and retention decisions. A reviewer may approve a single requested update without approving a recurring campaign or onward sharing.
Test the workflow with synthetic records from different original purposes. Confirm that records outside the reviewed scope remain excluded even when their contact details are technically valid. Check that a future import cannot overwrite purpose restrictions with a generic subscribed value.
Close the review when the authorized decision is implemented and verified, not merely when a form is signed. A useful purpose-change record explains what changed, why the new action is justified or blocked, and which original boundaries remain in force.
If you are also choosing research access, ask about Leads Automation’s independent Sales Navigator offer at US$15/month on WhatsApp. Confirm the available plan, eligibility and terms before ordering; this is not LinkedIn’s official price or an assurance that any particular integration is included.