About this block

Incident Response Process publishes the playbook you hold yourself to. Four numbered cards run the arc of an incident, detect, communicate, resolve, learn, each with a short description of what happens in that phase. The lede frames the promise, the same four steps run every time and each carries a commitment you measure against.

The steps are one array. The commitment row at the base of each card is where the block earns its keep, paged within 60 seconds and postmortem within 5 business days are numbers a reader can hold you to. A process without deadlines is a diagram, the printed time commitment is what makes it a promise.

When to use

Reach for this block on status pages and trust centers where buyers want to know not just whether you fail but how you behave when you do. The numbered arc reads fast and the commitment rows answer the follow up question before it is asked, turning an anxious topic into a demonstration of discipline.

A natural flow around it on a Marketing Pro page:

Before

• Reliability stats establishing the track record

After

• Incident update timeline showing the process running in a real incident
• SLA commitments binding the commitments into contract terms

What you can display

One strong use is the incident response playbook. Other processes:

• Security response. The disclosure to patch path with each stage timed, for a security page.
• Onboarding steps. The path from signup to live with a commitment per stage, for a sales page.
• Support workflow. Triage to resolution with the target time at each handoff, for a support page.

Tip: print a real number on every step, a commitment you can count is what separates this from a flowchart.