What's new

Building a plan that would actually hold

Business continuity is a loop, not a document. PumaBCP follows the ISO 22301 / NIST SP 800-34 cycle, and each step below lands in a specific view.

• 1 · Start with the impact, not the inventory — in Workflows, write down the processes the business cannot lose and how long it could survive without each. Rank by impact over time, not by how loud the owner is. Everything downstream depends on getting this order right.
• 2 · Set MTD, RTO and RPO deliberately — maximum tolerable downtime is how long the damage stays acceptable; the recovery time objective is your target inside it; the recovery point objective is how much recent data you can afford to lose. All three are business decisions, and defaulting them to whatever IT can currently manage is how plans quietly become fiction.
• 3 · Inventory what those processes run on — in Assets, with the backup state filled in honestly. "Untested" is a legitimate answer and a far more useful one than an optimistic "Verified".
• 4 · Confirm the dependencies and break them — the Dependency map opens with links already proposed; keep the true ones, run Guided mapping for the rest, then click the shared database, the sole vendor, the one person who knows the runbook. Recovery stalls at the weakest link, and simulating the failure is cheaper than discovering it.
• 5 · Exercise before you need it — run a Tabletop scenario end to end. An untested plan is a hypothesis, and it will be tested on the worst possible day whether or not you chose the date. Deeper facilitation lives in PumaTTX.
• 6 · Turn the gaps into owned actions — the exercise's Gaps and Actions steps are the output that matters. A finding with no owner and no date is a note, not a fix.
• 7 · Publish and re-run — export the recovery plan as Markdown, RTF or PDF, then put the next review in the calendar. A stale plan fails exactly when it is needed.

Going deeper

The standards are ISO 22301 (business continuity management systems) and NIST SP 800-34 (Contingency Planning Guide). Assess the threats feeding your impact analysis in PumaRisk; run the exercises in PumaTTX.

Where your plans live

Every plan, asset, dependency, backup, workflow, scenario, and history snapshot is held in this browser's sessionStorage under the pumabcp.* key prefix. Nothing is sent over the network. Closing the tab keeps your data; opening this file in a different browser, profile, or device shows an empty plan.

Backing up

Two export scopes, each with its own home:

• Full backup — the topbar ↓ icon (or ⌘S) writes every plan in one .pumapack. This is the safeguard against losing browser storage entirely — closed wrong window, cleared cookies, switched browser, lost device. Restore brings every plan back as a fresh workspace.
• Per-workspace — right-click any workspace tab (long-press on touch) for the per-plan menu. Save workspace writes a single-plan .pumapack (the format for sharing a plan with a client, or opening it in another browser). The Reporting group offers Markdown, RTF (Word/Pages/TextEdit), and PDF (system print dialog) renderings of the recovery plan suitable for leadership.

Clear all local data

Keyboard shortcuts

About PumaBCP

PumaBCP is a lightweight, portable, offline business continuity and disaster recovery planning tool that runs entirely in your browser. It covers asset inventory, dependency cascade modeling, guided tabletop exercises, and recovery plan export.

This tool is provided as-is, with no warranties or guarantees. It is not professional advice. By using it you accept full responsibility for any outcomes that result from your use.

About PumaWorx

PumaWorx is a suite of offline, single-HTML productivity apps that run entirely in your local browser. The entire suite is a personal, open source vibecoding project.