From pre-scan to decision in one route Risks and measures with an owner Data protection officer's advice recorded

Custom DPIA workflow tool development

Appfront builds workflow tools for organisations that carry out DPIAs (data protection impact assessments): a pre-scan that determines whether a DPIA is needed, a questionnaire per processing activity, risks and measures with an owner, the advice of the data protection officer, the controller's decision, and a reassessment when the processing changes. Integrated with the record of processing activities, so for every processing activity you can see whether there is a DPIA and what came out of it.

What is a DPIA workflow tool?

Under the GDPR, an organisation must carry out a data protection impact assessment (DPIA) when processing is likely to result in a high risk to the people whose data is involved. Think of large-scale processing of health data, camera surveillance or profiling. A DPIA describes the processing, assesses the risks and records measures. The data protection officer advises. A workflow tool guides the organisation through those steps.

In many organisations, a DPIA is a text document that someone fills in and emails around. Whether a DPIA is needed is assessed differently for each project. Measures are listed in the document, but nobody follows them up. The officer's advice sits in an email. And when processing changes, nobody knows the DPIA needs to be redone. When the supervisory authority asks a question, everything has to be hunted down.

We build custom because the workflow has to fit your organisation: which DPIA model you use, for example a government model or your own, who drafts, advises and decides on the DPIA, how your record of processing activities is set up, and how measures are followed up. When a DPIA is mandatory and what it must contain is something you determine with your data protection officer; the tool makes sure the process is followed.

Needed or not

A pre-scan per processing activity based on the criteria for a mandatory DPIA, with the outcome and the justification recorded.

Risks with measures

Risks with likelihood and impact, and measures with an owner and deadline that are followed up until they are completed.

Advice and decision

The data protection officer's advice and the controller's decision on the DPIA, with date and justification.

How we build your DPIA workflow tool

We start with your DPIAs: how many per year, which model, who is involved, and how measures are currently followed up.

1
Mapping process and model

Your DPIA model, roles, record of processing activities, and how measures are followed up.

2
Pre-scan and questionnaire

The pre-scan per processing activity and the questionnaire based on your model.

3
Risks, measures and advice

Risk analysis, measures with an owner, the officer's advice and the decision.

4
Reassessment and integration

Reassessment on change, integration with the record of processing activities, reporting, and then ongoing maintenance.

What a DPIA workflow tool actually does

The components below come up at almost every organisation that carries out DPIAs. Which ones you need depends on the number of processing activities.

Pre-scan

A short questionnaire that determines whether a DPIA is needed, with the justification.

Questionnaire

Description, purpose, legal basis, data, data subjects and recipients per processing activity.

Risk analysis

Risks to data subjects with likelihood and impact, and the residual risk after measures.

Measures

Measures with owner, deadline and status, followed up until they are completed.

Advice and decision

Advice from the data protection officer and decision by the controller.

Reassessment

A notification when processing changes or a reassessment is needed.

Who we build a DPIA workflow tool for

The tool is intended for organisations with many processing activities and regular DPIAs.

Municipalities

Many processing activities in the social domain and enforcement. The model and the integration with the register are the core.

Healthcare organisations

Health data on a large scale. Risks and measures matter most.

Schools and universities of applied sciences

Digital learning tools and systems with student data. The pre-scan is what you need.

Financial service providers

Profiling and automated decisions. Advice and decision-making are at the core.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page covers DPIAs. For data processing agreements, see our page on a contract register for data processing agreements; for data cleansing, our page on GDPR software; and for risk and compliance, our page on a GRC platform. You can read about our approach at building software.

Pre-scan Questionnaire following your model Risk analysis Measures with an owner Advice from the data protection officer Decision by the controller Prior consultation Reassessment on change Integration with the record of processing activities Reporting

Why Appfront for your DPIA workflow tool?

A DPIA that sits in a folder protects no one. That's what we build on: a route everyone follows, measures that actually get carried out, and a reassessment when it's needed.

Everyone follows the same route

The pre-scan, questionnaire, advice and decision follow the same process for every DPIA.

Measures carried out

Every measure has an owner and stays visible until it has been completed.

Ready for any question

For each processing activity you can see whether there is a DPIA, what came out of it and who made the decision.

Security and privacy in a DPIA workflow tool

The tool contains descriptions of processing activities, risks and security measures: information that should not be public. Access is set up by role: the author works on their own DPIA, the data protection officer advises, the controller decides.

The tool runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about a DPIA workflow tool

Questions that privacy officers and lawyers ask before getting started.

It uses a pre-scan to determine whether a DPIA is needed, guides the author through the questionnaire, records risks and measures, collects the advice of the data protection officer and the decision, and flags when a reassessment is needed.

Under the GDPR, when processing is likely to result in a high risk to data subjects. The Dutch Data Protection Authority (Autoriteit Persoonsgegevens) publishes a list of processing activities for which a DPIA is mandatory. What applies to your processing activities is something you determine with your data protection officer.

Yes. The questionnaire follows the model you use, for example a model used within government or your own.

If a high risk remains after measures have been taken, the Dutch Data Protection Authority must be consulted in advance. The tool records whether this is necessary and what the outcome was.

Every measure gets an owner and a deadline, and stays visible until it has been completed. The data protection officer can see the progress.

Yes. For every processing activity in the record you can see whether there is a DPIA, and the DPIA refers back to the processing activity.

Check that first. There are privacy management packages with a DPIA module, and they work well if your model fits within them. Custom development makes sense if you have your own model, if the workflow needs to connect to your own record and systems, or if measures need to land in your existing follow-up process.

DPIAs that follow a fixed route, with measures that actually get carried out?

Tell us how many DPIAs you carry out each year, which model you use and how measures are currently followed up. We'll show you what the pre-scan, the risk analysis and the advice look like.

Edit content