# Template: data mapping sheet

One sheet per process flow: customer onboarding, payroll, marketing campaigns, loan servicing, and so on. Interview the process owner, trace the flow end to end including integrations and exports, then validate with IT against real systems.

| Field | Your entry |
| --- | --- |
| 1. Process and owner | Example: customer onboarding, owned by head of retail banking |
| 2. Whose data | Example: customers, and their nominees |
| 3. What data | Example: name, contact, ID proof, photograph, financial details |
| 4. Source | Example: collected directly through the branch form and the app |
| 5. Purpose and legal basis | Example: open and service the account; consent, plus regulatory obligation |
| 6. Where it lives | Example: core banking app, document store, CRM; nightly backups |
| 7. Where in the world | Example: primary hosting in India; support access from one overseas centre |
| 8. Who can reach it | Example: branch ops, central ops, two admin roles |
| 9. Who receives it | Example: KYC agency, card printer, group analytics entity |
| 10. How long it stays | Example: for the relationship plus 5 years from closure; trigger is account closure; deletion by scheduled purge |
| 11. Safeguards in place | Example: encryption at rest, role-based access, access logging |
| 12. Risk flags | Example: large scale; financial data. Impact assessment done. |

Notes:

- If a field cannot be answered, write "not known" rather than leaving it blank. Every "not known" is a gap to close.
- Field 5 feeds the notice and consent work. Field 10 feeds retention and erasure. Field 12 flags the flows that need an impact assessment.
- Update the sheet when the process changes: a new vendor, a new system, a new report.
