> 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/audit/questionnaire-types/tia.md).

# Transfer Impact Assessment (TIA)

Learn how to conduct a Transfer Impact Assessment (TIA) with Dastra.

## What is a TIA?

A Transfer Impact Assessment (TIA) is an analysis required when transferring personal data outside the EU/EEA to assess whether the destination country provides an essentially equivalent level of data protection. It is typically conducted alongside the implementation of a transfer mechanism such as Standard Contractual Clauses (SCCs).

TIAs are recommended by the European Data Protection Board (EDPB) and are required in practice when relying on SCCs for international transfers.

## TIA templates in Dastra

Dastra provides TIA templates in the questionnaire library, including:

* **Transfer Impact Assessment - TIA (outside EU/EEA)**: Dastra's standard TIA template (45 questions)
* **Data Transfer Impact Assessment (DTIA)**: a more comprehensive template (96 questions)

To access these templates, go to the "Questionnaire templates" tab, click **"Create a template"** → **"Automated questionnaires"**, and search for "TIA".

## Structure of a TIA questionnaire

A TIA questionnaire is typically structured around four steps:

1. **Understanding the Transfer** — describe the transfer: exporter, importer, nature and purpose of the transfer
2. **Identifying the Transfer Tool Used** — identify the legal mechanism used (SCCs, BCRs, adequacy decision, etc.)
3. **Assessing the Legislation and Practices of the Destination Country** — evaluate the legal framework of the destination country, including data protection legislation, data subjects' rights, remedies and sanctions, laws allowing access to data, and essential guarantees
4. **Implementing Supplementary Measures** — if the assessment reveals gaps, identify additional technical, contractual or organisational measures to bridge them

## Creating a TIA directly from a processing activity

When editing a processing activity in Dastra, you can create a TIA directly from a recipient marked as a processor:

1. Go to the **Recipients** tab of the processing activity
2. Open a recipient and scroll to the transfer section
3. Click **"Create a transfer impact questionnaire (TIA)"**

This automatically links the TIA response to the relevant transfer and recipient.

## Go further

{% content-ref url="/pages/rNkNzVSuXi6rd9VHOA1p" %}
[PIA / DPIA](/en/features/audit/questionnaire-types/pia-dpia.md)
{% endcontent-ref %}

{% content-ref url="/pages/WMkbHFF0GhVLIXcx5i9k" %}
[Legitimate Interests Assessment (LIA)](/en/features/audit/questionnaire-types/lia.md)
{% endcontent-ref %}


---

# 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/audit/questionnaire-types/tia.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.