The operator clicks delete. The spreadsheet says complete.
The source application no longer shows the record. A downloaded export remains in a working folder. The processor has acknowledged a ticket without confirming an outcome. A backup still contains the earlier version.
A data deletion record needs room for those different states. Record what was authorized, what someone attempted, what evidence confirms, and what remains unresolved.
The method below starts after a disposition decision is authorized. It proposes a receipt for ordinary business-record disposal. It does not authorize deletion, determine a legal hold, or replace the process for an individual's rights request. Every action and record in the example is fictional.
Establish Which Process Started the Work
Write the initiating event before listing actions. A schedule review and an individual's erasure request enter through different decision paths.
For routine disposal, cite the approved schedule version, the satisfied trigger, and the disposition approval. Record any exceptions the approver considered. The operator needs a bounded decision to execute.
For an individual's request, route the case to the responsible privacy owner. The ICO's UK right-to-erasure guidance explains that the right applies in specified circumstances and has exceptions. A disposal worksheet does not decide those issues.
The cited ICO pages concern UK personal data. They carry guidance-review notices following the Data (Use and Access) Act. Checked 2026.10.28. Applicable jurisdiction, duties, and holds need qualified review.
Keep the initiating process visible in the receipt. If the team discovers a rights request during routine disposal, refer it to that process. Do not relabel it merely to fit an existing checklist.
Define the Authorized Scope Before Any Action
Consider a fictional business retiring a temporary workshop coordination list. Its records owner has already approved disposal after reviewing the purpose and applicable requirements.
The approval covers the workshop contact class, synthetic identifiers WS-041 through WS-046, and four named locations. It excludes payment evidence. No unresolved hold applies to the authorized workshop scope in this example.
Record that boundary exactly. A project folder can contain both classes. Permission to dispose of one class does not authorize deleting the whole folder.
Name the operator and the reviewer. The operator records actions. The reviewer checks whether the evidence supports the claimed result. Assign each role before execution, even when the same person holds both responsibilities.
If the operator finds a newly asserted hold or an ambiguous identifier, stop the affected action. Preserve the existing evidence and return the question to the authority owner. Do not treat an earlier approval as an answer to a new conflict.
Give the receipt its own identifier. The fictional example uses DR-017. Keep the approval reference separate so later readers can inspect the actual decision.
Map Copies and Their Evidence Limits
Use a location table before recording results. Follow the copy chain through the source application, exported file, processor service, and backup.
| Copy | Location and scope | Evidence available in the example | Evidence limit |
|---|---|---|---|
| C-01 | Source application, six workshop records | Authorized action log and post-action check | Says nothing about exports or processor copies |
| C-02 | Controlled folder, one six-row export | File-action record and folder review | Covers this path, not unknown downloads |
| C-03 | Processor service, workshop submission set | Ticket acknowledgment | Confirms receipt of the ticket, not completed deletion |
| C-04 | Identified backup generation | Backup inventory and approved handling record | Establishes remaining copy and restrictions, not erasure |
The six identifiers form one affected record set. Four copy locations do not turn it into twenty-four different people. Keep the record set and its representations separate.
Use the business system dependency map to identify known exports and downstream services. Mark a location unknown when nobody can verify it. Do not convert an incomplete search into a global claim.
Ask the service owner which product, workspace, plan, and configuration the evidence covers. This example assumes no particular vendor behavior. Each capability needs confirmation for the actual service.
Use a Receipt With Distinct Decision and Result Fields
Keep a case header above the copy table. The header describes the authority and affected scope. The copy rows describe actions and observations.
| Receipt field | Entry required by this proposed method |
|---|---|
| Receipt identifier | Stable reference for this disposition |
| Initiating process | Schedule-triggered disposal or separately managed request reference |
| Authority | Approval reference, approver, schedule version, and authorization date |
| Affected identifiers | Controlled record-set reference without copied sensitive contents |
| Scope and exclusions | Included classes, locations, and explicit boundaries |
| Action date and operator | Timestamp with time zone and accountable operator |
| Attempted action | Exact operation and location covered |
| Confirmation evidence | Restricted evidence reference and observation date |
| Result | Confirmed within scope, pending, blocked, or remaining copy with approved handling |
| Exceptions | Hold, uncertainty, failure, or excluded copy requiring another decision |
| Next review | Owner, date, and evidence needed to resolve the open item |
| Review decision | Reviewer, reviewed scope, limits, and accepted current status |
Use explicit status meanings. “Confirmed within scope” describes one identified copy and the evidence examined. It does not claim physical elimination from every storage device.
“Pending” means the result lacks required confirmation. “Blocked” means execution cannot proceed under the current authority or conditions. A remaining backup copy needs its own handling state.
Put evidence references in controlled storage. The receipt needs enough information to trace the work without reproducing the contents selected for disposal.
Record the Attempt and Observation Separately
For C-01, the fictional operator records an authorized deletion action at 10:00 UTC on 2026.10.28. The action log identifies the six synthetic records.
At 10:05 UTC, the operator checks the same identifiers through the approved application view. The view returns no matching active records. A reviewer examines both references.
The receipt says: source action recorded; active-record absence confirmed through the named view. That sentence matches the evidence boundary. It makes no claim about the service's underlying storage or other copies.
For C-02, the operator records removal of the identified export at 10:10 UTC. The reviewer checks the controlled path and the evidence specified by the approved procedure.
If the check only establishes absence from that path, write that limit. Do not invent a secure-erasure certificate or claim every workstation has been inspected.
An error message belongs in the attempted-action field even when a later attempt succeeds. Preserve the sequence with a reference to the correction. The final result should not erase the history needed to understand it.
Explain Offline Storage and Backup Handling Precisely
Taking information offline is different from deleting it. The ICO's storage-limitation guidance says offline personal data remains subject to the relevant obligations and needs a justified retention reason.
For valid UK erasure requests without an exemption, the ICO includes backup systems. Its guidance recognizes that backup data may remain until scheduled overwrite. It describes placing that data beyond use and explaining backup handling to the individual. This is context-dependent guidance, not permission to ignore a backup.
For this worksheet, record the backup generation, responsible owner, applicable handling decision, expected lifecycle event, and evidence still needed. Get qualified review of whether the arrangement is appropriate.
Record how the approved recovery procedure addresses the affected records if a restore occurs. A restriction needs an owner who can explain its implementation and limits.
Do not label a backup erased while the receipt says it remains. Do not promise instant deletion everywhere because one application screen is empty.
Work Through the Partial Result
DR-017 reaches its first review with two bounded confirmations, one vendor question, and one restricted backup copy.
| Copy | Recorded outcome | Open question or next evidence | Owner and next review |
|---|---|---|---|
| C-01 | Confirmed within the approved application view | No further evidence required for this scoped check | Application owner, accepted 2026.10.28 |
| C-02 | Confirmed at the identified export path | Unknown downloads remain outside this inspection's assurance | File owner, accepted 2026.10.28 |
| C-03 | Pending processor confirmation | Obtain outcome covering the named submission set and exceptions | Service owner, 2026.11.02 |
| C-04 | Remaining under approved restricted handling | Confirm scheduled lifecycle outcome and preserve recovery restrictions | Backup owner, 2026.11.09 |
These are fictional follow-up dates, not statutory deadlines or real service commitments. The backup's expected lifecycle date comes from the invented handling record.
The summary reads: disposition partially verified; processor outcome pending; identified backup remains under approved restrictions. The reviewer leaves the case open.
Do not report “four of four deleted.” Two rows have scoped confirmations. Two rows remain open. Even “half complete” can obscure their different evidence requirements.
Keep the six-record boundary unchanged. If another copy is discovered, add it with its discovery date and authority review. Reconcile the scope before making a new completion claim.
Resolve Exceptions Without Rewriting the Evidence
Suppose the processor replies with “request received.” C-03 remains pending. Acknowledgment confirms an intake event. It does not answer whether the named records were removed.
The service owner asks for a result tied to the workspace, affected identifiers, completion date, remaining copies, and exceptions. Keep the request specific enough for an inspectable answer.
If the reply identifies an obligation requiring continued retention, return that claim to the responsible reviewer. Record the source and affected subset. The operator does not decide its legal validity or bypass it.
Keep the vendor's original response and the review decision distinct. A reviewer may accept limited assurance while documenting uncertainty. The receipt should state what was accepted and why, without upgrading the underlying evidence.
A vendor departure introduces additional artifact and copy questions. Use the AI vendor exit plan for that broader change. A disposition receipt covers the authorized records and actions within its own boundary.
Close Only the Scope the Reviewer Can Support
Define closure criteria in the approved procedure before execution. Use the SOP documentation method to name the evidence, reviewer, and stop conditions.
For DR-017, leave overall closure pending until the reviewer resolves the processor outcome and backup follow-up. A date passing does not establish either result.
At review, compare each copy row with its required evidence. Confirm whether a known exception is resolved, still restricted, or waiting for another authority decision. Preserve any remaining limits in the closing statement.
Give the receipt itself an owner, access boundary, retention reason, and review rule. Keep only the identifiers and evidence references needed to support its purpose. Reproducing the disposed contents defeats that design.
Let the next reader distinguish approval, attempt, observation, and conclusion without reconstructing the whole case from email. A partial result belongs on the record. Completion needs evidence.
Sources
- ICO: Right to erasure. UK request scope, exceptions, and backup handling. Guidance under review. Checked 2026.10.28.
- ICO: Principle (e), Storage limitation. UK offline-storage and retention context. Guidance under review. Checked 2026.10.28.