dpdp.storeevidence workbenchRESOURCE LIBRARY

Home / Tools / Rights Request Kit Generator

05 / In your browser / VERSION 0.3.0

Rights Request Kit Generator

Give operators a consistent sequence for a request without pretending one form fits every case.

Launch locallyRead the working guide
LOCAL INSTRUMENT / SYNTHETIC EXAMPLE INCLUDED

Method

Builds four operational lanes and an evidence-gated editable checklist for access, correction/completion/updating, erasure, grievance and nomination-related work.

Use it safely

Begin with the synthetic example in the toolbench, then minimise any real-world input. Inspect each finding, its source/status note and the facts behind it before exporting a result.

What it cannot determine

It cannot verify identity, discover records, decide exceptions, calculate a deadline, change a system or send a response.

Processing boundary. This preview processes current input in browser memory. No input is submitted or stored by dpdp.store. Results are evidence-building aids, not legal approval, certification or an official schema.

8 minute working guide / SYNTHETIC WALKTHROUGH

From input to a reviewable handoff.

GUIDE 0.5
Reviewed
2026-08-26
Legal status
editorial analysis
Changelog
0.5.0 — first public static working guide.

What this produces: A four-lane local case plan with a 15-field completeness record and eight editable tasks whose closed states require evidence notes or not-applicable rationales.

FICTIONAL PRACTICE SCENARIO

A fictional operator receives a correction request under a synthetic reference and needs a consistent task sequence without copying the requester’s personal data into another system.

Before you begin

  • Choose one of the five source-specific workflows and create a non-identifying local case reference before opening the tool.
  • Select an identity-risk approach appropriate to the channel and harm risk; keep the underlying identity evidence in the controlled case system because the generator verifies nothing.
  • Identify a responsible owner, received-time record, search scope, processor handoff, response route and escalation reviewers.

Walk the evidence sequence

  1. Create a minimised case frame

    Enter the workflow, synthetic reference, owner, received-time record, clock basis, channel and identity-risk choice. Keep the narrative and personal records in the controlled case system, not this preview.

    Evidence to inspect
    The intake lane preserves open identity decisions and minimised evidence references without submitting or retaining the request.
    Human review
    Check that the reference can be reconciled safely by authorised staff and does not expose identity in the export name.

  2. Plan a complete system search

    Use the inventory and processor register to enter the primary-system, derived-store, archive and processor/recipient scope, then review the workflow-specific search tasks.

    Evidence to inspect
    The search lane and task checklist keep system discovery and external handoffs visible instead of implying that one database is complete.
    Human review
    Confirm scope, exceptions and access controls before retrieving or disclosing any record.

  3. Separate decision from execution

    Record the reviewed decision, fact-specific exceptions, authorised system actions, verification and controlled evidence references. Keep unresolved legal or security judgments in escalation.

    Evidence to inspect
    The decision lane separates planning from execution and keeps every completion claim tied to an evidence note.
    Human review
    Require appropriate legal, security or service-owner review where identity, third-party rights, retention or fraud risk is uncertain.

  4. Close with evidence and follow-up

    Reconcile processor acknowledgements, system changes, the approved response and escalation record. Mark a task Complete or Not applicable only with an evidence note or rationale, then export the current record deliberately.

    Evidence to inspect
    The JSON reflects the current task states and evidence notes; the tool still sends nothing and cannot prove the linked evidence exists.
    Human review
    Do not treat a checked box as proof; link each completed task to controlled evidence.

Handoff check

  • Was identity risk handled proportionately without collecting unnecessary data?
  • Did the search include processors, archives and derived systems where relevant?
  • Can each completed action be traced to controlled evidence and an authorised decision?
STOP / REVIEW BOUNDARY

The kit does not verify identity, discover systems or processors, calculate a deadline, decide an exception, modify a system, validate a nomination, communicate with a requester or approach the Board.

Security and parsing

  • Inputs have byte, row or component limits appropriate to the parser.
  • Imported content is treated as text or data and is never executed.
  • Spreadsheet exports neutralise formula-leading cells.
  • Use the per-tool reset or “Clear current toolbench state” to remove current in-tab input and results. Downloaded files remain under your control.

Version record

0.3.0 · 26 August 2026: deterministic public static implementation, synthetic fixture and bounded local parser. Guide record 0.5 · 26 August 2026.