Standards

Information governance

Standard: Company can identify, organise, protect and retrieve the information needed to run the business, support key decisions and respond to partner, bank, donor or programme . is handled on a need-to-know basis, and external sharing is controlled so the company remains reviewable without over-disclosing

On this page
  1. Practical challenges
  2. 11.1Key information and evidence inventory
  3. 11.2Record ownership and organisation
  4. 11.3Information classification and controlled access
  5. 11.4External sharing and controlled disclosure
  6. 11.5Information lifecycle management
  7. 11.6Use of informal channels
  8. Situations this standard answers

Practical challenges

O Operational

Important information may be spread across emails, chats, personal folders, shared drives, ERP systems, spreadsheets, messengers or individual devices

Decisions may be made quickly, while supporting evidence is created later, stored inconsistently or not stored at all

Fast growth and urgent delivery pressure may lead to fragmented records and unclear ownership of information

Different business functions may require access to the same information for different operational purposes, making it difficult to balance availability with appropriate access controls.

S Security

Information may include sensitive technical data, product details, customer or end-user information, routes, locations, military-linked information, personal data, pricing, source code, prototypes or restricted project materials

Broad access to information may improve collaboration but increase security, commercial, personal safety or operational risks.

R Regulatory

Export-control, sanctions, data protection, confidentiality, IP, employment, public procurement or contractual requirements may affect what information must be kept, protected or shared

P Partner

Different customers, governments, donors or international partners may impose different information handling, retention or sharing requirements, making it difficult to apply a single approach across all business relationships.

Requests from customers, governments or international partners for documentation or evidence may need to be balanced against confidentiality, security or contractual restrictions on sharing company information.

RES Resource

Small and fast-growing companies may not have a dedicated information , IT security or document control function

Topics

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

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 , commercial operations, legal and regulatory obligations, and partner , including ownership, decision-making, contracting, third parties, payments and export-related activities where relevant
  • Keep the list short and focused on records that matter
Developing
  • Define minimum record types for key processes and higher-risk activities
  • Identify gaps where important information is not routinely created or retained.
  • Ensure the inventory covers information needed to explain significant decisions, contractual relationships and key business activities.
Advancing
  • Maintain a practical evidence inventory linked to relevant risk areas, including ownership/control, decision-making, third parties, contracting, payments, , cases, export/end-use exposure and transactions
  • Use the inventory to prepare for bank, donor, JV, programme or foreign partner due diligence
  • Ensure the inventory identifies the information needed to explain significant business decisions, relationships and higher-risk activities (what happened, what checks were done, who approved it, what conditions applied and what evidence supports the conclusion)
  • Review the inventory when the company enters new markets, partnerships, programmes or export scenarios
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.
Developing
  • Maintain a simple record map showing key record types, storage location, responsible owner and access level
  • Ensure important records can be located quickly and brought together to explain significant decisions, approvals and business relationships.
  • Use consistent naming and folder structures that support retrieval of and high-sensitivity records.
Advancing
  • Maintain a controlled record structure for key business, , third-party, contract, payment and export-related information
  • Link records to responsible owners, review points, access rights and retention needs
  • Ensure evidence supporting significant decisions and relationships can be assembled quickly and coherently for audits, investigations, or authorised external review.
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 , military-linked information, personal data, 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.
Developing
  • Define different access arrangements for different categories of sensitive information.
  • Review access when people change roles, leave the company or move to sensitive projects
  • Define what can be shared internally, what needs approval, what should be redacted and what should only be shared through controlled channels
  • Ensure access arrangements support legitimate business activities while limiting unnecessary access to sensitive information.
Advancing
  • Consistently apply and maintain access arrangements across systems and business functions using proportionate controls (e.g. role-based permissions, need-to-know access or restricted workspaces).
  • Be able to demonstrate who has access to the most sensitive information, who approved that access and how access decisions are managed.
  • Escalate and investigate significant information loss, unauthorised disclosure or other material information handling incidents, and implement appropriate corrective measures.
11.4

External sharing and controlled disclosure

Getting started
  • Define who may approve external sharing of sensitive or information
  • Share only the information necessary for the intended purpose.
  • Avoid sharing unrestricted folders, internal communications or other without appropriate review.
Developing
  • Use proportionate disclosure arrangements when sharing information with banks, donors, customers, programme counterparts, joint venture partners, foreign partners or other authorised external parties.
  • Consider NDA, restricted folder access, named recipients, redactions, summaries, or data-room access where appropriate
  • Keep a basic record of what was shared, with whom and for what purpose
Advancing
  • Maintain a consistent approach for , partner , funding, programme participation, export-related activities and other recurring external information requests.
  • Use staged disclosure where appropriate, sharing information progressively according to the purpose, level of trust, confidentiality arrangements and stage of the relationship.
  • Prepare standard external-facing summaries or recurring information sets where this improves the efficiency and consistency of responding to authorised requests.
  • Track significant external disclosures of sensitive information and periodically review whether existing safeguards remain appropriate.
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.
Developing
  • Apply to important company information, including contracts, documents, ownership/control records, technical documentation, procedures and materials.
  • Keep approved versions separate from drafts and record material changes
  • Periodically review important company information to ensure it remains accurate and current.
  • Define how long different categories of information should be retained and when they should be archived or disposed of.
Advancing
  • Maintain version history or for important information where traceability is needed.
  • Ensure material changes to important documents are approved, attributable and retrievable
  • Apply consistent lifecycle management so information is updated, archived, retained and disposed of in accordance with business, legal, contractual and partner requirements.
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.
Developing
  • Define which decisions must always be transferred into formal business records. Examples may include approvals, contract changes, payment instructions, exceptions, , export-related commitments, partner requests, technical changes and other significant business decisions.
  • Use meeting notes, follow-up emails, system entries or other documented records to capture important decisions.
  • Define who is responsible for recording decisions made through informal communications.
Advancing
  • Maintain a consistent approach for ensuring key decisions made through informal communications become reviewable business records.
  • Review recurring reliance on informal communications where it creates evidence gaps or makes important decisions difficult to reconstruct.
Record where you stand on information governance

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

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

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