YUDU Sentinel Blog

DORA Incident Communication Guide for Financial Teams

Written by Edward Jones | 19 Nov 2026

What communication tools help meet DORA incident management requirements?

The most useful DORA incident management communication tools are two-way alerts, an independent crisis channel, secure chat and conferencing, accessible response plans and a time-stamped decision log. Together, they help financial firms reach the right people, assess the impact on clients, escalate major incidents and assemble the evidence needed for incident reporting. The reporting lead then submits the approved notification through the competent authority’s designated channel.

Consider a bank whose payment queue stops clearing just as staff lose access to Teams and email. Operations can see delayed transactions. The service provider is investigating. The contact centre is already taking calls. How quickly can those three teams agree what clients should do, and how will the bank establish when it first understood the scale of the disruption?

What does DORA require teams to communicate?

The EU’s Digital Operational Resilience Act requires in-scope financial entities to record ICT-related incidents and operate a process for detecting, managing and notifying them. Article 17 requires firms to assign roles, establish internal escalation procedures and report at least major incidents to relevant senior management. The management body must be informed about those incidents, their impact, the response and the additional controls to be established.

Article 14 covers crisis communication plans and the roles of staff handling the response and external disclosures, subject to the applicable ICT risk framework. Article 19 requires firms to report major ICT-related incidents to their competent authority. If a major incident affects clients’ financial interests, the firm must also tell those clients about the incident and the measures taken to mitigate its adverse effects, as soon as it becomes aware of that impact. Give client communication its own owner so it can proceed alongside the regulatory filing. Read DORA Articles 14 and 17–19.

Which capabilities support each stage of the response?

1. Reach the people who can assess the impact

Use targeted, two-way alerts across SMS, voice and in-app messaging. Build groups around the service at risk, such as payments, trading or claims, and include an on-call deputy for each decision-making role. Ask each recipient to confirm whether they can take the role. A delivery receipt alone leaves the incident lead guessing whether anyone is actually investigating.

2. Coordinate outside the affected systems

An out-of-band communications platform gives responders a place to work if corporate email, Teams or the usual sign-in service fails or becomes unsafe to use. Test whether a duty manager can sign in from a separate device, find the provider’s emergency contact and open a restricted crisis room. Keep the initial SMS brief. Put transaction details, investigation notes and decisions in the access-controlled workspace.

3. Give compliance the facts to classify the incident

Use a shared impact record with a named owner and a time against each update. Ask operations for service downtime and transaction volumes, client services for affected customers and markets, and security for evidence of data loss or unauthorised access. Record the source of each figure, mark estimates and revisit them as evidence improves. Compliance can then apply the classification criteria and materiality thresholds, including the rules on recurring incidents, and record when and why the firm classified the incident as major. See the incident classification standards.

4. Give leadership, clients and staff the information each needs

A management briefing should state which service has failed, the known client impact, the decision required and when the next update is due. A client notice should explain what has happened, what the firm is doing and any action the client should take. For a payment delay, an especially important question is whether clients should resubmit a transaction. Give contact-centre staff the approved wording at the same time so a caller receives the same advice as someone reading the service update.

5. Preserve the evidence behind each report

Keep an accessible copy of the reporting template, authority contact details and submission instructions. Assign a reporting lead and deputy. In the incident record, link each approved report to its supporting figures, approval time and submission receipt. A time-stamped chat can show when someone raised a concern. A decision log should also identify who acted on it and why.

How quickly must a financial firm report a major ICT-related incident?

Record both the time the firm became aware of the ICT-related incident and the time it classified it as major. They start different clocks.

  • Initial notification. Submit as early as possible, within four hours of major classification and no later than 24 hours after awareness. If the firm first classifies the incident as major after those 24 hours, submit within four hours of classification.
  • Intermediate report. Submit within 72 hours of the initial notification, even if nothing has changed. Provide updates when the status or handling changes significantly or the authority requests one. Submit an updated intermediate report without undue delay and in any case once regular activities have recovered.
  • Final report. Submit within one month of the intermediate report or the most recent updated intermediate report. Cover root cause, resolution and actual impact figures as they become available.

If the firm cannot meet a deadline, it must tell the authority without undue delay, by that deadline, and explain why. A limited weekend and bank-holiday extension exists. For initial and intermediate filings it excludes credit institutions, central counterparties, trading venue operators and other financial entities identified as essential or important under NIS2. Build the applicable calendar into the playbook. Check Article 5 of the reporting time-limit regulation.

For example, if a bank becomes aware of an ICT incident at 08:00 on Monday and classifies it as major at 10:30, its initial notification is due as early as possible and by 14:30 that day. If the bank submits at noon, the 72-hour deadline falls at noon on Thursday. Recording the actual filing time gives the next shift the correct deadline.

Use the standard reporting forms and the secure electronic channel provided by the competent authority. If that channel is unavailable, use the other secure means agreed with the authority or established in consultation with it. Keep those fallback details somewhere the reporting lead can reach during an outage. See the standard forms and submission procedures.

How YUDU Sentinel supports incident response communication

YUDU Sentinel gives financial teams an independent, single-tenant environment for crisis communication.

  • With Level 1 – Out-of-Band Communication, the duty manager can send targeted alerts, receive replies and use the tamper-evident audit log to establish who responded. In the payments example, that lets the incident lead see whether payments operations and client services have both joined the response.

  • Level 2 – Out-of-Band Collaboration adds secure chat, video crisis rooms and offline access to response documents. Operations and the provider liaison can establish the facts while senior leaders review the client impact in a restricted Space.

  • Level 3 – Service Continuity adds synchronisation of selected operational documents and data, so teams can consult the last successfully synchronised information when the source system is unavailable. The firm’s reporting lead retains ownership of classification, approval and regulatory submission.

Explore Sentinel’s three levels of operational resilience.

Can your team complete the first notification without corporate email?

Run the payments scenario with Teams, email and corporate single sign-on unavailable for the exercise. Give the provider liaison a revised estimate of affected transactions halfway through. Ask the duty manager to reach a deputy, compliance to record whether that estimate changes classification, and client services to update its advice.

For the debrief, ask the next shift to reconstruct four things from the records alone: when the firm became aware, when it classified the incident, what clients were told and when the next report is due. Any answer that depends on finding the person who ran the call identifies a specific gap in the firm’s incident response communication and regulatory compliance arrangements.