# FAQ: Universal ROPA

*Audience: prospects evaluating Relyance, and new customers getting started.*

## What is the Universal ROPA, in one paragraph?

It's your Record of Processing Activities, generated from what Relyance discovers in your source code, infrastructure, vendors, contracts, and websites, instead of from interviews and spreadsheets. Each processing activity is recorded with its controller, processor, data subjects, data elements, legal basis, retention period, transfers, and the sources behind each value. Your team reviews, edits, and approves the records, and every change is logged. Find it under **Comply → Universal ROPA™**.

## Do I have to build the ROPA from scratch?

No. Relyance creates records from the vendors and systems in your inventory as discovery runs, and keeps them current. You review them, fill in what can't be discovered - such as the purpose of processing and the legal basis - and add any activities no system reveals with **Add Processing Activity**.

## Does Relyance use AI to build the ROPA?

Yes, where AI prediction is enabled. When a vendor is added, Relyance uses AI to choose its most relevant processing activity, fills in that activity's standard details (legal basis, data subjects, recipients, and purpose), and predicts whether the vendor is a processor, joint controller, or subprocessor. The predictions are based on your business description, the vendor's purpose, and where Relyance found it. Predicted values are labelled **Machine Learning Prediction**, predicted records start as **Discovered**, and a person approves them. See [How Relyance predicts your ROPA](/docs/universal-ropa/overview-and-implementation-guide/#how-relyance-predicts-your-ropa).

## Why does the same processing activity appear several times?

Each record is one processing activity with one controller and one processor. An activity carried out with three processors is three records. Group the list by **Processing Activity** to see them together, and open the group to edit them all at once. See [Working with groups](/docs/universal-ropa/admin-configuration-guide/#working-with-groups).

## Will Relyance overwrite my edits?

No. Values you add stay on the record. When you remove a value that discovery added, Relyance remembers the removal and doesn't add it back. Discovery still adds new values it finds, and those show up in the audit log under the user **System**.

## How does Relyance decide who is controller and who is processor?

From the vendor's data-handler role. When a vendor processes data on your behalf, your business entity is the controller and the vendor is the processor. When you process data on behalf of your customers, the controller is **Your Customer**. Where role prediction is enabled, Relyance also uses AI to predict the role and shows its confidence and evidence when you hover over the controller or processor. Always review the role before approving a record.

## How do I know where a value came from?

Every value carries its source - **Operational Reality**, **Contract**, **Assessment**, **Public Knowledge**, or **Manually Added**. Select a value on a record to see its **Data Sources**. The **Discovery Source** column shows which systems found the activity. See [Provenance: sources](/docs/universal-ropa/audit-log-and-reporting/#provenance-sources).

## What do the statuses mean?

**Discovered** records are waiting for review, **Draft** records are work in progress, **Approved** records are signed off, and **Archived** records are no longer active. **Disapprove** sends a record back to **Discovered**. A **Draft** record can't be approved until you change its status.

## Can I update many records at once?

Yes. Select records and choose **Bulk Edit** to add, remove, or replace values in a field across all of them, with a preview before anything changes. You can also approve, disapprove, archive, delete, export, and create assessments in bulk. See [Bulk actions](/docs/universal-ropa/admin-configuration-guide/#bulk-actions).

## Can I add fields that aren't in the standard ROPA?

Yes. Add custom fields from any record's **Additional Fields** card - text, date, dropdown, multi-select, URL, number, yes/no, duration, or location. They appear on every record and in the list, filters, bulk edit, and export. See [Custom fields](/docs/universal-ropa/admin-configuration-guide/#custom-fields).

## Can I export the ROPA for a regulator?

Yes. **Excel Export** downloads the records you've selected, or every record matching your filters, with the columns you're showing, up to 10,000 records per export. See [Exporting the ROPA](/docs/universal-ropa/admin-configuration-guide/#exporting-the-ropa).

## Can I run a DPIA on a processing activity?

Yes. Select records and choose **Create Assessment**, or use **Create Assessment** on a record or group page. A record's **Articles** tab lists the assessments linked to it. See [Creating assessments](/docs/assessments/admin-configuration-guide/#creating-assessments).

## Is a deleted record gone for good?

Deleting a record removes it from the ROPA, and the deletion is recorded in the audit log. To take a record out of use but keep it on file, archive it instead.

## Is there an API for the ROPA?

Not a published one yet. Use the Excel export to get ROPA data out of Relyance.
