The one-page scope document a founder will sign in a single meeting
The seven fields that make a scope document a decision, not a discussion. The three fields founders push back on and how to counter each pushback without losing the room. By the end of this lesson you have a template you can walk into Monday morning.
Legal basis
DPDP Act 2023 (No. 22 of 2023, assented 11 August 2023). DPDP Rules 2025 notified 13 November 2025 via Gazette Notifications G.S.R. 843(E), 844(E), 845(E) and 846(E). Sectoral overlays as in force on 5 October 2026: CERT-In Directions No. 20(3)/2022-CERT-In (28 April 2022); RBI Draft Data Governance Framework (15 July 2026, consultation closed 17 August 2026); SEBI CSCRF (20 August 2024, SEBI AI Vulnerability Detection Advisory 5 May 2026); IRDAI Information and Cyber Security Guidelines 2026 (6 April 2026); Telecom Cyber Security Rules 2024 (21 November 2024); Aadhaar Data Security Regulations 2016. Constitutional context: Puttaswamy v. Union of India (2017) 10 SCC 1.
Keep reading, free
Add your name and email. We send a one-click link that brings you straight back to this lesson, signed in. No password, no payment.
[L1-C1] are clickable. Click any to see the verbatim text of the Section, Rule or judgment we're relying on.
Learn how we verify content ›
L2-C1 L2-C2 - The shape of a DPDP engagement, before anyone opens a Section
- The one-page scope document a founder will sign in a single meeting
- The stakeholder RACI that actually works (and the trap in a six-column RACI)
- The 90-day Gantt with four checkpoint reviews baked in
- Three programme killers that sink DPDP in week 2 — and the two-minute CFO pitch
- Discovery interview questions that get engineering to actually tell you where data lives
- Reading a database schema the way an auditor reads it
- The four hiding places engineering always forgets to mention
- File-share and cloud-storage scanning without buying a six-figure DLP
- Building the draft data inventory that will survive Day 15
- Discovery sign-off and the Day-15 stop-or-go decision pack
- The eight columns of a DPDP RoPA, and why no ninth belongs
- Filling the RoPA from the Module 2 inventory, column by column
- The three red-flag cells an auditor spots in the first sixty seconds
- The twenty-minute RoPA walkthrough a DPB officer will ask you to run
- ABC Tyres worked example: four RoPA rows, filled column by column
- RoPA sign-off, the Day-30 Board update, and setting up Module 4
- The lawful basis decision tree, and why "legitimate interest" is not an answer
- The retention matrix, layered by sector, that defends every cell
- The Third Schedule three-year inactivity rule and the 48-hour pre-erasure notice
- Erasure requests and the "unless required by law" response
- Getting the retention schedule signed off by Day 30
- Drafting the Rule 3 standalone notice without turning it into a wall of text
- The Section 6 consent flow and the auditable consent record
- Cookies and tracking under DPDP, when the Act does not mention cookies
- Multilingual notice under the Eighth Schedule: 22 languages, Claude AI, not Bhashini
- The Rule 4 Consent Manager integration plan: live-frontier work
- Going live: the Day-45 checklist that keeps the notice from embarrassing you
- The DSAR intake form that collects what you need and nothing more
- Identity verification without over-collection — three tiers, one decision tree
- The 90-day clock, and why you must beat it, not touch it
- The four response templates — grant, carve-out, refuse, escalate
- Section 13 grievance and the Section 15 duty that handles bad-faith requests
- The vendor risk register — ten columns, one row per vendor, nothing more
- The ten DPA clauses you do not negotiate away
- The Rule 15 cross-border decision log — four columns and the empty negative list
- Three vendor conversations that go sideways — and the exact scripts
- Section 17 exemptions — when they genuinely apply and when founders only think they do
- The Day-75 cutoff — accept the risk, or kill-switch the vendor
- Classifying an incident as a personal data breach under Section 2(u)
- Rule 7 Stage 1 — the "without delay" intimation to Data Principals and the Board
- Rule 7 Stage 2 — the 72-hour detailed report to the Data Protection Board
- The CERT-In six-hour parallel clock — filing twice without duplicating effort
- The two-hour tabletop that turns a paper runbook into a tested one
- Scoping a DPIA before Legal is the one asking you to run one
- A risk-rating methodology that survives a Board meeting
- Algorithmic due diligence for AI systems, worked on a credit-scoring model
- The Rule 13 independent audit on a 12-month clock
- The DPO role that survives a change of CEO
- The 12-month DPO calendar that keeps a programme alive after Day 91
- Five KPIs that indicate programme health — and the gaming behaviour that corrupts each
- Board reporting cadence and the six-slide deck that gets fifteen minutes well-spent
- The budget renewal ask — how to argue for a 10 percent increase, not accept a 10 percent cut
- The DPO handover document — what a departing DPO owes a successor
- Running a steering committee that decides, not one that updates
- Converting an engineering "no, not this quarter" into a scheduled Yes
- Handling the marketing pixel removal fight without losing the CMO
- Briefing a Board on DPDP risk in ten minutes and six slides
- The three recurring cross-functional disputes and how to mediate each
- When to escalate to the CEO, when to absorb, and how to escalate once
- ABC Tyres — the client brief and your Day-0 engagement plan
- Walking the full ABC Tyres programme file end to end
- Submitting your capstone and preparing for the final exam