Policy Document·1 mapped controls

What this policy is

The behavioural expectations every employee is held to — ethical conduct, professional behaviour, conflicts of interest, gifts and hospitality, anti-bribery, and reporting of wrongdoing.

Why every organization needs one

The code is the foundation HR and Legal rely on for any disciplinary action and is increasingly demanded by enterprise customer security questionnaires.

What a competent Employee Code Of Conduct typically contains

  • Purpose and scope
  • Roles and responsibilities
  • Definitions
  • Ethical principles
  • Conflict-of-interest declaration
  • Anti-bribery and gift limits
  • Whistleblower protection
  • Review cadence (typically annual) and version control
  • Approval, sign-off and effective date

How iCompaas tracks this policy

The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_employee_code_of_conduct_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).

Compliance frameworks that reference this policy

The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.

FrameworkControlTitleComponent
ISO/IEC 27001:2022A.6.4Disciplinary processPeople controls

1 control across 1 framework reference this policy.

About this page

This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.