DORA’s register of information and an executable exit test solve different problems. Treating either one as a substitute for the other creates false confidence.
Commission Implementing Regulation (EU) 2024/2956 defines reporting templates for contractual arrangements, ICT services, providers and the functions they support. Its templates include fields for substitutability, the existence of an exit plan, reintegration difficulty, the impact of discontinuing a service and identified alternative providers.
The register is a governed map
The register helps an organisation and its supervisors understand who provides which ICT services, where those arrangements sit, and which functions may be exposed. That information depends on contracts, legal entities, provider records and business ownership. A cloud inventory cannot infer all of it safely.
An exit test is execution evidence
A technical proof begins lower down: a reviewed workload boundary, its dependencies, a target design and observable behaviour that must survive. It can then record the exact package and checks used, what executed, what passed, and which caveats remain.
Join them later, do not burden setup now
A future report can map a customer’s approved legal and business identifiers onto existing technical evidence. That should be an explicit, optional workflow for customers who need it—not a questionnaire that blocks every team from discovering and testing a workload.
Collect technical facts once. Ask for regulatory context only when someone chooses the regulatory output.
PortabilityLabs does not currently produce or submit a DORA register or readiness pack. Its current role is to preserve evidence that may later support a governed mapping prepared with appropriate risk, legal and compliance ownership.