> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/ropa/activity.md).

# Complete a data processing activity

Learn how to fill in 100% of the information relating to a single data processing in your register.

## A processing creation process that guides you step by step

The Dastra application guides you through each step of the process of creating a processing activity, while leaving you free to work at your own pace. Benefit from advice at every step and become compliant with the GDPR requirements.

## The Dastra processing questionnaire

The processing questionnaire collects the information required for a processing activity. It is split into sections, listed in the navigation on the left of the processing activity. Next to most sections, the navigation shows how many items you have already entered (purposes, datasets, recipients, etc.). Use **Next** and **Back** at the bottom of the page to move from one section to another.

A **Data controller** processing activity has 12 sections:

* **General** - Enter general information on the processing of personal data, such as its name, organizational unit and description.

{% content-ref url="/pages/-M6E1QoNOuJYaOThm8WI" %}
[General information](https://doc.dastra.eu/en/features/ropa/activity/general.md)
{% endcontent-ref %}

* **Parties involved** - List the users in charge of the processing activity and the stakeholders involved, such as joint controllers or the processing implementation manager.

{% content-ref url="/pages/-M6E24PHuVMBVnEFj-NI" %}
[Stakeholders](https://doc.dastra.eu/en/features/ropa/activity/stakeholders.md)
{% endcontent-ref %}

* **Purposes** - Describe the purposes of the processing and the lawful basis of each one.

{% content-ref url="/pages/-M6E2s4H0EQWnHgHMK0N" %}
[Purposes](https://doc.dastra.eu/en/features/ropa/activity/purposes.md)
{% endcontent-ref %}

* **Assets** - List the assets, internal or external to the organization (applications, software, servers, etc.), that support the processing activity.

{% content-ref url="/pages/-M6E3cFvODZHW6K\_bxTI" %}
[Assets](https://doc.dastra.eu/en/features/ropa/activity/assets.md)
{% endcontent-ref %}

* **Datasets** - List the categories of data processed and their retention policies.

{% content-ref url="/pages/-M6E2KBYOqFfcpfKeJfW" %}
[Datasets and retention](https://doc.dastra.eu/en/features/ropa/activity/datasets.md)
{% endcontent-ref %}

* **Data subject** - List the categories of data subjects concerned by the processing.

{% content-ref url="/pages/-M6E3ukQo6e-uPJGWLWL" %}
[Data subjects](https://doc.dastra.eu/en/features/ropa/activity/data-subjects.md)
{% endcontent-ref %}

* **Subject's rights** - Detail how data subjects can exercise each of their rights.

{% content-ref url="/pages/-M6E4JiI\_3UVufPWUpy5" %}
[Data subjects rights (DSR)](https://doc.dastra.eu/en/features/ropa/activity/rights.md)
{% endcontent-ref %}

* **Recipients** - List the recipients of the data. This is also where you declare data transfers outside the EU.

{% content-ref url="/pages/-M6E4ha2ieA6B9nz1d1J" %}
[Recipients](https://doc.dastra.eu/en/features/ropa/activity/recipients.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M6E5UkEU2AFCrIgtOlP" %}
[Data transfers outside the EU](https://doc.dastra.eu/en/features/ropa/activity/recipients/transfers.md)
{% endcontent-ref %}

* **Measures** - Describe the technical and organizational security measures that protect the data.

{% content-ref url="/pages/PUzRGRCIFbFXa3rD3HJV" %}
[Security measures](https://doc.dastra.eu/en/features/ropa/activity/security.md)
{% endcontent-ref %}

* **Impact assessment** - Assess whether the processing requires a data protection impact assessment (DPIA).

{% content-ref url="/pages/-M6E6sWom2H7F\_vNOCJk" %}
[Impact assessment](https://doc.dastra.eu/en/features/ropa/activity/impact-analysis.md)
{% endcontent-ref %}

* **Documentation** - Document the processing activity and upload any additional document (for example, code of ethics, privacy policy, etc.).

{% content-ref url="/pages/-M6E7eJIcRhEDxeYJF2J" %}
[Documentation](https://doc.dastra.eu/en/features/ropa/activity/documents.md)
{% endcontent-ref %}

* **Summary** - Review everything entered in the previous sections on a single page.

{% content-ref url="/pages/kGDYmlHXiN29BzhEm8tW" %}
[Summary](https://doc.dastra.eu/en/features/ropa/activity/summary.md)
{% endcontent-ref %}

{% hint style="info" %}
A **Data processor** processing activity follows the same path, with two differences: a **Controllers** section, placed after **Datasets**, lists the customers on whose behalf you process the data, and there is no **Impact assessment** section. See [the "Data processor" record](https://doc.dastra.eu/en/features/ropa/processor.md).
{% endhint %}

Custom fields defined by your organization can also appear in any of these sections.

Once you have entered the information you have, you can start identifying what remains to be done.

{% content-ref url="/pages/-Lw3hALWsjvX2sseOt14" %}
[Planning](https://doc.dastra.eu/en/features/tasks.md)
{% endcontent-ref %}

## Indicators on processing activities

The questionnaire is not the only guide available when you fill in a processing activity. Three indicators help you assess how complete, how well documented and how sensitive the activity is. They are displayed in the panel on the right of the processing activity and in its **Summary** section:

* **Overall progression**
* **Quality**
* **Sensitivity**

### Overall progression

This percentage is calculated from a series of checks that verify that the processing activity contains all the mandatory elements: purposes, datasets with their data fields and retention rules, data subject categories, recipients, security measures and, for a data processor activity, controllers.

These elements correspond to the information that Article 30 of the GDPR requires in the record of processing activities.

### Quality

This percentage is calculated from a series of checks on the quality of the elements you have entered in the form. For example, these checks verify that:

* each purpose has a lawful basis,
* at least one asset is linked to the processing activity,
* the exercise of data subject rights is described,
* the **Impact assessment** section has been completed and, where a DPIA is required, that it has been carried out,
* an **Accountable** user is assigned to the processing activity,
* a transfer is declared for each recipient located outside the EU.

These criteria go beyond Article 30 of the GDPR and help you anticipate other obligations. For example:

* carrying out a DPIA on a processing activity that requires one,
* identifying the software that supports the processing activity, which tells you who its editor is: you can then identify the processor and any data transfers.

### Sensitivity

This indicator shows the **sensitivity level of the processing activity**.

It is calculated automatically from the **following criteria**:

* presence of sensitive data,
* presence of minors and/or vulnerable persons among the data subjects,
* large volume of data subjects,
* presence of a processor,
* presence of a transfer to a country without an adequate level of protection,
* need to carry out a DPIA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.dastra.eu/en/features/ropa/activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
