business · local-first tool
Keep Essential Business Contacts Beside the First Recovery Steps
A response plan needs an owner, a supplier backup, and a current contact—not just a file named 'emergency'.
Build an index of critical process labels, responsible roles, backup contacts, and review dates for an internal plan.
What changes the result: your business's essential processes, continuity priorities, and reviewed contacts.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Count short labels that lack a source, location, review date, or confirmed status, depending on the row type. The tool stores pointers, not the underlying documents, meter accounts, access codes, or proof that a record is current.
Question to keep open: Should recovery planning begin with the most likely interruption or the function that would be hardest to restore?
Boundary: This card is not a tested continuity plan, security assessment, or emergency-response service. Store sensitive contact details securely and follow official emergency guidance.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.