# Data Map Worksheet

Use this before a pilot, AI experiment, privacy review, or integration discussion. A data map makes it easier to explain what the product collects, where data moves, who can access it, and which features depend on it.

## Product Context

- Product or feature:
- Date:
- Owner:
- Environment:
- Primary workflow:

## Data Inventory

| Data type | Source | Identifiable? | Access roles | Stored where | Retention | Purpose | Downstream feature | Owner | Open risks |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |  |  |  |  |

## Data Movement

| Step | From | To | Method | Security control | Audit trail? |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

## Governance Checks

- [ ] Data sources are documented.
- [ ] Consent or authority to use data is understood.
- [ ] Identifiable data is separated from non-identifiable data where practical.
- [ ] Access roles match real job needs.
- [ ] Retention and deletion expectations are written.
- [ ] Dataset versions or source versions are trackable.
- [ ] Audit trail covers important access and changes.
- [ ] Downstream AI, reporting, or integration dependencies are named.

## Open Questions

| Question | Owner | Needed by | Decision or evidence needed |
| --- | --- | --- | --- |
|  |  |  |  |