Independent DPDP educationSWARN is in development · educational, not legal adviceSource status: 30 Aug 2026
DPDP/HQintegrations + engineeringSearch details
Menu

DPDP/HQ · LOCAL INDEX

Go directly to the work.

8 fast paths87 routes and records indexed · nothing is sent
↑↓ moveEnter openEsc closeBrowser-local interaction
DISC-04v1.0

CONTROL RECORD · REVIEWED 2026-08-30

Collection-surface review

Make collection-surface review 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 collection-surface review an inspectable system decision with a named owner, defined trigger and retrievable evidence.
Rationale
Make systems, data categories, purposes, owners and processors visible before deciding what should change.
Owner model
Processing inventory owner · System owner · Independent reviewer
Review frequency
Quarterly and on material system or purpose change
Architecture layer
Discovery and ownership
Version
1.0 · 2026-08-30

IMPLEMENTATION SEQUENCE

Move from scope to retrievable evidence.

  1. 01

    Scope the decision: define the decision, owner, trigger, evidence and review path before implementation.

  2. 02

    Record the approved design and its source-status verification boundary.

  3. 03

    Connect implementation events to evidence that a reviewer can retrieve without broad production access.

EVIDENCE ARTEFACTS

  • Test scope and sample
  • Timestamped result with evidence references
  • Finding and remediation record

CONTROL TEST

  1. Select a recent, in-scope sample for collection-surface review and record why it was chosen.
  2. Trace the sample from its trigger and owner through the implemented system to the retained evidence.
  3. Record exceptions, confidence and remediation without converting an unknown into a pass.

ANTI-PATTERNS

Completion labels can hide an evidence gap.

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
  1. Control pathwayDISC-04: Collection-surface review
    1. 01 · PrerequisitePurpose-owner assignment

      Review DISC-03 before testing this dependent record.

      Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023
    2. 02 · Implementation patternProcessor and sub-processor register

      Link approved providers to instructions, data flows, locations, assurance and exit work.

      Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025
    3. 03 · Validation / testSelect a recent, in-scope sample for collection-surface review 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
    4. 04 · Evidence artefactTest scope and sample

      Timestamped result with evidence references · Finding and remediation record

      Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023
    5. 05 · Failure modeTreating “collection-surface review” 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
    6. 06 · Research noteFrom obligation to evidence: the DPDP implementation stack

      Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision. Radar context: Software and data-flow inventories is Adopt.

      Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026
    7. 07 · Specialist propertyImplementation pathways

      Explore implementation planning when the inventory is ready to drive work. This route remains optional if the destination is unavailable.

      Contextual external property · no affiliation or availability implied
Open semantic relationship table (1pathway)
RecordPhaseRelationshipStatus / boundarySource pointers
DISC-04: Collection-surface review01 · PrerequisitePurpose-owner assignment

Review DISC-03 before testing this dependent record.

Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023dpdp-act-2023
DISC-04: Collection-surface review02 · Implementation patternProcessor and sub-processor register

Link approved providers to instructions, data flows, locations, assurance and exit work.

Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025
DISC-04: Collection-surface review03 · Validation / testSelect a recent, in-scope sample for collection-surface review 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-2023dpdp-act-2023
DISC-04: Collection-surface review04 · Evidence artefactTest scope and sample

Timestamped result with evidence references · Finding and remediation record

Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023dpdp-act-2023
DISC-04: Collection-surface review05 · Failure modeTreating “collection-surface review” 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-2023dpdp-act-2023
DISC-04: Collection-surface review06 · Research noteFrom obligation to evidence: the DPDP implementation stack

Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision. Radar context: Software and data-flow inventories is Adopt.

Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026act-commencement-2025 · pib-status-2026
DISC-04: Collection-surface review07 · Specialist propertyImplementation pathways

Explore implementation planning when the inventory is ready to drive work. This route remains optional if the destination is unavailable.

Contextual external property · no affiliation or availability impliedNone · 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 ledger

CONNECTED SYSTEM PATTERN

Processor and sub-processor register

Link approved providers to instructions, data flows, locations, assurance and exit work.

Open sequence

LOCAL WORKSPACE NOTE

Give this work a next owner.

This browser only

Nothing is sent anywhere. Avoid names, personal data or confidential incident details.

No local note loaded.

RELATED CONTROLS

DISC-03Purpose-owner assignmentDISC-05Processor discoveryDISC-01Processing inventory ownership

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.