What Is a DR Command Centre? A Practical Guide for Banks and Data Centres

Ask ten operational resilience leads what a "DR command centre" is and you'll get ten different answers — half of them describing a physical room with whiteboards, the other half describing a WhatsApp group with a senior name on it.

Both are wrong. A DR command centre is neither a place nor a chat group. It's the operational system that coordinates a disaster recovery exercise or real incident — where decisions get made, tasks get assigned, status gets tracked, evidence gets captured, and the regulator-ready record gets built in real time.

This post explains what a proper command centre actually does, why most banks and data centres don't really have one (even when they think they do), and what to look for when you're building or selecting one.

The Working Definition

A DR command centre is the single source of truth during a DR exercise or incident. At any moment, anyone with appropriate access should be able to see:

• What exercise/incident is in progress
• Which runbook is being executed
• Which tasks are complete, in progress, blocked, or not yet started
• Who owns each task and when it's due
• What SLAs are at risk
• Which decisions have been made and by whom
• What evidence (screenshots, logs, approvals, sign-offs) has been captured
• Where the gaps are, in real time

If your "command centre" can't surface those answers within seconds, you don't have one. You have people in a Teams call.

Why This Matters in Practice

The difference between a real command centre and an ad-hoc one shows up in three moments:

During the exercise

In a real exercise, dozens of tasks are happening in parallel across IT, risk, business teams, and external vendors. Without structured tracking, the exercise lead is guessing about what's done, what's stuck, and where the SLA risk is. With a command centre, they can see the full picture on one dashboard.

When something goes wrong

In a real incident — not a planned exercise — coordination matters even more. People are stressed, communications are noisy, and decisions need to be traceable. A command centre captures who decided what at what time, with what information. After the incident, the post-mortem is based on data, not on reconstructed memory.

When the regulator asks

BNM, MAS, APRA, and other APAC regulators have all raised the bar on operational resilience evidence. They expect to see structured exercise records, documented decision logs, evidence captured at the task level, and continuous-improvement loops. "We had a WhatsApp group and took some screenshots" doesn't pass that bar anymore.

The Components of a Real Command Centre

A DR command centre platform — not a room, not a chat group — should have these capabilities:

1. Live exercise dashboard

A real-time view of the active exercise: which scenario is running, what stage it's in, how many tasks are complete vs. pending vs. blocked, and overall progress against the planned timeline. The exercise lead should be able to glance at this and make decisions.

2. Task tracking with ownership and SLA

Every task has an owner, a planned start time, a planned duration, and dependencies. When a task is in progress, it shows who's working on it and how long they've been at it. When a task is blocked, the blocker is visible. SLA breaches surface automatically.

3. Decision log

When the command centre lead makes a decision (switch to fallback site, escalate to executive committee, abandon the exercise scenario, etc.), it's logged with timestamp, decision-maker, and rationale. This is the part of the record regulators and post-mortems care about most.

4. Evidence capture at the task level

Screenshots, logs, approval emails, signed-off checklists — all attached to the relevant task in real time. Not assembled after the exercise. Not screenshotted into a shared drive and titled "Misc evidence." Attached to the task, timestamped, immutable.

5. Multi-team coordination

DR exercises span IT, risk, compliance, business teams, and often external vendors. The command centre needs to give all of them appropriate access — view-only for some, task ownership for others, scoped access for vendors. WhatsApp groups don't have this notion.

6. Communications channel integration

The command centre should be the source of structured updates; chat tools (Teams, WhatsApp) remain useful for free-form discussion. But the record lives in the command centre, not in the chat thread.

7. Post-exercise report generation

When the exercise ends, the command centre should produce a report covering timeline, tasks completed, SLA performance, gaps identified, decisions made, and evidence attached — in minutes, not days. Without this, post-exercise reviews stall because nobody wants to spend a week assembling slides.

Why Most Organisations Don't Really Have One

Most banks and data centres think they have a command centre because they have:

• A physical war room with a big screen
• A Microsoft Teams call running during the exercise
• A WhatsApp group with senior names on it
• A Word document called "DR Runbook v17_final_FINAL.docx"
• A SharePoint folder where someone is supposed to upload evidence

None of those are a command centre. They're props around the absence of one.

The test: a week after the exercise, can you produce a complete, timestamped record of what happened — including SLA performance, decisions made, evidence captured, and gaps identified — in under an hour? If yes, you have a command centre. If you'd need to spend three days reconstructing it from screenshots, emails, and people's memories, you don't.

The Cost of Not Having One

Organisations operating without a real command centre pay for it in three ways:

Reconstruction cost after every exercise. The post-exercise report becomes a multi-week project. Senior people spend hours reconstructing what happened from chat logs and emails. Findings get diluted in the noise.

Regulator audit pain. When BNM or another regulator asks for exercise evidence weeks later, the response is slow, incomplete, and visibly reconstructed. That triggers follow-up questions and an erosion of regulator confidence — which compounds.

Worse real-incident response. Teams that exercise on ad-hoc tools also respond to real incidents on ad-hoc tools. The coordination quality during real outages mirrors the coordination quality during exercises. If exercises are chaotic, real incidents will be worse.

What "Good" Looks Like in Practice

In organisations with a mature command centre:

• Exercises are scheduled in the platform with scope, scenarios, runbooks, and participants pre-loaded
• On exercise day, the dashboard goes live; teams execute tasks; evidence flows in automatically
• The command centre lead spots blockers in real time and makes decisions on the spot, logged automatically
• SLAs are tracked and breaches flagged within seconds
• Post-exercise reports are generated in 10 minutes from the live data — not assembled over days
• Findings flow into a remediation tracker that the next exercise verifies
• Regulator audits are answered with structured exports in hours, not weeks

The maturity gap between organisations that have this and organisations that don't is substantial — and increasingly noticed by regulators.

How ResiliencePro Fits

ResiliencePro is BlueAura's operational resilience platform with a purpose-built DR command centre at its core. The platform handles:

• Digital DR runbooks with versioning and approvals
• Exercise scheduling and execution
• Real-time command centre dashboard
• Task tracking with SLA monitoring and breach alerts
• Decision log capture with timestamps
• Evidence attachment at the task level
• Multi-team coordination including external vendors
• One-click compliance reports for BNM, MAS, APRA, and other regulators

It's used by banks and data centre operators across Malaysia and APAC. For banks specifically, see how it addresses BNM operational resilience requirements. For data centres, see how it handles multi-site failover coordination.

You can visit ResiliencePro directly, or contact us to walk through how it would fit into your existing exercise program.

The Bottom Line

If your organisation runs DR exercises but doesn't have a structured command centre, you're investing significant time and money into a process that doesn't produce the evidence, learning, or operational readiness it should. The exercises that matter — for regulator audits, for real-incident response, for continuous improvement — depend on the command centre being a real system, not a room or a chat group.

Banks and data centres that operationalise the command centre as a platform produce better exercises, better post-mortems, better audit responses, and ultimately better real-incident outcomes. The ones that don't keep paying the reconstruction tax, exercise after exercise.

If you've been thinking about upgrading your DR exercise program, building the command centre properly is where to start. Everything else follows from there.