Most organizations hire a disaster recovery consultant to answer one question: if our technology fails, how fast can we get the business back? A surprising number of them end up with an answer that happens to require a specific backup platform.
That is not always wrong. But it is the first thing to check.
The short answer: a disaster recovery consultant works with your business leaders to decide how fast each critical service has to come back after a technology failure, then builds and tests the plan that gets it there. Choose one who starts with the business, isn’t paid to sell you a platform, and leaves your team able to run recovery without them.
A disclosure before we start: Bryghtpath provides IT disaster recovery consulting, and we work tool-agnostic, in whatever platforms our clients already use, so we have a point of view on that first question. The seven questions below apply to any firm you evaluate, including us.
First, Make Sure You Are Searching for the Right Kind of Consultant
“Disaster recovery consultant” means two very different things:
| Community disaster recovery | IT disaster recovery | |
| Typical client | Cities, counties, states, agencies after a natural disaster | Organizations whose technology must come back after an outage, cyberattack, or site loss |
| Core work | FEMA grants, reimbursement, rebuilding | Recovery strategy, tiering, plans, testing, recovery sequencing |
| Success looks like | Funding recovered, community rebuilt | Critical services restored within the time the business can tolerate |
Many of the top search results serve the first group. If you are a CIO, CISO, or IT infrastructure leader, you want the second.
Seven Questions to Ask a Disaster Recovery Consultant
1. Do you start with the business or the infrastructure?
A good answer: they start with the business services that matter most, using your Business Impact Analysis (BIA), and work down to the systems that support them.
A red flag: they start with a server inventory or a platform demo.
Recovery priorities come from the business. An infrastructure-first plan recovers servers efficiently in the wrong order.
2. How are you paid, and what do you resell?
Many disaster recovery consulting services are delivered by the services teams of backup, replication, or disaster recovery as a service (DRaaS) vendors. Their people can be excellent, and their recommendations will usually include their platform.
Ask directly: do you resell, receive referral fees from, or deliver services for any technology vendor? Neither answer disqualifies a firm. Not knowing the answer is the risk.
3. How will you reconcile what the business needs with what IT can deliver?
The business says it needs payroll back in four hours. The infrastructure can restore it in three days. That gap between the recovery time objective (RTO) the business needs and the recovery time IT can actually achieve is the most important finding in any disaster recovery engagement.
A good answer: a consultant who measures both, shows the gap service by service, and gives you options to close it, with costs, so executives can decide what to fund and what to accept.
A red flag: RTOs copied from a template, or tiers assigned without anyone measuring actual recovery times.
4. Will the plan tell us what to recover first?
A disaster recovery plan that lists systems and backup locations is an inventory. A useful plan defines the recovery order: the foundation first (identity, network, security tooling), then the services that keep the company running, then everything else, with dependencies mapped and durations estimated. (We wrote about this in detail in what most ransomware recovery plans are missing.)
5. How do you handle cyber recovery, not just site failover?
Traditional disaster recovery assumed a failed data center and a clean copy somewhere else. Ransomware breaks that assumption: the backups may be compromised, and the clean restore point may be days old.
A good answer: a plan that covers both a site or cloud outage and a destructive cyberattack, including how to validate clean restore points and who decides how much data loss is acceptable.
A red flag: “Your replication covers that.”
6. How will we know it works?
Ask what testing looks like after the plan is written: tabletop exercises for the decisions, technical recovery tests for the systems, and an improvement plan for what fails.
A good answer: a testing cycle with measured recovery times and an after action report that closes gaps. (Here is how to turn exercise findings into an improvement plan.)
A red flag: “We’ll hand you a test plan.”
7. What will my team own when you leave?
The engagement should end with governance, owners, a maintenance cycle, and people who can run the next test without the consultant in the room.
A good answer: defined ownership, training, and a maturity baseline you can measure against next year.
A red flag: an open-ended dependency on the firm, or a plan only the consultant understands.
Red Flags in a Disaster Recovery Proposal
- The recommendation is a product. Strategy should come before platforms, and the platform should be a choice among options.
- No mention of the business. If the proposal never mentions your BIA or business services, it is an infrastructure project.
- RTOs without measurement. Targets nobody has tested are wishes.
- Ransomware treated as a footnote. Today it is the most likely reason you will invoke the plan.
- No testing in scope. A plan that is never tested has not been proven to work.
What Good Looks Like
One health insurer came to us with no working IT disaster recovery program. Their chief information security officer described the result this way: “Bryghtpath helped us cut through the noise and stand up an ITDR program that actually works. We went from zero to tested in under a year.”
“Tested” is the word that matters in that sentence. A disaster recovery program is only real once it has been tested.
Where to Start
If you are not sure what you need yet, start with a baseline. A business continuity maturity assessment scores your IT disaster recovery program against ISO 27031, NIST SP 800-53, and the standards you answer to, and tells you which gaps matter first. ResiliencyPulse lets your team score itself, starting at $749.99 a year. Our facilitated Resiliency Diagnosis® starts in the mid five figures and adds the outside view a board or regulator will expect.
If your team does not have the time or hands to run the program after it is built, Resilience as a Service runs IT disaster recovery alongside business continuity and crisis management as one program.
The right disaster recovery consultant does not sell you recovery. They prove you have it.
Keep Going
A few ways to go deeper if this was useful.
- Read more. Resilience, crisis management, and continuity writing at Bryghtpath Insights, or the structured Ultimate Guide to Business Continuity.
- See how we approach IT disaster recovery. Our IT disaster recovery consulting starts with the business, works in the tools you already have, and ends with a tested recovery capability.
- Get a maturity score. Our Resiliency Diagnosis® is a standards-based review that produces a maturity score and a prioritized roadmap.
- Talk to us. Set up a call to think through your disaster recovery program with us.





