—Scoring
One weighted index, computed on the server.
Responses are scored against the six ACTIVE™ capabilities. Each capability produces a 0–100 sub-score; the overall readiness index is the weighted mean of those sub-scores. Scoring is performed server-side and written by a database trigger, so a client cannot submit or alter its own score.
- audit
- 15%
- create
- 15%
- track
- 22%
- initiate
- 18%
- validate
- 20%
- evolve
- 10%
—Readiness bands
Five bands, defined thresholds.
| Band | Range | Interpretation |
|---|---|---|
| Critical | 0–39 | Foundational gaps across the response chain. A serious incident is likely to be mishandled in the first hour. |
| Vulnerable | 40–54 | Some capability exists, but key parts of the response chain will break under pressure. |
| Developing | 55–69 | Core structures are forming. Response is workable but slow, and rehearsal is inconsistent. |
| Ready | 70–84 | Response systems are documented, owned, and largely rehearsed. Residual gaps remain in speed or AI exposure. |
| Resilient | 85–100 | Response is fast, owned, evidence-based, and continuously improved after every event. |
—Limitations
What First Hour does not claim.
Not independently validated
Weights and band thresholds are practitioner-defined for the Founding 20 phase. They have not been independently validated and must not be described as a certified or scientific instrument.
Not predictive
First Hour does not predict whether a crisis will occur, how long containment will take, or what a specific incident will cost. Model outputs are labelled as indicative readiness signals, never as forecasts.
Illustrative / development benchmark
Any comparison shown before a sufficient real, consented sample exists is a development benchmark for interface purposes only. It is not industry data.
Self-reported inputs
Assessment responses are self-reported by your team. Simulation observes decision behaviour, which is why stress-testing is part of the cycle rather than an optional extra.