Tools
ISO 22301:2019 §8.4 · ISO 22320
In development

riscResponse

RISC · Risk Intelligent Supply Chain

riscResponse is the incident response and activation workspace in the RISC family from e|Resilient. When a disruption hits, declare the incident, activate the right plans, coordinate the team from one source of truth, and capture every decision in a defensible timeline — so the response is managed, not improvised.

The RISC family. The lowercase “risc” prefix is shared across our tools and originates with riscManager.com, our Risk Intelligent Supply Chain platform. Where riscScope assesses the threats and riscAnalysis sets the recovery objectives, riscResponse is where the program is put to work — the execution layer that activates the plans the rest of the family spent its effort making defensible.

Why It Exists

The plan is written. The incident still goes sideways.

A company can do everything right — a current risk register, a defensible BIA, a continuity plan signed off by leadership — and still fumble the actual event. The reason is almost never the plan. It's that when the disruption finally hits, everyone is in a different document, a different group text, and a different phone call, and nobody is keeping the record.

The gap isn't planning — it's activation. The first hour is spent deciding whether this is real, finding the right version of the plan, working out who's supposed to be in the room, and reconstructing later what was decided and when. That hour is paid for by every system, customer, and employee waiting on a response that hasn't organized itself yet.

riscResponse closes that gap. Declare the incident, activate the right plans in one move, run the response from a single live workspace, and let the decision log write itself — so the after-action review reads like a managed event, not a scramble someone tried to remember.

What It Does

The three jobs a response workspace has to do.

A response either activates cleanly, coordinates a team in real time, and leaves a defensible record — or it doesn't.riscResponseis built around those three jobs and nothing it doesn't need during a live event.

  • 🚨

    Declare and activate

    The moment something happens, riscResponse turns a written plan into a live response. Declare the incident, classify its severity, and the right response and continuity plans activate — no scramble to find the binder while the clock runs.

    • Incident declaration with severity classification (Sev 1–4)
    • Activation authority captured — who can declare, who must be told
    • One-click activation pulls the relevant response and continuity plans
    • Auto-notification to the response team the moment the incident opens
  • 🧭

    Coordinate the response

    During an event, everyone working from a different document, group text, and phone call is how managed incidents become chaotic ones. riscResponse puts the whole team on one live source of truth for the duration.

    • Role-based action checklists — every seat knows its next move
    • Live status board: open tasks, owners, and current incident state
    • Task assignment and hand-off tracked in real time
    • Communication log for internal, customer, and stakeholder updates
  • 🧾

    Capture the record

    The decisions made under pressure are exactly the ones an after-action review and an auditor will ask about later. riscResponse writes the record as the response unfolds — automatically, with timestamps — so nobody is reconstructing it from memory a week later.

    • Time-stamped decision and event log built automatically
    • Who decided what, when, and on what information — captured inline
    • Severity changes and escalation history tracked per incident
    • After-action report generated from the live record, not rebuilt after

How It Works

From declaration to after-action report.

Four steps. Pre-staged before the event, auto-saved through it. Resume from any device, any time.

  1. Step 1

    Pre-stage the response

    Before anything happens, map your response plans, Crisis and Incident Management Team roles, escalation triggers, and communication templates into the workspace — fed by the threats from riscScope and the recovery objectives from riscAnalysis. The response is staged and waiting, not assembled mid-crisis.

  2. Step 2

    Declare the incident

    When a disruption hits, the on-call lead declares it, sets the severity, and the right plans activate. The response team is notified automatically and arrives in a workspace that already knows what plan is running and what each role owns.

  3. Step 3

    Run the response

    Role-based action checklists, a live status board, and real-time task assignment keep everyone aligned through the event. Every decision and status change is logged with a timestamp as it happens. Auto-saved at every input, multi-device, resume from anywhere.

  4. Step 4

    Stand down and debrief

    Close the incident, export the full timeline and decision log, and generate the after-action report with corrective actions — the input that drives your next exercise cycle and the evidence an auditor or insurer will ask to see.

What You Get

The record an audit asks for — written as it happened.

Everything riscResponse produces comes from the live response, not a reconstruction afterward. The timeline your board reviews, the AAR that drives your next exercise, and the evidence your insurer wants are the same source of truth — captured once, while it was actually happening.

  • Time-stamped incident timeline and decision log — the defensible record of who decided what, when, and on what information
  • Activated plan and role-assignment matrix showing who held which response role for the duration of the event
  • After-action report (AAR) with corrective actions, ready to feed the next exercise and plan-revision cycle
  • Severity classification and escalation history for every incident, with the declaration and stand-down times
  • Communication log: every internal, customer, and stakeholder notification sent during the response
  • CSV and print-ready PDF export of the full incident record for the board, the insurer, or the regulator
  • Incident-over-incident comparison — see whether declaration, activation, and recovery times are actually improving
In development

Coming to the RISC family.

riscResponse is in active development. Join the waitlist to shape it and get first access when it ships — or, if you need response capability today, e|Resilient delivers it hands-on through our Crisis Management and Emergency Response engagements.

Path 1 · Early access

Be first when riscResponse ships

Join the waitlist and we'll bring you into early access as the workspace matures. Waitlist members help shape the response model — the severity scale, the action checklists, the AAR format — and get it inside their e|Resilient workspace ahead of general availability.

Path 2 · Available today

Need response capability now?

You don't have to wait for the workspace to get the capability. While riscResponse is in development, e|Resilient builds and runs the same response discipline with you directly through our Crisis Management and Emergency Response service lines.

Stop letting the first hour decide the outcome.

Join the riscResponsewaitlist, or schedule a 30-minute consultation and we'll walk through how e|Resilient runs incident response today — and where the workspace is headed.

Book consultation