Development and coordination of management disciplines

What clause 5.8 says

The clause does not create a new discipline. It asks the organization to identify the disciplines that contribute to resilience, assess how each one contributes, build flexibility into them, and improve communication, coordination and cooperation between them. Annex A gives a sample list of twenty disciplines, from asset management to strategic planning. The clause also asks the organization to handle uncertainty around its goals across the functions. The word across is doing the work. A risk register that no one outside the risk function reads, a continuity plan that ignores the supplier strategy, and a security programme that reports elsewhere are each individually competent and collectively incoherent.

Why it matters

Most large organizations have the disciplines. What they lack is a way to see the seams between them. The clause is an instruction to look at the seams: where two disciplines make assumptions about each other, where a control in one creates a dependency in another, and where a decision in one is invisible to the rest. Coordination is not the same as centralisation. The disciplines keep their expertise and their accountability; the programme creates the forum and the information flow that let them act as a system.

What good looks like

Map the disciplines against the nine attributes and the core services. For each discipline, record what it contributes, what it assumes from the others, and where the handoffs are. Choose the three seams that matter most and write a short protocol for each: who decides, who is informed, and what triggers the handoff. Test one protocol in an exercise. Redo the map when a discipline changes its operating model.

Evidence a reviewer asks for

There is no ISO certification or accredited assessment scheme for ISO 22316. The assessor here is your internal auditor, a customer assurance team or a consultant.

An assessor will ask how the disciplines coordinate and who can see across them. A list of disciplines with no seam analysis describes an org chart, not a resilience system.

• Discipline map The management disciplines in scope, their contribution and their dependencies
• Seam protocol For the critical handoffs, who decides, who is informed and the trigger
• Coordination forum The forum where disciplines coordinate, with the decisions it took
• Flexibility evidence How a discipline changed its approach in response to a new condition
• Annex A review Which of the sample disciplines apply, and which do not, with the reason

Where it commonly fails

• Each discipline reports separately and no forum sees them together.
• The continuity plan assumes a supplier strategy that the business has already changed.
• Coordination is delegated to a junior role with no authority over the disciplines.

What to do before the second edition

Hold a half-day seam workshop with the discipline leads. Ask each to name one assumption it makes about another discipline. The assumptions that are wrong are the priority work. Record them and assign an owner.

Read across

• 4.2 Coordinated approach
• 5.7 Availability of resources
• 5.9 Supporting continual improvement
• 6.1 General

← 5.7 Availability of resources5.9 Supporting continual improvement →

Full register / The dates / Free transition check