0
Critical services modeled
Active service inventory
ORGANIZATIONAL RESILIENCE INTELLIGENCEKnow what matters.
Know what matters.
Recover what counts.
Map critical services, test disruption scenarios, and turn recovery priorities into a measurable action plan.
—Readiness index
Illustrative planning sandbox: all default services, losses, recovery timings and stress trials are hypothetical. No real-time systems, incidents, security tools or operational data are connected.
0h
Median recovery objective
RTO across active services
$0
Modeled disruption impact
Current scenario, not forecast
0%
Recovery steps complete
Browser-local checklist
Recovery readiness
Prioritize weak points and dependencies across your modeled operations.
Service readiness profile
Illustrative confidence scores entered by the user
Strong ≥ 80Developing 55–79Needs attention < 55
Executive insights
Derived from editable assumptions
Impact concentration
Which services contribute most to your modeled financial exposure?
Estimated interruption loss by service
Using selected scenario, assumed hourly loss and modeled interruption time
Service dependency registry
Own your continuity inventory, assumptions and recovery targets.
Service readiness is a user-entered planning estimate. Dependency links are used for simplified, one-level knock-on scenario modeling, not a full dependency graph or production monitoring.
Active services
Click edit to change assumptions
Archived services
Archived records are excluded from calculations but preserved locally.
Disruption scenario lab
Explore hypothetical impacts, response levers and recovery constraints.
Scenario multipliers are illustrative assumptions, not historical incident rates, calibrated probabilities or verified monetary forecasts.
Response assumptions
Update levers to instantly recalculate deterministic outputs
InterpretationMore effective containment and additional response capacity reduce modeled downtime. These controls do not guarantee an actual recovery outcome.
Scenario impact snapshot
Calculated for your active services
Total modeled interruption loss$0
Aggregate modeled downtime0h
Services above recovery target0
Response budget (planning input)$0
Potential data-loss window, maximum0 min
Modeled interruption loss excludes response budget. Data-loss windows are derived from entered RPO objectives, not measurements of lost records.
Uncertainty exercise
Compare many random variations of the selected illustrative scenario.
Simulated impact distribution
10th, 50th and 90th percentiles across 400 deterministic trials
Exposure breakdown
Prioritized operational services in the current scenario
Actionable recovery plan
Track preparedness tasks and review an ordered response sequence.
Priority recovery order
Sorted by current modeled loss and criticality
Preparedness checklist
Completion saved only in this browser
Workspace and evidence
Keep an offline record of changes and document your assumptions.
Data controls
No login, backend, external data or paid services
JSON workspace backup
Includes services, scenarios and checklist progress
Restore workspace
Input is validated before it replaces local state
Reset sample workspace
Replaces local sample data after confirmation
Nothing is sent to servers by this application. Browsers may clear local storage. Export a backup before resetting or switching devices.
Recent activity
Local change history for this workspace
Model transparency
What the numbers mean and what they do not prove.
Calculation method
- A preset scenario assigns a hypothetical exposure factor to each functional domain. A severely affected direct dependency adds up to 0.25 exposure to a dependent service (one level).
- Modeled downtime = minimum of scenario duration and [RTO × readiness factor × scenario recovery factor × containment factor × budget factor + 18% × scenario duration × exposure].
- Modeled interruption loss = downtime × user-entered hourly loss × exposure. Total impact sums individual services; overlaps may be double counted.
- Potential data-loss window uses RPO × scenario multiplier, capped by downtime and presented as an illustrative window only.
- 400 seeded stress trials change hypothetical duration and intensity; percentiles describe this exercise, not actual disruption probabilities.
Scope and limitations
ContinuityOS is a static, educational planning tool. It does not detect or respond to real incidents, measure true resilience, certify compliance with ISO 22301 or other standards, establish service-level guarantees, or predict actual losses or recovery times. Defaults are fictional and must be replaced with validated organizational inputs before any serious decision. Financial impact can overlap across dependencies; the model omits knock-on losses beyond one dependency level, contractual penalties, taxes, insurance and externalities.
Good practiceUse this tool for workshops and structured discussions. Verify objectives, owners, dependencies, assumptions and response playbooks with responsible personnel.