Common situations
S6

A production site goes down before delivery

A critical production site suddenly becomes unavailable just days before an important delivery. Production needs to continue elsewhere, but key equipment, information and personnel are not all available, and some of the usual processes cannot operate as normal, while the delivery deadline remains unchanged.

Show what is needed at

The minimal version a partner might accept.

4 standards bear on this

2

Organisational structure & roles

Helps you establish backup responsibilities when a key person or function becomes unavailable.

Read 2 in full, with the challenges it runs into
2.1

Role definition for key functions

Getting started
  • List the key functions needed to run the company and support external cooperation
  • Identify who is responsible for each key function in practice
  • Cover at minimum finance, procurement, contracting, operations/production, security, HR/people, compliance/legal where applicable, and export or partner coordination
2.2

Functional structure and reporting lines

Getting started
  • Prepare a simple internal structure showing key functions and reporting lines
  • Use functions rather than personal names where this is safer or more practical
  • Include at least management, finance, procurement, operations/production, legal/compliance where applicable, security and export or partner interface roles
2.3

Role documentation and accessibility

Getting started
  • Record key responsibilities in an accessible form, such as job descriptions, role notes, process descriptions or employment contracts
  • Avoid relying only on chats, verbal instructions or individual memory
2.4

Partner-facing role explanation

Getting started
  • Identify which organisational information may be shared with external partners and who approves its disclosure
  • Avoid ad hoc sharing of internal charts, names or reporting lines
2.5

Governance and review

Getting started
  • Assign one person or function to maintain the organisational structure and role information
  • Define who approves changes to key roles, reporting lines and organisational responsibilities
3

Decision-making & authorities

Helps you maintain clear authority for urgent decisions and exceptions during disruption.

Read 3 in full, with the challenges it runs into
3.1

Key decision categories

Getting started
  • Identify the main types of decisions that should not be left fully informal
  • Cover at least contracts, significant payments, procurement, supplier or intermediary engagement, export-related activity, sensitive hiring, partnerships, use of donations or support, and exceptions from standard practice
3.2

Decision authority and approval

Getting started
  • Define who initiates, reviews and approves/blocks each key decision category
  • Use existing tools where possible, such as email, task trackers and avoid relying solely on informal discussions for approvals of key decisions.
3.3

Escalation and high-sensitivity decision

Getting started
  • Identify decisions and situations that require enhanced review or escalation before a decision is final because they involve elevated legal, integrity, operational or security risks.
  • At a minimum, include decisions involving defence products, public-sector counterparts, export activity, intermediaries, complex or unusual payments, unclear ownership, sanctions or adverse media concerns, conflicts of interest, controlled technology, sensitive customers or end users, restricted information, urgent exceptions, or commitments outside normal authority.
  • Highly sensitive decision making requires additional reviews and or approvals, with an accurate record of the final decision.
3.4

Exception and urgent decisions

Getting started
  • Identify when a decision represents an exception to normal practice
  • Record the reason for the exception, who approved it and whether follow-up is required
  • Avoid allowing urgent decisions to remain completely undocumented
3.5

Decision documentation and evidence

Getting started
  • Record key decisions in a simple form, using existing tools where possible
  • At minimum, record what was decided, who approved it and when
  • Keep information relied on for the decision together with the decision record where it is necessary to explain or evidence the decision avoiding reliance on chats, verbal arrangements and other informal arangements
3.6

Governance and review

Getting started
  • Assign one person or function to maintain the company's decision-making framework
  • Define who approves changes to decision categories, approval routes and escalation rules
12

Operational resilience

Helps you identify what must continue, critical dependencies and workable backup arrangements.

Read 12 in full, with the challenges it runs into
12.1

Critical activities and continuity priorities

Getting started
  • Identify the activities that must continue during disruption. Examples may include production, delivery, customer and partner commitments, financial operations and other functions essential to maintaining business continuity.
  • Keep the list short and realistic
12.2

Crisis decision authority and role continuity

Getting started
  • Identify who can make urgent decisions during disruption
  • Identify critical roles where the company depends heavily on one person.
  • Cover at least production, finance, procurement, customer and partner communication, export-related activities, security-sensitive responsibilities and other business-critical functions.
12.3

Minimum controls during disruption

Getting started
  • Identify which controls should not be fully bypassed even during disruption, Examples may include payments, procurement, third parties, access to sensitive information, export-related activities, conflicts of interest and other high-risk decisions
  • If a control cannot be followed, record the reason and who approved the exception
12.4

Critical operational dependencies

Getting started
  • Identify suppliers, subcontractors, logistics providers, materials, components, systems or services that are critical for continued operation
  • Define who is responsible for managing each critical operational dependency.
  • Keep basic contact and contract information accessible
12.5

Access to critical information during disruption

Getting started
  • Identify the information and records that must remain available for critical business activities during disruption.
  • Consider information needed to continue production, deliveries, payments, customer and partner commitments, regulatory obligations and other essential operations.
  • Avoid relying solely on personal devices, local folders or informal communications for information critical to business continuity.
12.6

Partner communication and external commitments

Getting started
  • Identify who is authorised to communicate with customers, partners, donors, banks, programme counterparts and other external stakeholders during disruption.
  • Keep communication factual and coordinated
  • Do not make commitments externally unless the person has authority to do so
11

Information governance

Helps authorised personnel retain access to the information and records needed to continue critical operations.

Read 11 in full, with the challenges it runs into
11.1

Key information and evidence inventory

Getting started
  • Identify the main types of information the company needs to keep for business, management and partner review
  • Cover needed to support governance, commercial operations, legal and regulatory obligations, and partner due diligence, including ownership, decision-making, contracting, third parties, payments and export-related activities where relevant
  • Keep the list short and focused on records that matter
11.2

Record ownership and organisation

Getting started
  • Define where key records are stored
  • Avoid keeping important evidence only in personal emails, private chats, individual laptops or unmanaged folders
  • Assign responsibility for maintaining each important record type, where feasible.
11.3

Information classification and controlled access

Getting started
  • Identify which information is sensitive and requires restricted handling. Examples may include technical designs, source code, prototypes, production information, export-controlled information, customer or end-user information, commercially sensitive information, military-linked information, personal data, speak-up cases and other information whose unauthorised disclosure could create security, commercial or operational risks
  • Limit access to sensitive records to people who need them for their work
  • Share sensitive information only through approved and appropriately controlled channels. Avoid open chats, uncontrolled folders, personal accounts or other unauthorised channels.
  • Identify who may approve access to sensitive information
  • Avoid unnecessary copying, downloading or broad distribution of sensitive information.
11.4

External sharing and controlled disclosure

Getting started
  • Define who may approve external sharing of sensitive or partner-facing information
  • Share only the information necessary for the intended purpose.
  • Avoid sharing unrestricted folders, internal communications or other sensitive information without appropriate review.
11.5

Information lifecycle management

Getting started
  • Ensure current versions of important documents are easy to identify
  • Use simple version identification methods (e.g. version numbers, dates or approved file names).
  • Avoid using outdated contracts, policies, ownership files, partner materials or technical documents by mistake
  • Update important company information when relevant changes occur.
11.6

Use of informal channels

Getting started
  • Recognise when key decisions, approvals or commitments are made through chats, calls or informal messages
  • Where important business decisions or commitments are made through calls, chats or informal messages, ensure the outcome is recorded as part of the company's business records.
  • Avoid leaving key approvals or commitments only in informal communications.

More situations

All 11 situations