# DORA register of information: tool requirements matrix

Original T-NEX working aid. Version: 11 September 2026. Edit locally; no information is transmitted to T-NEX.

This template tests a tool; it is not an official register or submission format. Add institution-specific requirements. Check the applicable ITS/taxonomy version and actual reporting channel before acceptance.

## 1. Review scope

- Institution / entity: [complete]
- Supplier, product and version: [complete]
- Reviewer / business owner: [complete]
- Date and test environment: [complete]
- Applicable register/taxonomy version and source: [complete]
- Test data and cases covered: [complete]

## 2. Set criteria

Must = required; should = preferred; not applicable = reason required. An open result is not a pass.

| ID | Area | Question | Evidence task |
| --- | --- | --- | --- |
| ROI-01 | Data model | Can entities, contracts, ICT services, functions and providers be linked unambiguously? | One test contract with two services and a shared dependency, without duplicate master records. |
| ROI-02 | Identifiers and relationships | Are permitted identifiers and references maintained consistently? | Deliberately introduce missing, duplicate and unresolved identifiers in a sample dataset. |
| ROI-03 | Data quality | Are required fields, value lists and business inconsistencies explained clearly? | An error list identifying field, record, rule version and owner; recheck the correction. |
| ROI-04 | Supply chain | Can a provider change be traced to affected contracts and functions? | Enter one change and show its impact on the affected register records. |
| ROI-05 | Maintenance and approval | Who can edit, review and freeze a reporting snapshot? | Role changes, change history and traceable approval demonstrated in a complete workflow. |
| ROI-06 | Export and version | Does the export match the submission version actually required? | Declared taxonomy/schema version and reproducible export from a recorded data snapshot. |
| ROI-07 | Feedback | How are validation failures and follow-up questions resolved? | Link feedback to a register snapshot, correct it, re-export and retain the earlier version. |
| ROI-08 | Operations and handover | Will data, relationships and evidence remain usable after a supplier change? | Complete trial export with a field dictionary, attachments and documented limitations. |

## 3. Response and assessment sheet

| ID | Must/should/n.a. | Supplier answer | Evidence/version | Result | Deviation/deadline | Reviewer |
| --- | --- | --- | --- | --- | --- | --- |
| ROI-01 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-02 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-03 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-04 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-05 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-06 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-07 | [ ] | [ ] | [ ] | open | [ ] | [ ] |
| ROI-08 | [ ] | [ ] | [ ] | open | [ ] | [ ] |

## 4. Decision

- Missing mandatory evidence: [complete]
- Conditions and open actions: [complete]
- Business completeness assessed separately by / on: [complete]
- Decision / rationale / owner / date: [complete]
- Reassessment on version change: [complete]


## Sources and context

- [Verordnung (EU) 2022/2554: DORA, insbesondere Artikel 11, 24 und 28–30](https://eur-lex.europa.eu/eli/reg/2022/2554/oj)
- [Durchführungsverordnung (EU) 2024/2956: Vorlagen für das Informationsregister](https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj)