Nominations now open — Submit before 15 December 2026 · Free to enterSubmit Now

DORA Register of Information Becomes a Board-Level Legal Record

★
Editorial Team
DATENov 20, 2026
DORA Register of Information Becomes a Board-Level Legal Record

The Digital Operational Resilience Act is usually discussed in the language of operational resilience: ICT risk management, incident reporting, testing and third-party oversight. That framing is accurate, but it understates one of DORA’s more demanding legal consequences. The register of information required for ICT third-party arrangements is not an administrative inventory. It is a regulated record that supervisors, auditors and boards will use to test whether an organisation can tell a coherent story about its dependencies.

For legal teams, the risk is less about producing a spreadsheet than about whether the register, the underlying contracts and actual service delivery reconcile. A register that exists but cannot be explained, evidenced or updated is a control weakness. A register that contradicts the contracts it describes is worse: it becomes evidence that the organisation does not know its own arrangements.

From inventory to regulated record

DORA requires financial entities to maintain a register of information covering contractual arrangements for ICT services provided by third-party providers. The register captures details that legal, procurement and technology functions each hold in part: the provider, the service, the legal entity receiving it, the jurisdictions involved, data locations, subcontracting chains, contract terms, audit rights, incident notification and exit arrangements.

Treated as a data-entry task, the register will be incomplete, stale or inconsistent. Treated as a regulated record, it becomes something different: a structured account of the organisation’s third-party legal and operational exposure. That distinction matters because supervisors and auditors are unlikely to accept a register at face value. They will ask how entries were derived, who confirmed them and whether the underlying contracts support them.

The register is therefore a legal artefact. It records obligations, dependencies and rights. It should be maintained with the same discipline as a contract repository or a regulatory filing, not as a one-off exercise completed before a deadline.

The reconciliation test

The central test is reconciliation. Three records need to tell the same story: the register, the contracts and real service delivery. If the register describes a service differently from the contract, the discrepancy needs an explanation. If the contract grants audit rights but the register does not reflect them, the register is inaccurate. If a provider subcontracts part of a critical function and the register omits the subcontractor, the omission is a control failure.

Common gaps tend to cluster around a few areas. Service descriptions may be too broad to identify what is actually provided. Data locations may be recorded at a group level rather than at the level of the legal entity or branch receiving the service. Subcontracting arrangements may be disclosed in procurement files but not carried into the register. Termination and exit assistance clauses may exist in the contract but be absent from the fields used for dependency and exit planning. Incident notification terms may be recorded inconsistently across similar contracts.

Supervisors and auditors will look across legal entities, branches and providers for unexplained inconsistencies. A single mismatch may be a data error. A pattern of mismatches suggests that the organisation lacks a reliable process for keeping the register aligned with its contracts and operations. That is why legal teams should map contract clauses to register entries and treat contract amendments, renewals and service changes as triggers for review.

Board reporting and decision records

DORA places ICT risk oversight with the management body. The register should therefore feed board-level reporting on concentration, dependency and exit risk. Directors are not expected to inspect every row. They are expected to receive assurance that the register is complete, current and reconciled, and to understand where the organisation’s critical dependencies sit.

Useful reporting is derived from the register rather than compiled alongside it. It might show which providers support critical or important functions, where concentration exists across legal entities, how subcontracting affects dependency, which jurisdictions and data locations are involved, and where exit plans are untested or incomplete. The purpose is not to produce a dashboard for its own sake. The purpose is to support decisions about risk appetite, contractual leverage, contingency planning and provider oversight.

Those decisions and their follow-up should be minuted. A board that receives register-derived reporting, challenges gaps and records actions creates evidence that the register is part of governance rather than a compliance deliverable. That record matters when supervisors ask how senior management exercised oversight.

Ownership, change control and attestation

Legal teams should assign clear ownership for register accuracy. Legal can own the contractual accuracy of entries; procurement can own provider and sourcing data; technology and operations can own service mapping and dependency information; compliance or risk can coordinate the process. What matters is that ownership is explicit and that no function assumes another is maintaining the authoritative record.

Change control is equally important. New providers, contract renewals, service expansions, subcontracting changes, data-location changes and terminations should trigger register updates within a defined process. Periodic attestation by contract or business owners can confirm that entries remain accurate and that no unrecorded arrangements have emerged. The evidence of those reviews should be retained.

This is how register maintenance becomes a governance control rather than a compliance data-entry task. The register is only useful as legal evidence if it is current, traceable and consistent with the documents and services it describes.

A coherent account

DORA supervision is maturing, and third-party arrangements are a central supervisory priority. The organisations that fare best will not necessarily be those with the most elaborate templates. They will be those that can produce a coherent account of their ICT third-party arrangements and show that the register, the contracts and actual delivery fit together.

For legal teams, that means treating the register as a board-level legal record. It should be owned, reconciled, reported and updated. Where it is not, the gap will not look like a formatting problem. It will look like a failure of control.