Treat the request as a distribution task with a named owner. Find the affected uses, act on the ones you control and distinguish confirmed changes from requests still awaiting a response. Removing a page is one action; it is not evidence that every copy has disappeared.
Establish the request without creating an obstacle
Record when the request arrived, what the person wants stopped and which story or assets they mean. Use the existing relationship and information you already hold to resolve identity. If someone acts for the participant, check their authority. Keep any necessary clarification proportionate; do not turn a straightforward withdrawal into another approval exercise.
A request about personal participation may differ from a company's request about its logo or contractual publication permission. Record those issues separately so the appropriate owner can handle each one. Do not assume the account manager can settle every data, contract and rights question.
For UK processing that relied on consent, the ICO's consent-management guidance says withdrawal requires that processing to stop as soon as possible. It does not undo the lawfulness of earlier processing. You cannot simply switch lawful basis to carry on the same withdrawn processing. A different, fairly established retention purpose needs its own assessment. The guidance is marked as under review; involve the responsible privacy owner in the actual case.
That is a conditional consent rule, not a claim that every testimonial must use consent as its data-processing basis. A broader removal, objection or rights request may need a separate assessment. Give the responsible team the actual request and original records.
A completed request record
Fictional exercise: an operations manager withdraws consent for their participation in a supplier's marketing story. All people, files, times and actions below are invented teaching material.
The request arrives on 19 October 2026 at 09:05 UTC from the participant's established project email: “Please stop using my name, photograph and interview for marketing.” The project owner, Mira, matches it to story ST06 and the existing participant record. No representative is involved.
The privacy owner, Rowan, checks that record C03 was the consent relied on for the specified personal-data marketing use. The team does not reinterpret an old “approved” flag as permission to continue. A separate company-logo agreement is recorded but does not answer the participant's request.
Mira owns the distribution register. Rowan owns the assessment of source files, necessary records and any further rights questions. The team acknowledges the request and begins stopping the affected uses it controls while checking the distribution list.
Trace the released copies
Start with the publication record, then check the actual destinations. Include scheduled material and reusable templates; they can put a withdrawn quote back into circulation after the visible page is removed.
| Copy or use | Owner and action in this fictional incident | Evidence and current status |
|---|---|---|
| Website story ST06-v3 and quote card | Web owner removes the story and card at 09:18 UTC | Listed public locations checked; both no longer display the participant |
| Active paid creative AD06-v2 | Media owner pauses the affected campaign at 09:13 UTC | Paused status inspected; this does not establish that every earlier impression can be recalled |
| Two queued company posts | Social owner cancels both at 09:10 UTC | Queue checked; neither remains scheduled |
| Downloadable PDF linked from the story | Web owner disables the public file link at 09:20 UTC | Link no longer serves the file in the checked location; prior downloads remain unverified |
| Deck sent to three known sales recipients | Mira asks all three to stop using the affected version at 09:25 UTC | One confirms replacement; two confirmations pending |
| Source interview and working exports | Rowan removes them from routine marketing access pending the handling decision | Access restriction confirmed; retention or deletion decision remains open |
The register deliberately contains different states: completed, requested and unresolved. Avoid a single green “removed” status across all six rows.
Withdrawal response: keep each copy’s status visible
Fictional ST06 incident
Stop marketing use
Participant request
Mira coordinates the distribution register
Website story and quote card
Owner: web owner
Removed; listed public locations checked
Campaign and queued posts
Owners: media owner / social owner
Campaign paused; two posts cancelled
Public PDF link
Owner: web owner
Disabled in the checked location
Earlier downloads unverified
Deck: three known recipients
Owner: Mira
One replacement confirmed
Two confirmations pending
Source interview and exports
Owner: Rowan
Marketing access restricted
Handling decision open
Add an owner and evidence reference to each subsequent update. A sent email proves that a request was sent. A recipient's confirmation supports a narrower conclusion about that recipient. Neither establishes the state of unknown downloads or copies forwarded beyond the known list.
When only one use is withdrawn after an internal edit
A request can affect one use without being a request to withdraw every version. Record the participant’s actual instruction, then give each affected file and destination a decision. A folder marked “approved” is too broad to guide the next upload.
Separate fictional exercise: SC09 is an invented customer-video project, not a continuation of the ST06 incident above. Its participant previously approved website story v03 and paid-ad cut v04. After v04 circulates to the editor and media operator, the participant says: “Please keep the agreed website story, but do not use my interview in paid advertising.” No paid placement has launched in this exercise.
The project owner records that wording against request W02. The responsible privacy and rights owners confirm the scope and handling for this exercise; the website-use record R03 remains separately confirmed. This is a production decision record, not a legal conclusion that another use may always continue. If the request or authority is unclear in a real case, resolve that uncertainty before treating the affected use as available.
Here is the team’s completed disposition sheet. All files, records, checks and responses below are fictional.
| Asset and exact use | Known location or recipient | Required action and owner | Evidence and disposition |
|---|---|---|---|
| SC09_web_v03.mp4 — agreed website story | Website player W03; web owner | Keep only this unchanged website use under the separately confirmed R03 record; project owner records the boundary. | W03 matches v03. Available for this website use only; this row does not permit ads or new edits. |
| SC09_paid_v04.mp4 — withdrawn paid use | Internal review link sent to editor and media operator | Project owner blocks paid use in the release record; editor removes v04 from the reusable delivery folder; media operator checks the listed ad destination. | Both recipients acknowledge the restriction. Folder check is complete; no live or queued placement appears in the checked destination. Paid use blocked; no claim about unlisted destinations. |
| SC09_ad-review-deck_v01 — embeds the v04 clip | One known internal sales recipient | Project owner asks for the embedded clip and old review link to be removed, and asks whether the deck was forwarded. | Request sent; no reply yet. Recipient handling remains open. The deck is held from further use or forwarding; removal is unconfirmed. |
| SC09_web_v05.mp4 — proposed shorter website edit | Sales request only; no export exists | Editor leaves this optional edit unstarted. If commissioned, link the actual new cut to its own review and release decision. | Not created or approved. The v03 decision does not automatically cover v05; unchanged v03 does not need replacing merely to create a new number. |
The immediate instruction is specific: no paid upload of v04, no further use of the review deck, and no assumption that a renamed export is cleared. The website row has its own confirmed scope. The open deck response prevents the team from reporting that every internally distributed copy has been dealt with.
Update the working handoff as well as the register. Replace the old general “approved” note with a reference to W02 and the exact use restrictions. Restrict the affected files from routine reuse while the responsible owner decides their handling; do not turn this worksheet into an instruction to delete all originals or retain them indefinitely.
Reuse the row, not an “approved” flag
For each actual asset, record its identifier and version; the exact use and destination; known recipients; the required action and owner; evidence of that action; and the remaining release decision. Keep a request sent, an acknowledgement received and a destination checked as separate facts.
If a recipient reports forwarding a copy, add the newly known destination and owner. If they have not replied, keep that row open. Do not describe untraced copies as removed, or reopen an unaffected use solely because it shares source footage.
If you commission an editor to handle the change, send the completed sheet and ask for a defined correction handoff: changed files, withdrawn reuse paths, checked destinations and outstanding recipient actions. Agree any additional edit separately. Accept the handoff against those items, rather than against a new file called “final”.
The next section returns to the ST06 withdrawal example above.
Keep the response specific
At 10:00 UTC, the fictional team can send an update such as:
We have removed the identified website story and quote card, disabled the linked PDF and stopped the listed campaign and queued posts. We have asked the three known deck recipients to stop using that version; one has confirmed and two have not yet replied. We cannot confirm the state of earlier downloaded copies. Rowan is reviewing the handling of source files and necessary records. Mira will send the next status update at the time agreed with you.
For a real incident, replace every completed-action statement with what your evidence supports. If only a pause request has been sent to an agency, say that. Do not report a campaign as paused until someone has checked its status.
Agree the next communication with the participant, without presenting your project's update time as a universal legal deadline. A useful update explains what changed, what remains uncertain and who owns the remaining work.
Handle records and retention separately
Stopping a public marketing use and deciding what happens to underlying files are different tasks. Route the latter to the privacy owner with the original purpose, basis, notices, agreements and actual request. Do not create a new rationale after withdrawal simply to keep using the testimonial.
A minimal record of the request and actions can help prevent accidental reuse. Its contents, access and retention need their own justification; the register is not a reason to keep every recording or identity document indefinitely.
Also check the systems that feed future work. A removed page may leave a quote marked “available” in the sales library. Change that operational status and tell the relevant people which version is affected. Keep the detail needed to prevent reuse without copying sensitive material into every team chat.
Close the production task honestly
The fictional incident remains open until the two known recipients respond and Rowan resolves the remaining file-handling questions. Unknown historical downloads are recorded as unknown. The team can close particular owned placements while leaving those limitations visible.
If you commission help, send the supplier the affected asset list and ask for a defined scope: stop or replace owned placements, update approved source folders, contact known distributors and provide action evidence. Establish which systems the supplier can actually control. Do not buy a promise of “complete removal everywhere” without a verifiable scope.
For your next project, make the released-copy list part of the approval map. The practical result is a response another person can continue from: what was requested, what stopped, what was checked and what still needs a decision.