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 audiences
0 / 601 Is there an audience map: every role that touches personal data, internal and external?
02 Does each audience have its own curriculum, in its own terms?
03 Do partners' and vendors' staff who handle your data get included? Their people can cause your breach.
The content
0 / 604 Do customer-facing staff learn request intake, verification, and what never to send on personal channels?
05 Do developers learn consent enforcement, logging and deletion in code?
06 Do marketing teams learn lawful bases, honouring withdrawal, and the rules on children's data?
07 Does leadership learn accountability, breach decisions and board reporting?
The records
0 / 608 Is completion recorded per person, who completed what and when, exportable for audits?
09 Is there a real consequence when someone fails to complete required training?
The proof
0 / 610 Is there a refresh cycle, plus a change trigger: when a rule, process or system changes, the training changes with it?
11 Is there a knowledge-transfer plan, so internal owners can run the programme when external help leaves?
12 Have you tested understanding, not attendance?
| Score | Where you stand | What to do next |
|---|---|---|
| 0 to 8 | Exposed | Training is a launch-day memory or one deck for all. Map the audiences first. |
| 9 to 16 | Halfway | The material exists but the programme leaks: no refresh, no records, vendors left out. |
| 17 to 21 | Strong base | Run the three-question test below and close what it exposes. |
| 22 to 24 | Leading | Keep the change trigger honest: every legal or system change lands in the material. |
Any single "No" is a named gap, whatever the total says. Nothing leaves your browser.
What role-based training is
The people who touch personal data need to know what the DPDP Act requires of their specific work, plus a standing internal awareness channel that keeps the topic present. The board, staff who handle customer data, IT and developers, marketing, HR and the DPO office each need their own material, in their own terms.
The framework: four moves
Move 1: Map the audiences. Board and leadership, customer-facing staff, operations, IT and developers, HR, marketing, the DPO office, and partners or vendors who handle your data.
Move 2: Write curricula per role. Branch staff need request intake, verification and what never to send on personal channels. Developers need consent enforcement, logging and deletion in code. Marketing needs lawful bases, withdrawal honouring and children. Leadership needs accountability, breach decisions and board reporting.
Move 3: Deliver and record. Sessions for roles that need discussion, e-learning for scale, a portal as the standing resource. Most enterprises mix all three. Record who completed what, when; these records are audit evidence.
Move 4: Refresh on change and transfer knowledge. Set a refresh cycle and a change trigger, so a new rule, process or system lands in the training. Include partners and vendors where they handle your data. And before any outside help leaves, transfer the capability: internal owners trained to run the programme, not just to use it.
Template: the training plan
One row per audience. Copy this and fill it in.
| Audience | What they must know | Delivery | Refresh | Owner | Completion tracked where |
|---|---|---|---|---|---|
| Example: branch staff | Request intake, verification, channel discipline | Session + e-learning | Yearly, and on process change | HR with DPO office | LMS records |
| Example: developers | Consent enforcement, logging, deletion in code | Session | On system change | Engineering head | LMS records |
The downloadable file adds the full audience list and a column guide.
What good looks like at the end
You should have: role-based curricula and materials, a standing awareness channel, completion records, a refresh cycle, and a knowledge-transfer plan for any external support.
The live test: ask three people in three different roles what they would do if a customer asked them to delete their data. Three correct, consistent answers mean the training reached the floor. Three different guesses mean it did not.
Where enterprises go wrong
- One generic deck for every audience.
- Training measured by attendance, never by understanding.
- A one-off launch round with no refresh, quietly going stale.
- Partners and vendors left out of the net.
- Programmes where the only people who understand the system work for the vendor.
The decisions to make
- Delivery mode per audience: sessions, e-learning, portal.
- Frequency and the refresh trigger.
- Whether partners and vendors are in scope.
- How effectiveness is measured beyond attendance.
Next step
Seeing it and proving it, the dashboards and evidence that show the programme working. If you need help with any of this, write to us and we will help.