Standards

Organisational structure & roles

Standard: Company can explain how are organised, who is responsible for key decisions, and when matters must be escalated. The structure does not need to be complex, but it should be clear enough to support day-to-day management, continuity and conducted on the company by prospective partners

On this page
  1. Practical challenges
  2. 2.1Role definition for key functions
  3. 2.2Functional structure and reporting lines
  4. 2.3Role documentation and accessibility
  5. 2.4Partner-facing role explanation
  6. 2.5Governance and review
  7. Situations this standard answers

Practical challenges

O Operational

Teams may be small, fast-moving and built around people who cover several functions at once

Responsibilities may shift quickly because of growth, urgent production needs, new projects or wartime pressure

S Security

Publishing names, reporting lines or sensitive roles may create personal or operational security risks

Some roles may need to remain restricted because they relate to sensitive projects, locations, technology or customer relationships

RES Resource

Companies may not have enough management layers or separate functions to apply a classic corporate structure

Topics

5 topics, each written at three levels. Each level assumes the one before it.

2.1

Role definition for key functions

Getting started
  • List the 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
Developing
  • Define the main responsibilities of each key function in a short and practical way
  • Record where responsibilities overlap and who has the final say when more than one function is involved
  • Make sure responsible people understand their role and know when to involve others
Advancing
  • Keep role descriptions aligned with how decisions are actually made in practice
  • Ensure that differences in responsibilities or authority between comparable roles are deliberate and reflect the needs of the role or business
  • Review role definitions when the company estructures, introduces new products, enters new partnerships, or export activities or changes its operational model
2.2

Functional structure and reporting lines

Getting started
  • Prepare a simple internal structure showing 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
Developing
  • Keep the structure updated when changes to teams, projects or reporting lines affect how key functions are organised
  • Reflect where key functions sit in practice, including temporary or project-based roles
  • Identify areas where one person covers several functions
Advancing
  • Maintain a clear internal structure that reflects how the company actually operates
  • Keep a controlled version that can be shared when needed without disclosing sensitive personnel, locations or restricted project information
  • Use the structure to support , partner and continuity planning
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
Developing
  • Keep role information structured and accessible for relevant staff
  • Ensure role documents are consistent with internal processes and actual reporting lines
  • Update role documents when responsibilities change materially
Advancing
  • Keep documents clear enough to support , internal handover, partner and continuity
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
Developing
  • Prepare a concise explanation of and responsibilities, avoiding unnecessary personal details
  • Explain responsibilities for finance, contracting, procurement, compliance/legal where applicable, export interface, security-sensitive coordination and management approval
Advancing
  • Maintain a controlled partner-facing organisational overview for or programme
  • Apply : functional overview first, named rindividuals only where necessary and approved
  • Share sensitive organisational information through controlled channels and keep a record of external disclosures
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
Developing
  • Review role and organisational structure when there are material changes, such as rapid hiring, new projects, new sites, restructuring, export activity, joint production or major partner engagement
  • Keep a short record of organisational changes resulting from the review
Advancing
  • Ensure periodic management or board-level review of organisational structure and
  • Use review findings to close gaps and reduce overlaps
  • Public disclosure of organisational information should remain proportionate to security and business needs
Record where you stand on organisational structure & roles

Situations this standard answers

  1. S1
    A foreign partner asks who owns you

    A foreign defence company wants to partner with you, but before proceeding it asks for information about your ownership, decision-making and business processes. Some of the information has never been formally documented or brought together, and some of it is sensitive but the partner cannot proceed without it.

  2. S4
    Grown from 20 to 200, still run like 20

    Your company has grown from 20 to 200 people in a short time, but it still operates much as it did when everyone knew each other. Now an important decision needs to be made and several people believe they have authority to approve it, while others are not sure who is actually responsible.

  3. 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.