Common situations
S9

Law enforcement asks about employee misconduct

Law enforcement contacts your company about suspected misconduct involving your employee and asks how the company handled the issue. You need to respond quickly, but information is scattered, some of it is sensitive, and decisions made months earlier were not all formally recorded.

Show what is needed at

The minimal version a partner might accept.

4 standards bear on this

8

Speak-up culture

Helps you demonstrate how concerns can be identified internally, escalated and handled safely.

Read 8 in full, with the challenges it runs into
8.1

What should be reported

Getting started
  • Explain in simple terms what types of concerns should be raised
  • Include suspected misconduct, bribery, conflicts of interest, unsafe shortcuts, pressure to bypass checks, misuse of assets or funds, serious quality issues, data leaks, retaliation, or concerns about third parties.
  • Make clear that people do not need full proof before raising a concern
8.2

Reporting channels

Getting started
  • At least one reporting channel is established for raising concerns (e.g. dedicated reporting email, designated reporting person or reporting form).
  • Concerns are expected to be raised through established reporting arrangements rather than addressed solely through informal discussions
  • The reporting process is documented (e.g. Reporting Procedure, Speak-up Procedure or equivalent guidance).
  • Reporting arrangements enable concerns to be raised confidentially, with anonymous reporting available where appropriate to the company's legal, operational and security context.
8.3

Protection of whistleblowers (preventive)

Getting started
  • Access to information identifying the reporter is restricted to those who need it for handling the report.
  • The company considers how the identity of the reporter can be protected throughout the reporting process and introduces appropriate safeguards where needed (e.g. limiting the number of people involved in handling the report, separating the reporter from those assessing the concern where feasible, or limiting access to documents containing identifying information).
  • Where the identity of the reporter cannot reasonably remain confidential, the company considers and agrees appropriate protection arrangements with the reporter before further handling the report where feasible.
  • For reports raised in good faith the company should implement an explicit non-retaliation policy.
8.4

Response to retaliation

Getting started
  • Where a concern of retaliation is raised, the company reviews whether any recent organisational decisions affecting the reporter (e.g. performance assessment, disciplinary action, change of responsibilities or project assignment) may be connected to the original report.
  • Allegations or indications of retaliation are reviewed by the person or function responsible for handling such concerns, or by another or function not involved in the alleged retaliation or underlying concern where a conflict of interest exists, to determine whether retaliation may have occurred (e.g. by reviewing relevant decisions, speaking to those involved or considering the timing and circumstances of the alleged retaliation). The outcome and any actions taken are documented.
  • Where retaliation is identified, the company takes action to stop the behaviour and prevent further retaliation (e.g. withdrawing or correcting retaliatory decisions, increasing oversight of decisions affecting the reporter, changing reporting or supervisory arrangements where necessary, or taking disciplinary or other management action in relation to those responsible).
8.5

Governance

Getting started
  • A responsible person or function is designated to receive and manage reports, with responsibilities clearly defined and communicated. Where separation of responsibilities is not feasible, alternative review or escalation arrangements are established.
  • The responsible person or function is able to request information and involve relevant business functions where necessary to manage reports.
  • Reports involving the responsible person/function or senior management are handled through alternative reporting or escalation arrangements.
8.6

Communication & awareness

Getting started
  • Employees understand what concerns should be reported and how to raise them.
  • Information on the speak-up system remains readily accessible throughout employment (e.g. during induction, through internal guidance, the intranet, notice boards or other communication channels).
8.7

Learning & improvement

Getting started
  • Learning and improvement are ad-hoc.
14

Internal investigations

Helps you assess serious concerns, investigate them appropriately and document conclusions and corrective actions.

Read 14 in full, with the challenges it runs into
14.1

Scope and responsibility

Getting started
  • Identify the types of integrity concerns that may require an internal investigation rather than routine management or operational handling.
  • Concerns may arise through speak-up reports, audits, internal controls, management observations, partner notifications, due diligence or other sources.
  • Define who receives and makes the initial decision on how the concern should be handled.
14.2

Independence and objectivity

Getting started
  • Recognise situations where the person(s) handling or overseeing an investigation may have a conflict of interest or other circumstances affecting their impartiality.
  • Avoid assigning investigations to people directly involved in the matter or reporting to those whose conduct is being reviewed.
  • Escalate concerns where impartiality cannot reasonably be maintained.
14.3

Investigation outcomes and response measures

Getting started
  • Record the outcome of the investigation and the basis for the conclusion reached.
  • Define any follow-up actions arising from the investigation and assign responsibility for their implementation.
  • Record the basis for closing the investigation, including where allegations are not substantiated or evidence is insufficient to reach a conclusion.
14.4

External coordination and information sharing

Getting started
  • Identify when an investigation involves external stakeholders, such as customers, government authorities, prime contractors, subcontractors or international partners.
  • Define who may communicate externally about an ongoing investigation.
  • Avoid communicating investigation information externally without appropriate authorisation.
11

Information governance

Helps you retrieve the records and evidence needed to reconstruct what happened and how the company responded.

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

Decision-making & authorities

Helps you demonstrate who made relevant decisions, what was approved and how exceptions or were handled.

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

More situations

All 11 situations