dpdp.storeevidence workbenchRESOURCE LIBRARY

Home / Workflows / Notice evidence chain

WORKFLOW 01 / 4 REVIEW STAGES

Website notice → lint → versioned evidence

Move from one collection surface and one controlled draft to a traceable local review record without mistaking structural cues for approval.

Start with the scenarioOpen the toolbench
LOCAL TOOLS / HUMAN CONFIRMATION REQUIRED

Outcome to assemble

A reviewed notice version, an exported linter record and a decision log that explains which cues were accepted, rejected or escalated.

Reviewed
2026-08-26
Legal status
editorial analysis
Source/method records
act-2023rules-2025rules-2025-corrigendumdpdp-store-method-0.2
Changelog
0.5.0 — first public static working guide.
FICTIONAL PRACTICE SCENARIO

A fictional account-registration page collects name, work email and organisation for access setup. The working draft is deliberately incomplete so the team can practise reviewing itemisation, purpose, withdrawal, grievance and Board-route cues.

STAGED HANDOFF

Follow the evidence, not a score.

WORKFLOW 0.5
  1. 01

    Freeze the collection-surface facts

    Record the exact surface, data categories, purposes, actor, contact routes and notice version in the controlled product record.

    Handoff
    A fact sheet the notice author can use without copying live user records.
    Stop and review
    Stop if the product team cannot confirm what is collected or why; a lint cannot repair missing facts.
  2. 02

    Run a synthetic baseline, then the draft

    Use the built-in synthetic example to understand the finding states, then paste the minimised draft and run the local linter.

    Handoff
    A bounded list of source-linked structural cues for the author and reviewer.
    Stop and review
    Do not export after editing until the stale result has been rerun.
  3. 03

    Resolve cues in the controlled notice

    Edit for factual accuracy and clarity, not keyword satisfaction. Record why each cue changed or why a reviewer rejected it.

    Handoff
    A candidate notice and an explicit decision trail.
    Stop and review
    Escalate legal meaning, interface presentation, consent design and current-status questions to qualified reviewers.
  4. 04

    Rerun, export and bind the versions

    Generate a fresh result, export it locally and bind the result version to the reviewed notice and collection-surface record.

    Handoff
    A three-part pack: notice, structural-review export and decision log.
    Stop and review
    The pack is evidence of a review process, not certification that the notice or surrounding journey complies.

Before the pack moves on

  • The notice and finding export name the same controlled version.
  • The collection-surface fact sheet matches actual product behaviour.
  • Every unresolved cue has an owner and review path.
  • Downloaded evidence is stored and retained under organisation controls.
WORKFLOW LIMIT

This workflow cannot observe the rendered prominence, surrounding interface, user understanding, product behaviour or validity of consent.