1. Why mapping comes first
You cannot protect, move or defend data you do not know you have. Many companies discover that they hold copies of customer records, contracts or staff files in tools set up by a single department, without IT being aware of it. Data flow mapping answers a simple question: which information enters the organisation, where it is saved, who uses it and to whom it is sent.
The result serves several decisions: the record of processing activities required by the GDPR (Regulation (EU) 2016/679), the evaluation of suppliers, the backup plan, the choice of where to keep data and the response to an incident. A map produced once and never updated loses value quickly, so it should be treated as a living document, to be reviewed every time an important process changes.
2. Prerequisites: what to prepare first
Three things are needed before starting. The first is a person responsible for the collection, usually someone from administration or IT, with the authority to ask the departments for information. The second is an initial list of the main business processes: sales, administration, payroll, customer support, production or services, depending on your sector. The third is a shared space where the information is recorded, with access limited to the people who really need to see it.
No specific software is needed to start. The method matters more than the tool, and a well-structured file is enough for a small company. If your organisation is larger or regulated, ask an adviser or your support supplier which dedicated tools are suitable, without assuming that a product will solve the problem on its own. The time spent on this step pays off in the later phases.
3. The steps of the mapping
Proceed by process, not by system. Starting from software leads to a technical inventory that says nothing about the data circulating in day-to-day activities, such as files sent by email or exports made by hand. Each process should be described with the steps that follow, and the results should be noted on the same row of the map, so that the information stays linked together.
- List the processes that handle information about people, customers, suppliers and employees.
- For each process, note the types of data involved, such as personal records, contracts, payment details or reports.
- Identify the tools used, including unofficial ones such as shared spreadsheets or group chats.
- Record where the data is stored and for how long it is kept.
- Note who consults or modifies it, indicating the role and not the person's name.
- Record which suppliers or third parties receive the data, with the purpose of the transfer.
- Check whether backup copies exist and where they are kept.
4. Common mistakes
Mapping more often fails for organisational reasons than technical ones. The typical mistakes are these, and it is worth keeping them in mind while you work with the departments to avoid having to start again. Each one is easy to avoid if you know it in advance, but hard to correct once the map has been presented to management. Each one is a concrete trap, not a theoretical risk.
A final mistake is treating the map as a purely legal document. It also serves to decide what to do: which data to move, which to protect more carefully, which to delete because no longer needed. A map that does not lead to any decision quickly becomes an exercise to be filed away. When the map does not lead to concrete decisions, it is worth reviewing the method before moving on to other processes.
- Limiting the scope to official IT systems and forgetting the spreadsheets and chats used in daily work.
- Describing processes as management imagines them, rather than as they actually run.
- Recording suppliers without indicating which data they receive and for what purpose.
- Stopping at the first version without planning a periodic update.
- Keeping the map in a folder that the people who need to use it cannot access.
5. How to check the map is complete
Use the table as a final check. Every row must have a verifiable answer, not an impression. If a check cannot be closed, the map is not complete, and you should flag the gap to be filled, assigning it to an owner with an agreed deadline. The check does not need to be perfect on the first pass, provided every gap is recorded and assigned to an owner with a deadline.
Repeat the checks when processes, suppliers or tools change, and in any case at a cadence decided internally. A map that nobody updates quickly becomes a façade document, and the gap between what is written and what happens grows without anyone noticing. A written confirmation from each owner, with the date, makes responsibility clear and reduces later discussions.
| Check | How to do it | Expected outcome |
|---|---|---|
| Process coverage | Compare the list with the organisation chart and with department heads | Every department that handles data appears at least once |
| Unofficial tools | Ask which shared files and services are used in the work | External tools are noted with a purpose |
| Suppliers | Compare with the service contracts and invoices | Every supplier that receives data has a dedicated row |
| Backup copies | Ask IT or the supplier where the backups are stored | Every copy is linked to the original data |
6. Using the map for decisions
A complete map serves to answer concrete questions. Which data leaves the company, and to which suppliers? Which processes handle sensitive data and require stronger controls? Where are the backup copies kept? Each answer links the map to a decision: renegotiating a contract, changing a supplier, restricting access to a shared folder or deleting a copy that is no longer needed.
It is worth linking the map also to the record of processing and the supplier list. This way a change in one department is reflected in the documents that derive from it, without having to rebuild them from scratch each time. The link also reduces the risk of two documents saying different things about the same processing. A periodic check prevents the map drifting away from reality.
7. How to start
This week, choose just one high-impact process, for example the one that manages customer records or payroll, and map it using the steps in section three. Record the results in a shared document with the department head and ask for a review within an agreed deadline. Choose the process for which a gap would have the most visible consequences, so that you get visible results from the first steps.
When the first process is closed, move on to the next and report the gaps that emerged. With the method proven, the map grows in small steps without blocking daily work, and becomes the basis for the other guides in the data sovereignty series. Every completed process should be recorded with the review date and the name of the owner who confirmed it, so that the map remains traceable.
Frequently Asked Questions
How long does a mapping take?
It depends on the size of the organisation and the number of processes that handle personal data. A reliable estimate is not possible without a first round of interviews with the departments. It is best to start with a single process, measure how long it takes and use that figure to plan the rest of the work.
Who should take part in the mapping?
The person responsible for the collection coordinates, but the heads of the departments who know the real processes are needed, and the data protection officer or an adviser where one exists. IT helps identify systems, but on its own cannot see the files used in daily work, which are often the most sensitive part to record.
Does the data map replace the record of processing?
No. The map is a working tool that feeds the record of processing required by the GDPR, but the two documents have different content and formats. Check with an adviser which information the record must contain in your case, and how to link it to the map without duplicating the work.
Do I need a dedicated software tool?
Not necessarily. For a small organisation a well-structured shared spreadsheet is enough, provided it is clear who updates it and who can access it. Dedicated tools become useful when processes are numerous, change often or need to be linked to other management systems. Evaluate the options with the supplier, without relying on a single product as the only solution.
What do I do if I find data in unexpected places?
Do not delete it straight away without assessing it. Note where it is, who created it, why it is needed and whether it contains personal data. Then decide with the manager whether to move it to a controlled location, restrict access to it or delete it, in line with internal rules and applicable law. Document the decision, because it will be the evidence of your action.