dpdp.storeevidence workbenchRESOURCE LIBRARY

Home / Tools / Retention Schedule Builder

04 / In your browser / VERSION 0.3.0

Retention Schedule Builder

Replace vague periods with events, ownership, deletion mechanics and evidence.

Launch locallyRead the working guide
LOCAL INSTRUMENT / SYNTHETIC EXAMPLE INCLUDED

Method

Builds four inspectable decision lanes separating organisation policy, holds and other-law branches, final Rule 8 source review, and deletion coverage.

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 choose a lawful period for an organisation. Organisation-defined periods remain policy choices.

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.

7 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 retention decision record with visible open choices, source status, optional Third Schedule template evidence, backup/processor coverage and deletion-verification tasks.

FICTIONAL PRACTICE SCENARIO

A fictional support process needs a policy record tied to case closure. Its organisation choice is known, but its legal-hold, Third Schedule, warning and Rule 8(3) log decisions are deliberately left open for review.

Before you begin

  • Bring one confirmed inventory row, the responsible owner and the system’s actual deletion capabilities.
  • Separate a policy choice from a period required by another applicable law or contract.
  • Use a synthetic purpose while learning the tool; do not paste case details or personal records.

Walk the evidence sequence

  1. Name the purpose-complete event

    Describe an event an operator or system can observe, such as verified case closure, rather than entering “when no longer needed”.

    Evidence to inspect
    The generated record ties the lifecycle decision to a concrete event and named owner.
    Human review
    Confirm that the event covers the real purpose and does not trigger while an active service or request still depends on the data.

  2. Separate policy from holds and other law

    Record the organisation-defined review choice, then select a hold status and identify authority, evidence, owner and release event for any separate branch.

    Evidence to inspect
    The output keeps the policy lane apart from the hold/other-law lane and marks unassessed decisions as open.
    Human review
    Have every asserted authority and release condition checked by the responsible legal or records reviewer.

  3. Review the final Rule 8 paths

    Check whether a Third Schedule class, India user threshold and purpose scope may match; separately document the Rule 8(2) warning and Rule 8(3) data/log treatment without calculating a date.

    Evidence to inspect
    A selected potential template carries its official class, purpose scope, three-year source text and at-least-48-hour warning text; “not assessed” remains open.
    Human review
    Confirm current commencement, classification, thresholds, exclusions, Seventh Schedule purpose and other-law retention with qualified reviewers.

  4. Define deletion coverage and verifiable completion

    Name the production mechanism, processor action, archive/backup/restore treatment, verification evidence, accountable owner and next review date, then export the current record.

    Evidence to inspect
    The local JSON and completeness table can be reviewed beside the inventory row, processor record and system procedure.
    Human review
    Test every relevant mechanism in the real systems; a written schedule or checked field is not proof of deletion.

Handoff check

  • Can the start event be detected consistently?
  • Are legal holds, warnings, backups and processors addressed separately?
  • Is deletion evidence assigned to an accountable owner and review date?
STOP / REVIEW BOUNDARY

The builder does not prescribe a universal period, determine a legal hold or Third Schedule match, calculate a warning/retention date, resolve an exception or verify deletion. It turns reviewed choices into an inspectable local record.

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.