Building your DORA Register of Information
The fifteen templates and a build sequence that avoids rework.
Read the guide →The register covers all contractual arrangements for ICT services from ICT third-party service providers. Every word of that is doing work, and the register grows or shrinks by an order of magnitude depending on how each is read.
Article 28(3) of Regulation (EU) 2022/2554 requires a register covering all contractual arrangements on the use of ICT services provided by ICT third-party service providers. There is no materiality threshold and no value floor. The common assumption that only critical or important arrangements belong is the single largest source of understated registers.
What criticality changes is the depth of what must be recorded — particularly how far the supply chain is documented and which assessments are attached — not whether the arrangement appears at all.
ICT services are digital and data services provided through ICT systems on an ongoing basis, including hardware as a service and hardware support. Two boundaries recur:
Genuinely outside are non-digital services, and financial services received from a regulated entity that are not ICT services in themselves.
An ICT third-party service provider is an undertaking providing ICT services. The status is defined by what is provided, not by the commercial relationship, which produces two results firms often resist:
| Relationship | Treatment |
|---|---|
| Intragroup provider | In scope. A shared services entity providing ICT services under a contractual arrangement is recorded like any other provider, with the intragroup nature recorded rather than used as an exclusion. |
| Cloud and platform providers | In scope, and typically the most consequential entries because of the supply chain and data-location detail attached. |
| Subcontractors | Recorded through the supply chain templates, by rank, where they support a critical or important function. |
| Individual contractors | Turns on whether the arrangement is for staff augmentation under the firm’s own direction or for the provision of an ICT service. Document the reasoning. |
The critical-or-important determination governs how much has to be documented: the depth of supply chain disclosure, the assessments of substitutability and exit, and the level of scrutiny the supervisor will apply. Doing it after the arrangement inventory is complete is the efficient order, because it can then be applied to a known population rather than used to filter one.
Primary instruments only. Each is named in full so the reference remains traceable even if a link moves.
Yes, where they are contractual arrangements for the provision of ICT services. The intragroup character is recorded as an attribute; it is not a basis for exclusion. Group shared-service entities are among the most commonly missed entries.
A one-off licence with no ongoing provision is the strongest case for being outside, but it is rare in practice: maintenance, updates, hosting or support all constitute ongoing provision. Assess the arrangement as delivered rather than as titled, and record the reasoning.
No. The obligation covers all contractual arrangements for ICT services. Criticality determines the depth of documentation required, particularly for the supply chain and the assessments, not whether an arrangement is included.
Record the arrangement. The register describes the arrangements in force, and an unlocatable contract is a contract-management issue to escalate rather than a reason to omit a live dependency from a supervisory dataset.
REGREP is an independent software provider. This record explains a reporting framework in plain language and is not legal, tax or regulatory advice. Confirm scope, thresholds and submission dates with your competent authority before you file.
More on this framework, and the module that produces the filing.
The fifteen templates and a build sequence that avoids rework.
Read the guide →Turning a scoped population into linked template rows.
Read the guide →Assemble, validate and export the report package.
See the module →Load your arrangement inventory and let the module hold the scope decisions, the keys and the coded lists across periods.