Business Continuity & Disaster Recovery
A disaster recovery plan that only exists in one person's head isn't a plan — it's a liability. I write, test, and maintain the documentation that lets an organization actually recover instead of improvising under pressure. When no DR plan exists yet, writing one from scratch — not reviewing someone else's template — is where the work starts. I've done exactly that: writing a credit union's first disaster recovery plan as part of modernizing infrastructure that had never been formally documented.
What this covers
DR plan authorship
Writing the plan itself when none exists, not just auditing one that's already there.
Business impact analysis
Identifying what actually needs to recover first, and how fast, before writing a single recovery step.
Recovery testing & tabletop exercises
A plan nobody has tested is a plan nobody trusts when it matters.
Documentation that survives turnover
Recovery steps written so someone other than the person who wrote them can execute them.
Alignment with infrastructure reality
A DR plan has to match what's actually running today, not what the architecture diagram says.
Who this is for
Organizations with infrastructure that's grown faster than its documentation, where recovery from a major outage currently depends on one or two people's institutional knowledge rather than a written, tested plan. Especially relevant ahead of an audit, a cyber insurance renewal, or after a near-miss that made the gap obvious.
Have this problem right now?
I take on a limited number of clients at a time so every engagement gets real attention. Let's talk about scope, cadence, and fit.
Book an introductory call