EVIDENCE ARTEFACTS
- Versioned decision record
- Named ownership and approval
- Implementation or test evidence
RIGHTS-04v1.0
CONTROL RECORD · REVIEWED 2026-08-30
Erasure workflow
Make erasure workflow an inspectable system decision with a named owner, defined trigger and retrievable evidence.
Engineering control
Catalogue status
not legal status
RECORD ANATOMY
What this control needs to be reviewable.
- Objective
- Make erasure workflow an inspectable system decision with a named owner, defined trigger and retrievable evidence.
- Rationale
- Turn intake, identity risk, system search, action, communication and escalation into one traceable workflow.
- Owner model
- Request case owner · System task owner · Identity-risk reviewer
- Review frequency
- Per request plus quarterly workflow sampling
- Architecture layer
- Rights and grievance operations
- Version
- 1.0 · 2026-08-30
IMPLEMENTATION SEQUENCE
Move from scope to retrievable evidence.
- 01
Scope the decision: define the decision, owner, trigger, evidence and review path before implementation.
- 02
Record the approved design and its source-status verification boundary.
- 03
Connect implementation events to evidence that a reviewer can retrieve without broad production access.
CONTROL TEST
- Select a recent, in-scope sample for erasure workflow and record why it was chosen.
- Trace the sample from its trigger and owner through the implemented system to the retained evidence.
- Record exceptions, confidence and remediation without converting an unknown into a pass.
ANTI-PATTERNS
Completion labels can hide an evidence gap.
- Treating “erasure workflow” as a policy sentence without an operating owner
- Marking the control complete from self-attestation alone
- Hiding missing, stale or inaccessible evidence behind a pass label
ARCHITECTURE → EVIDENCE DECISION JOURNEY
Follow the dependency, then inspect the proof.
Each connection uses existing catalogue records. Source IDs remain verification pointers—not provision mappings.
Add to a review route- Control pathwayRIGHTS-04: Erasure workflow
- 01 · PrerequisiteCorrection workflow
Review RIGHTS-03 before testing this dependent record.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 02 · Implementation patternData Principal request orchestration
Coordinate identity risk, search, action, response and escalation without building a new data silo.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 - 03 · Validation / testSelect a recent, in-scope sample for erasure workflow and record why it was chosen.
Trace the sample from its trigger and owner through the implemented system to the retained evidence. Record exceptions, confidence and remediation without converting an unknown into a pass.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 04 · Evidence artefactVersioned decision record
Named ownership and approval · Implementation or test evidence
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 05 · Failure modeTreating “erasure workflow” as a policy sentence without an operating owner
Marking the control complete from self-attestation alone · Hiding missing, stale or inaccessible evidence behind a pass label
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 06 · Research noteWhat an evidence-producing rights workflow needs
A case workflow should expose missing system acknowledgements and unresolved risk instead of equating a sent response with completed work. Radar context: Rights-request orchestration is Trial.
Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026 - 07 · Specialist propertyEvidence review
Examine how evidence quality and confidence can be reviewed without certification claims. This route remains optional if the destination is unavailable.
Contextual external property · no affiliation or availability implied
- 01 · PrerequisiteCorrection workflow
Open semantic relationship table (1pathway)
| Record | Phase | Relationship | Status / boundary | Source pointers |
|---|---|---|---|---|
| RIGHTS-04: Erasure workflow | 01 · Prerequisite | Correction workflow Review RIGHTS-03 before testing this dependent record. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| RIGHTS-04: Erasure workflow | 02 · Implementation pattern | Data Principal request orchestration Coordinate identity risk, search, action, response and escalation without building a new data silo. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 | dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025 |
| RIGHTS-04: Erasure workflow | 03 · Validation / test | Select a recent, in-scope sample for erasure workflow and record why it was chosen. Trace the sample from its trigger and owner through the implemented system to the retained evidence. Record exceptions, confidence and remediation without converting an unknown into a pass. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| RIGHTS-04: Erasure workflow | 04 · Evidence artefact | Versioned decision record Named ownership and approval · Implementation or test evidence | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| RIGHTS-04: Erasure workflow | 05 · Failure mode | Treating “erasure workflow” as a policy sentence without an operating owner Marking the control complete from self-attestation alone · Hiding missing, stale or inaccessible evidence behind a pass label | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| RIGHTS-04: Erasure workflow | 06 · Research note | What an evidence-producing rights workflow needs A case workflow should expose missing system acknowledgements and unresolved risk instead of equating a sent response with completed work. Radar context: Rights-request orchestration is Trial. | Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026 | act-commencement-2025 · pib-status-2026 |
| RIGHTS-04: Erasure workflow | 07 · Specialist property | Evidence review Examine how evidence quality and confidence can be reviewed without certification claims. This route remains optional if the destination is unavailable. | Contextual external property · no affiliation or availability implied | None · contextual external route |
VERIFY BEFORE MAPPING
GENERIC VERIFICATION POINTER · NOT A PROVISION MAPPING
dpdp-act-2023
Provision-specific applicability must be verified against the primary-text ledger.
Boundary: Operational control pattern; not a standalone legal conclusion.
Open the source ledgerCONNECTED SYSTEM PATTERN
Data Principal request orchestration
Coordinate identity risk, search, action, response and escalation without building a new data silo.
LOCAL WORKSPACE NOTE
Give this work a next owner.
Nothing is sent anywhere. Avoid names, personal data or confidential incident details.
CHANGE LOG
Version 1.3 — Architecture-to-evidence journey and non-personal review-route relationship added; verification-pointer boundary retained.
Version 1.2 — Official-source status rechecked; command-centre indexing and the non-mapping boundary retained.
Version 1.1 — Engineering fields, source verification pointers and acceptance evidence reviewed.
Version 1.0 — Stable catalogue ID, objective, evidence model, test sequence and verification boundary established.