Before you start
Business owners and IT or privacy leads preparing a first data-flow map.
Save your own copy and read Worked Example before completing Your Data Flow. Choose one activity and ask someone who performs it to explain the work, keeping different purposes separate, such as handling an enquiry and sending marketing. Record category names only, with people's records, messages and screenshots kept outside this workbook.
Use Not verified and record what needs checking, the responsible person or role, an evidence request and target date. The system owner can clarify access, suppliers and backups, while the responsible privacy or legal adviser can advise on applicable duties and retention obligations. Keep unverified assumptions separate from approved rules.
Using the guide
Choose one activity
A recognisable activity, such as workshop booking, recruitment or customer support, provides a manageable starting point. Name its business owner and the people whose information is involved.
Personal data means information about someone who can be identified from it, alone or with other information, so record categories such as names, business email addresses or support messages while keeping actual records elsewhere. Different purposes need separate consideration: answering an enquiry and adding someone to a marketing list are different activities.
Understand the information flow
A recent example, explained by the person doing the work without exposing personal records, helps reveal the actual flow. Each handoff is a movement between systems or people, such as a booking system sending details to an email service.
Give each handoff or working copy its own row, repeating stages where needed to include shared inboxes, spreadsheets, messaging tools and backups. Follow each copy through to the end of use, describing what a supplier receives and does as well as naming the supplier.
Record purpose, access and location
For each row, describe why the information is used, which data categories are needed and who can see it, distinguishing staff access from suppliers and other recipients. Hosting means where a system stores or processes information, while support staff may access it from somewhere else. Record countries or regions where known.
In Evidence / Follow-up, reference the notice, agreement or internal instruction the owner says applies, or a dated record such as an access review. These references identify what was checked while its contents stay elsewhere; legal adequacy still needs a separate assessment.
Record questions for review
Where a location, recipient or deletion process remains unclear, use 'not verified' and record the question, responsible person and target date in Evidence / Follow-up. Retention means how long a copy is kept or what event ends its use, including exported copies and relevant backups. An unconfirmed retention period remains open for review, and a convenient storage setting does not establish a legal requirement.
Confirm the map and choose actions
Review the rows with the business owner and system administrator, checking that each handoff has an owner, an evidence reference or assigned question, and an explanation of what happens at the end of use. Record the last verified date after this review; open questions may remain where they have an owner and next action.
The map can then guide changes such as removing an unnecessary export, narrowing access or agreeing a deletion process, with another review when the activity, system or supplier changes. For India's Digital Personal Data Protection (DPDP) framework, check applicability and when relevant duties take effect separately, as implementation is phased.
Fictional example: Riverstone Training
Riverstone Training runs workshops. Its operations lead follows a registration through the booking system, confirmation emails and a trainer's attendance export. In this fictional example, supplier access locations and deletion decisions still need confirmation.
- Activity
- Register participants and deliver a booked workshop.
- People and Data
- Participants: name, business email, selected workshop and attendance status.
- Flow
- Website form → booking system → confirmation email and restricted trainer attendance file. The trainer receives names and session details, not the full booking record.
- Next decision
- The operations lead and IT administrator will confirm supplier access locations and approve how booking records, exports and backups reach the end of their lifecycle.
Points to consider
- Mapping only the main application and missing email attachments or exported copies.
- Treating a policy statement as evidence of what actually happens.
- Treating an unresolved recipient, retention or ownership question as a confirmed fact.
Your next step
Review each handoff with the activity owner and agree who will resolve the open questions. The resulting map provides a starting point for a separate privacy and security review, without establishing compliance by itself.
Sources
Your editable worksheet
The download includes a How to Use tab, a blank working sheet and a clearly fictional completed example. Keep sensitive information in your approved systems. The worksheet helps organise work. It does not establish compliance or certification.
