Definitions: Edit
Define how your reporting company interprets and applies the scoring options and arrangement types used throughout the register — these definitions are included in your DORA register submission.
Fields covered on this page:
If you're having issues with any of the fields mentioned on this page, see Definitions template and option consistency issues.
Standalone arrangement
Describe whether this contract is concluded independently and managed separately from other ICT service agreements.
What to enter
Explain in plain text how your entity defines and identifies a standalone arrangement internally.
Describe the characteristics that distinguish it from overarching or subsequent arrangements in your contract portfolio.
Overarching arrangement
Describe the master or framework agreement governing multiple ICT service contracts and explain how it sets the general terms for related arrangements.
What to enter
Explain in plain text how your entity defines and identifies an overarching arrangement internally.
Describe the role it plays in governing subsequent arrangements and how your entity distinguishes it from standalone contracts.
Subsequent arrangement
Describe how this contract is linked to the main ICT agreement and explain how it supplements or builds on that overarching arrangement.
What to enter
Explain in plain text how your entity defines and identifies a subsequent arrangement internally.
Describe how it relates to the overarching arrangement it sits under and what distinguishes it from standalone contracts.
Data sensitivity (LOW)
Describe the data stored by the ICT provider and explain why its compromise would cause minor business, operational, financial, or regulatory consequences for the reporting company.
What to enter
Define what Low data sensitivity means for your entity.
Describe the types of data you classify at this level and the reasoning behind that classification — for example, publicly available data or operational data with no personal or financial content.
Data sensitivity (MEDIUM)
Describe the data stored by the ICT provider and explain why its compromise would cause moderate business, operational, financial, or regulatory consequences for the reporting company.
What to enter
Define what Medium data sensitivity means for your entity.
Describe the types of data you classify at this level and explain why their compromise would have a moderate impact on your operations or compliance position.
Data sensitivity (HIGH)
Describe the data stored by the ICT provider and explain why its compromise would cause severe business, operational, financial, or regulatory consequences for the reporting company.
What to enter
Define what High data sensitivity means for your entity.
Describe the types of data you classify at this level — for example, personal data, financial records, or confidential operational data — and explain why their compromise would have a severe impact.
Function Discontinuation Impact (LOW)
Describe the outsourced ICT function and explain why discontinuing it would cause only minor operational, financial, or regulatory impact for the reporting company.
What to enter
Define what a Low discontinuation impact means for your entity in the context of this function.
Describe the operational characteristics that make this function's disruption manageable and limited in scope.
Function Discontinuation Impact (MEDIUM)
Describe the outsourced ICT function and explain why discontinuing it would cause moderate operational, financial, or regulatory impact for the reporting company.
What to enter
Define what a Medium discontinuation impact means for your entity in the context of this function.
Describe the operational characteristics that make this function's disruption significant but not severe.
Function Discontinuation Impact (HIGH)
Describe the outsourced ICT function and explain why discontinuing it would cause severe operational, financial, or regulatory impact for the reporting company.
What to enter
Define what a High discontinuation impact means for your entity in the context of this function.
Describe the operational characteristics that make this function's disruption critical to your entity's continuity or compliance.
⇒
The following four fields define how your entity applies the substitutability scale — used in the Provider replaceability difficulty and Service replaceability fields to assess how easily a provider or service can be replaced.
Reintegration possibility (Not substitutable)
Describe why the outsourced ICT function cannot be reintegrated or replaced and explain the operational, technical, contractual, or resource constraints preventing substitution.
What to enter
Define what Not substitutable means for your entity.
Describe the specific constraints — for example, exclusive technology, regulatory restrictions, or critical dependencies — that make replacement impossible or not feasible.
Reintegration possibility (High complexity)
Describe the steps required to replace this ICT function and explain the operational, technical, financial, or contractual factors creating severe complexity for the reporting company.
What to enter
Define what High complexity substitutability means for your entity.
Describe the factors that make replacement severely difficult — for example, long migration timelines, significant cost, or deep integration with core systems.
Reintegration possibility (Medium complexity)
Describe the steps required to replace this ICT function and explain the operational, technical, financial, or contractual factors creating moderate complexity for the reporting company.
What to enter
Define what Medium complexity substitutability means for your entity.
Describe the factors that make replacement moderately challenging — for example, significant effort required but achievable within a reasonable timeframe.
Reintegration possibility (Low complexity)
Describe the steps required to replace this ICT function and explain the operational, technical, financial, or contractual factors creating minimal complexity for the reporting company.
What to enter
Define what Low complexity substitutability means for your entity.
Describe why replacement is achievable with minimal disruption — for example, standard market alternatives are available and migration is straightforward.
⇒
The following three fields define how your entity applies the reintegration scale — used in the Function reintegration possibility and ICT service reintegration possibility fields to assess how difficult it would be to bring a function or service back in-house or migrate to a substitute.
Reintegration possibility (LOW)
Describe the factors making reintegration or replacement easy and explain why the operational, technical, financial, or contractual challenges are minimal for the reporting company.
What to enter
Define what Low reintegration difficulty means for your entity.
Describe the characteristics of functions or services at this level — for example, standard market alternatives are available, migration timelines are short, and no significant dependencies exist.
Reintegration possibility (MEDIUM)
Describe the factors making reintegration or replacement difficult and explain the significant operational, technical, financial, or contractual challenges for the reporting company.
What to enter
Define what Medium reintegration difficulty means for your entity.
Describe the characteristics of functions or services at this level — for example, alternatives exist but require significant effort, cost, or time to implement.
Reintegration possibility (HIGH)
Describe the factors making reintegration or replacement highly complex and explain the significant operational, technical, financial, or contractual challenges for the reporting company.
What to enter
Define what High reintegration difficulty means for your entity.
Describe the characteristics of functions or services at this level — for example, no ready alternatives exist, migration would require extensive resources, or core dependencies make reintegration highly disruptive.
ICT Services Discontinuation Impact (LOW)
Describe the ICT services concerned and explain why discontinuing them would cause only minor operational, financial, regulatory, or business continuity impact for the reporting company.
What to enter
Define what a Low discontinuation impact means for your entity in the context of ICT services.
Describe the service characteristics that make disruption manageable and limited in scope.
ICT Services Discontinuation Impact (MEDIUM)
Describe the ICT services concerned and explain why discontinuing them would cause moderate operational, financial, regulatory, or business continuity impact for the reporting company.
What to enter
Define what a Medium discontinuation impact means for your entity in the context of ICT services.
Describe the service characteristics that make disruption significant but not severe.
ICT Services Discontinuation Impact (HIGH)
Describe the ICT services concerned and explain why discontinuing them would cause severe operational, financial, regulatory, or business continuity impact for the reporting company.
What to enter
Define what a High discontinuation impact means for your entity in the context of ICT services.
Describe the service characteristics that make disruption critical to your entity's continuity, financial stability, or regulatory compliance.