Register of information starter
A five-sheet starter that mirrors the standard templates for the register of information, so the function, arrangement and provider data is collected once.
Compliance5 Sept 20263 min read
On this page
register-of-information.xlsx · 12 kBLicensed CC BY 4.0
What this is
A five-sheet workbook mirroring the standard templates in Annex I of Commission Implementing Regulation (EU) 2024/2956 1. Function, arrangement and provider data is collected once, in the shape those templates need. It is the artefact produced by sections 3.8 and 3.9 of DORA implementation, and supports one decision per row: does this arrangement sit behind a critical or important function.
It is not a replacement for the standard templates, and not a submission format. The submission format is the authority's to set; this file is the working layer underneath.
How to use it
- Delete every row marked
EXAMPLE - delete. Three appear on each working sheet. - Fill Functions first. The criticality decision belongs to the function, not the contract. See the playbook, section 3.4.
- Work the Template map so each Annex I template has an owner role and a source system before data is collected.
- Fill Arrangements next, one row each, pointing at a function identifier. See the playbook, section 3.8.
- Fill Providers last, including subcontractors that effectively underpin critical or important functions 2.
- Resolve the closed-option columns before writing free text. Reliance, substitutability and criticality each take a value from a fixed list.
- Identify every provider that is a legal person by a valid and active LEI or EUID, and by both where both exist 3.
- Keep one value per data element, so a second valid value needs a second row 4. See section 3.9.
Sheets and columns
| Sheet | Mirrors | Columns |
|---|---|---|
| Read first | — | Licence, scope, identifier and closed-option rules |
| Template map | Annex I | The fifteen codes and titles, in order |
| Functions | B_06.01 | Identifier, activity, name, criticality, objectives |
| Arrangements | B_02.01, B_02.02 | Reference, type, function, dates, notice, law, locations |
| Providers | B_05.01, B_05.02, B_02.02, B_07.01 | Code and type, name, country, Rank, reliance, substitutability, exit plan |
Column names are as printed in the Implementing Regulation; ID is a local key, not part of it.
What good looks like
Six columns from the Providers sheet, example prefix dropped.
| ID | Identification code | Type of code | Rank | Substitutability | Existence of an exit plan |
|---|---|---|---|---|---|
| PR-001 | 1111AAAA2222BBBB3301 | LEI | 1 | 1. Not substitutable | 1. Yes |
| PR-002 | 1111AAAA2222BBBB3302 | LEI | 2 | 2. Highly complex substitutability | 1. Yes |
| PR-003 | 1111AAAA2222BBBB3303 | LEI | 1 | 4. Easily substitutable | 2. No |
Two things make those rows usable. Rank places each provider in one chain, so a subcontractor is visible rather than implied. Substitutability is a closed-list value, so two readers cannot disagree about it.
Fields
| Field | Required | Meaning | Common mistake |
|---|---|---|---|
| Function Identifier | yes | The key every arrangement points at | Creating it after the contract rows |
| Criticality or importance assessment | yes | The decision, from a closed list | Copying a procurement tier |
| Identification code, Type of code | yes | LEI or EUID for a legal person | A local vendor number |
| Rank | yes | Position in the supply chain | Leaving subcontractors out |
| Level of reliance, Substitutability | yes | Closed-list assessments | Free text nobody can compare |
| Existence of an exit plan | yes | Whether a plan exists | Recording intent, not a plan |
Download
- File:
register-of-information.xlsx(xlsx, 12 KB) — five sheets. - Markdown variant: the same tables at
content/templates/assets/_register-of-information.md. - Licence: CC BY 4.0 — reuse and adapt with attribution to GRCIDE.
- Version: 1.0, 2026-09-05. No personal data, no organisation names; example rows are invented.
Related
- Playbook: DORA implementation, sections 3.8 and 3.9.
- Radar: the subcontracting technical standard
References
- European Commission. Commission Implementing Regulation (EU) 2024/2956. https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj/eng 5
- European Parliament and Council. Regulation (EU) 2022/2554 (DORA). https://eur-lex.europa.eu/eli/reg/2022/2554/oj/eng 6
Standards and certification names are the property of their respective owners. GRCIDE is an independent publication and is not affiliated with, authorized, sponsored or endorsed by any standards body.
Sources
- 1EU Publications Office CELEX 32024R2956 Annex I · verified 2026-09-05
- 2EU Publications Office CELEX 32024R2956 Art. 3(2) · verified 2026-09-05
- 3EU Publications Office CELEX 32024R2956 Art. 3(5) · verified 2026-09-05
- 4EU Publications Office CELEX 32024R2956 Art. 4 · verified 2026-09-05
- 5EU Publications Office CELEX 32024R2956 · verified 2026-09-05
- 6EU Publications Office CELEX 32022R2554 · verified 2026-09-05
Related
- DORA implementation
Playbook
- AI use-case triage form
Template
- China–EU regulatory bridge
Reference