Common situations
S10

The engineer you need can start tomorrow

You have found the engineer you urgently need for a critical project and they can start tomorrow. But the role gives access to sensitive technology and systems, and completing all checks before granting access could delay work the team cannot afford to postpone.

Show what is needed at

The minimal version a partner might accept.

2 standards bear on this

13

Personnel integrity & sensitive roles

Helps you match screening, and safeguards to the sensitivity of the role without unnecessarily delaying recruitment.

Read 13 in full, with the challenges it runs into
13.1

Role risk classification before engagement

Getting started
  • Identify whether the role is standard, sensitive or critical before engagement. Examples may include access to funds, procurement, contracting, sensitive information, technical data, critical systems, export-related activities, public-sector interactions or key customer and partner relationships.
  • Keep the classification simple
13.2

Integrity-informed recruitment decisions

Getting started
  • Consider basic integrity and security information where the role has been classified as sensitive or critical
  • Where concerns are identified, consider whether they affect the person's role, level of access, supervision or suitability for the position.
13.3

Pre-engagement checks and screening level

Getting started
  • Define minimum checks before engagement for standard roles. Examples may include identity confirmation, right to work where relevant, employment or experience verification, and references where feasible.
  • For sensitive and critical roles, determine whether additional checks are required before granting access to the role.
  • For sensitive and critical roles, do not rely solely on personal trust, referrals or technical competence instead of proportionate pre-engagement checks.
13.4

Role-based onboarding and integrity expectations

Getting started
  • New personnel receive practical onboarding covering the company's expected behaviours, confidentiality, conflicts of interest, reporting concerns and appropriate handling of company information.
  • Onboarding may be simple and practical, but it should happen before or soon after the person starts work
  • Access to sensitive information, systems or responsibilities should not be granted before minimum onboarding is completed.
13.5

Safeguards for sensitive and critical roles

Getting started

Nothing required at this level.

13.6

Personnel integrity concerns and escalation

Getting started
  • Identify when personnel behaviour may create integrity, security, financial, operational or partner trust concerns
  • Recognise behaviours that may create integrity, security, operational or partner trust concerns, such as attempts to bypass controls, misuse of company resources, confidentiality breaches, conflicts of interest or other inappropriate conduct.
  • Escalate material concerns rather than handling everything informally
11

Information governance

Helps you control access to and systems while the person is being onboarded.

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