Self-assessment
Score yourself
Answer each question honestly. Yes = 2, Partly = 1, No = 0. Keep a running total.
Your score
0/ 24
0 of 12 answered
Not scored yet
The yardstick
0 / 601 Have you fixed, in writing, which frameworks the assessment measures you against: DPDP only, or allied frameworks too?
02 Do you have an applicability matrix: entities and business lines down one side, the Act's obligations across the top, each cell marked and justified?
03 If you were notified as a Significant Data Fiduciary, would you know which extra duties land on which entities?
The evidence
0 / 604 Will the assessment rate what branches and teams actually do, not what policy documents say?
05 Does every rating carry evidence you can produce: a document, a system screenshot, an interview record?
06 Has a named owner agreed to sign off each finding?
The ratings
0 / 607 Does every applicable provision get one of four ratings: Compliant, Partially Compliant, Non-Compliant, Not Applicable?
08 Is each gap risk-scored on legal exposure, likelihood and impact on people, so the fix list sequences itself?
09 Could you pick any rated provision today and show the evidence behind the rating?
The follow-through
0 / 610 Does the roadmap give every finding an owner and a date?
11 Are quick wins, the fixes you can finish before duties commence, separated from programme work?
12 Is the fix work funded and planned, or does the assessment end in a PDF?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | Either the assessment is not done, or it will not survive an auditor. Start with the applicability matrix; everything hangs on it. |
| 9 to 16 | Halfway | The section with your lowest marks is the weak link. Follow-through scores are the ones that decide whether anything gets fixed. |
| 17 to 21 | Strong base | Prove it. Run the evidence test at the end of this page and close whatever it exposes. |
| 22 to 24 | Leading | Keep the matrix and register alive as the business changes and new notifications arrive. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What a gap assessment is
A gap assessment is a structured, clause-by-clause comparison of current practice against the Act and Rules. Every applicable provision gets a rating: Compliant, Partially Compliant, Non-Compliant or Not Applicable. Each rating carries the evidence behind it, a risk score, and a place in a prioritised fix list.
It is fact-finding, not fixing. The assessment ends at findings, ratings and a roadmap. Implementing the fixes is the next phase, planned and funded separately. It is also read-only: walkthroughs, documents and existing audit reports. Not penetration testing.
The framework: four moves
Move 1: Fix the yardstick. The DPDP Act and Rules are the core. Decide up front whether to extend to allied frameworks your enterprise also answers to: the IT Act, the national incident-reporting directions, sectoral rules. Write the decision down. Widening the yardstick mid-way is how assessments never finish.
Move 2: Build the applicability matrix. Entities and business lines against obligations, each cell justified. Get applicability wrong and everything after is built in the wrong place. Revisit it when the business changes and when new notifications arrive.
Move 3: Rate practice, with evidence. Walk business units through what people really do with data. Rate every applicable provision, and attach the evidence to each rating: the document, the screenshot, the interview record. Score each gap on legal exposure, likelihood and impact on people, Critical to Low.
Move 4: Turn findings into a roadmap. Quick wins first, then programme work. Every finding gets a named owner, a date and a sign-off. A register nobody owns changes nothing. For a large estate, expect one report per system, a consolidated heat map, and a single prioritised roadmap on top.
Template: the gap register
One row per applicable provision. Copy this and fill it in.
| Provision | Applies to | Rating | Evidence | Risk | Fix | Owner | Due | Status |
|---|---|---|---|---|---|---|---|---|
| Example: notice before consent | Website, app | Partially Compliant | Notice v3 screenshot; app flow omits withdrawal route | High | Rewrite app notice; add withdrawal route | Head of digital | Open | |
The downloadable file adds the applicability matrix and a column guide.
What good looks like at the end
You should have: the applicability matrix, an evidence-backed gap register, per-system findings where your estate is large, a heat map, and a prioritised roadmap with owners and dates.
The live test: pick three provisions at random from the register. For each, ask the owner to show the evidence behind the rating. If the evidence cannot be produced, the rating is an opinion, not a finding.
Where enterprises go wrong
- Assessing policies instead of practice. The policy says one thing; the branch does another.
- A register with no owners or dates. Without both, nothing gets fixed.
- An assessment that ends in a PDF nobody funds. The most expensive gap assessment is the one nobody implements.
- Widening the yardstick mid-way.
The decisions to make
- The yardstick: DPDP only, or allied frameworks too.
- Fresh assessment or validation of an existing one. Validation is cheaper, but only if the earlier work was honest and recent.
- Breadth: organisation-wide, or named systems first.
- Whether Significant Data Fiduciary readiness is an explicit output.
- In-house, or an external assessment-only engagement for independence.
Next step
Make data protection someone's job, so every finding has an owner. If you need help with any of this, write to us and we will help.