Correction & completion (S.12)
- Reference
- DSR-2026-004820
- Status
- In progress
- Data Principal
- Tanvi Malik
- Contact
- ta••••••@rediffmail.com · ••••••9433
- Received
- 16 Apr 2026, 09:30
- Channel
- portal
- Language
- HI
- Identity
- Verified(otp mobile)
- Field
- residential_address
- Change
- 12-04-1978 → 12-04-1979
Runs from receipt. The organisation publishes this period, which makes it binding.
- Due
- 16 May 2026, 09:30
- Assigned to
- Progress
- 3 of 6 steps complete
Fulfilment steps
Each step is a system that must actually do something. A response issued before these complete is a response that will generate a grievance.
- Verify the requester's identityIdentity verification · Rohit Verma · 19 Apr 2026
- Locate every copy of the affected fieldData Discovery · Priya Nair · 22 Apr 2026
- Apply the correction in the golden sourceFamily ID Core Registry · Rohit Verma · 22 Apr 2026
- In progressPropagate the correction downstreamScheme Beneficiary Warehouse · Rohit Verma
- Notify recipients the data was shared withVendor Registry
- Confirm completion to the Data PrincipalRights portal
History
Events marked as visible are also shown to the Data Principal when they track the request.
- Request submitted4 months ago
Received through the Data Principal portal.
16 Apr 2026, 09:30Data PrincipalVisible to the Data Principal - Acknowledgement sent4 months ago
Reference number issued; response due within 30 days.
16 Apr 2026, 10:30SystemVisible to the Data Principal - Identity verified4 months ago
One-time code confirmed against the registered mobile number.
17 Apr 2026, 09:30SystemVisible to the Data Principal - Data map assembled4 months ago
Personal data located across connected sources and attached to the request.
18 Apr 2026, 09:30Data Discovery
Data map (8 elements)
Assembled automatically from Discovery. This is what makes a Section 11 response complete rather than best-effort — and it is only as good as discovery coverage.
Covering approximately 1.22 Cr records across 8 systems.
Response
Templates are bilingual and pre-populated. Section 11(b) requires the identities of other Data Fiduciaries the data was shared with to be disclosed, so the access template always lists recipients.