Insight · 1 Aug 2025
DORA Subcontracting Changes: Decide Before the Notice Period Ends
Since 22 July 2025, Delegated Regulation (EU) 2025/532 has set how material subcontracting changes reach a financial entity. Check that each notice reaches someone who can approve or object before the notice period ends.
DORAThird-party oversightThird-party riskeuFinancial Services and Insurance
Since 22 July 2025, Commission Delegated Regulation (EU) 2025/532 under the Digital Operational Resilience Act (DORA) has set what a financial entity must check before it signs a contract that lets an information and communication technologyThe systems, networks and digital services an organisation relies on to process and exchange information. DORA builds its financial-sector requirements around ICT risk, ICT services and ICT third-party service providers. (ICT) provider subcontract a service supporting a critical or important functionA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.. It also sets what happens when the provider later wants to change those arrangements. The process has three steps. Your contract must require the provider to tell you about a material change well in time. You then have a reasonable notice period to approve or object. The provider waits until you approve or the period ends without an objection. This only protects you if the notice reaches someone who can decide before the period runs out.
Which Arrangements Are in Scope
The regulation covers ICT services that support critical or important functions, or material parts of them, where the contract allows the provider to subcontract. The regulation’s recitals say group companies count as subcontractors too, and that you should focus on the subcontractors that underpin the service, including any whose disruption would impair its security or continuity, as recorded in your register of informationThe register that financial entities must maintain and update under DORA Article 28(3), covering all contractual arrangements for ICT services provided by ICT third-party service providers. Competent authorities collect the registers, and the ESAs use them to designate critical providers.. Where the regulation applies on a consolidated or sub-consolidated basis, the parent undertaking that prepares the consolidated accounts must make sure the subcontracting conditions are applied consistently in every financial entity in the group.
A supplier being large or commercially important does not bring a service into scope. What matters is whether the specific service supports a critical or important function. Nor does the regulation make your suppliers directly supervised, or require the same approval for every minor administrative change. Keep ordinary procurement changes separate from material changes to in-scope subcontracting.
What the Regulation Requires
Before you sign. You must decide whether the provider may subcontract the service at all. You may sign only once you have assessed that all ten conditions in Article 3(1) are met. Among them:
- the provider can identify every subcontractor that supports the critical or important function, tell you who they are and give you the information you need;
- each subcontractor grants you and the competent and resolution authorities the same access and inspection rights as the provider does;
- you have the resources and expertise to monitor the subcontracted risk;
- you have assessed the effect of a subcontractor failing, the risks of its location, your concentration risk and any obstacles to audit.
You must repeat your own assessments in points (f) to (j) at regular intervals. They cover your monitoring capacity, the effect of a subcontractor failing, location, concentration and obstacles to audit. Take account of changes in your business functions, ICT threats, concentration risk and geopolitical risk. Relying on the provider’s own assessment of its subcontractors does not reduce your responsibility.
In the contract. Article 4(1) requires the contract to name the services that may be subcontracted and the conditions. Among other things, it must state:
- that the provider stays responsible for what its subcontractors deliver and monitors them;
- what the provider must monitor and report to you about its subcontractors;
- where the subcontractor processes or stores data, where relevant;
- that continuity is ensured down the chain;
- that business contingency and security requirements pass down to the subcontractors;
- that subcontractors give you and the competent and resolution authorities the same access, inspection and audit rights as the provider does;
- that the provider must notify you of any material change to its subcontracting arrangements;
- that you have a right to terminate in the cases set out below.
When a change comes. Article 5 sets the sequence:
- The contract must require the provider to inform you of an intended material change well in time for you to assess two things: the effect on the risks you face, and whether the change could affect its ability to meet its contractual obligations to you.
- The contract sets a reasonable notice period for you to approve or object.
- The provider may implement the change only after you approve it, or after the period ends without an objection.
- If the change exceeds your risk tolerance, you must, before the period ends, inform the provider, object and request modifications.
If the provider goes ahead anyway. Article 4(1)(l) requires the contract to give you a right to terminate in these cases, which Article 6 lists:
- the provider implements a change after you objected and asked for modifications;
- it implements a change before the notice period ends without your approval;
- it subcontracts a service the contract did not explicitly allow to be subcontracted.
DORA Article 28(7) adds its own grounds for termination. One of them covers circumstances found in monitoring that could alter how the functions are performed, including material changes that affect the arrangement.
What the Regulation Leaves to Your Contract
The regulation does not define “material change”, and it does not set a number of days. It says “well in time” and “a reasonable notice period”. Your contract has to fill both gaps. A workable contract does three things:
- It lists what the provider must treat as material. Examples are a new subcontractor for an in-scope service, a replacement of an existing subcontractor and a move of the service or the data to another country. DORA Article 30(2)(b) already requires advance notice of a change of location.
- It sets a notice period your team can use, counting the time needed to ask questions and escalate.
- It names the address a notice must go to, so it does not land in a supplier portal no one watches.
Make the Notice Reach a Decision-Maker
Test the route with a realistic case. A payment platform moves part of its processing to a new subcontractor. Procurement receives a portal alert, the relationship manager is on leave and the security team learns about the change after the notice period has closed.
The weakness there is ownership, not the clause. When a notice arrives:
- open a case;
- link it to the contract and the function the service supports;
- assign an accountable service owner, with a deputy who has the same access and authority to escalate;
- record when the notice was received, the proposed implementation date and the last day to respond, as the contract defines it.
If the contract is unclear about when the period starts, ask legal counsel rather than letting an internal ticket decide. Nothing in the regulation says that sending the provider questions pauses the period. Agree any extension with the provider in writing.
Ask for the Facts That Could Change the Answer
Article 5 asks you to assess two things: your risks, and the provider’s ability to keep its commitments. Article 1 lists the complexity and risk factors you must take into account when applying the regulation, and they make a useful checklist here. Use them as a short comparison of the current arrangement and the proposed one, not a full onboarding questionnaire:
- Which service, or part of it, moves to whom?
- Where will the service be delivered from, and where will the data be processed and stored?
- Is the new subcontractor in your group? Is it supervised, in the EU or elsewhere?
- Will the provider now rely on one or a few subcontractors for the service? If several of your providers end up depending on the same subcontractor, bring in whoever owns concentration risk under DORA Article 29.
- Would the change make it harder to move the service to another provider?
- What happens to continuity and availability if the new subcontractor fails?
Ask for evidence in proportion to the uncertainty. A diagram, the subcontractor’s name and an explanation of the affected control may settle one case. Another may need assurance reports or a continuity exercise. An unanswered question is not evidence that the change is safe.
Approve, Object or Escalate
Write the decision in terms of what it means for the service. “Security approved” tells the next reviewer nothing. “Approved: recovery design and access boundaries stay within what we assessed and accepted at onboarding, subject to the listed checks” gives them something to verify.
If the change exceeds your risk tolerance, object and request modifications in writing before the period ends, and keep proof that the provider received it. Then make sure the business owner has a fallback if the disagreement is not resolved. For services supporting critical or important functions, DORA Article 28(8) requires documented exit plans that are sufficiently tested and reviewed periodically. DORA Article 30(3)(f) requires the contract to provide an adequate transition period.
A One-Page Decision Record
- Contract and function: the arrangement, the function it supports and why this change is in scope.
- Change: the current and proposed arrangements in plain language.
- Timing: when the notice arrived, the last day to respond and the proposed implementation date.
- Evidence: what supports the assessment and what is still unanswered.
- Decision: the risk tolerance applied, the consequence for the service and the person accountable.
- Response: the approval or objection sent, with proof of delivery.
- Follow-up: checks after implementation, contract records and any continuity action.
Close the Gaps in Existing Contracts
Contracts signed before 22 July 2025 may lack these clauses. Article 4(2) requires the changes needed to comply to be made in a timely manner and as soon as possible, and you must document the planned timeline. It sets no fixed number of days. For each contract, record:
- the missing provision;
- who is negotiating it;
- when you expect to finish;
- how you handle notices from that provider in the meantime.
Keep the two tracks apart. Renegotiating wording can take months, but a notice that arrives tomorrow still needs an owner.
Start with One Notice
Take a recent supplier change and replay it with compliance, the service owner and legal counsel. Can the team reach and send a decision within the notice period the contract actually gives? The answer shows where the route breaks, and that is a small, well-defined scope to fix first.
If you want that route and your subcontracting clauses audited independently, see our DORA Compliance Audit.
