What evidence do auditors commonly ask for on 8.4.2 Response structure?

Team structure chart with roles, responsibilities and inter team relationships; Pre defined activation thresholds and the authority to invoke them; Named team members and alternates with competence evidence; Documented team procedures for activation, operation, coordination and communication; Exercise evidence that the teams performed the listed competences.

What is the most common gap auditors find on 8.4.2?

Alternates named on paper but never included in an exercise

ISO 22301:2019 · Operation, ISO 22301:2019

`8.4.2` Response structure

Put in place and keep up a structure of one or more teams that respond to disruptions, with clearly stated roles and responsibilities and clear relationships between teams. Between them the teams must be able to: judge a disruption and its impact against thresholds set beforehand that warrant a formal response; trigger the response and the continuity solutions; plan actions; set priorities, putting the safety of life first; monitor the disruption and the response; and communicate with interested parties, the authorities and the media. Every team must have named people, with stand-ins, who hold the responsibility, authority and competence required, and documented procedures for triggering, running, coordinating and communicating.

Source: ISO 22301:2019, 8.4.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO 22301:2019 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Named team members and alternates with competence evidence · HR system / LMS
Exercise evidence that the teams performed the listed competences · HR system / LMS

governing documentDocuments that govern the control

Team structure chart with roles, responsibilities and inter team relationships · Policy repository / GRC workspace
Pre defined activation thresholds and the authority to invoke them · Document repository
Documented team procedures for activation, operation, coordination and communication · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Alternates named on paper but never included in an exercise
Activation thresholds undefined, so invocation waits on consensus
Life safety priority stated in policy but absent from the team procedures
Media and authority communication left to a role with no delegated authority to speak

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

8.4.1 General · 8.4.3 Warning and communication