# Workplace Conduct Policy

- Source: https://support.icompaas.com/compliance/policy-docs/workplace-conduct-policy
- Section: [Compliance](https://support.icompaas.com/compliance) › [Policy Documents](https://support.icompaas.com/compliance/policy-docs) › All policy documents
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Policy Document**·1 mapped controls

## What this policy is

Defines expected behaviour in the workplace — anti-harassment, anti-discrimination, professional conduct, and the reporting and investigation procedure for violations.

## Why every organization needs one

Both a legal-compliance requirement in most jurisdictions and a baseline expectation for customers and employees. Documented conduct expectations are also what gives HR procedural footing.

## What a competent Workplace Conduct Policy typically contains

-   Purpose and scope
-   Roles and responsibilities
-   Definitions
-   Prohibited conduct categories
-   Reporting channels (incl. anonymous)
-   Investigation procedure
-   Non-retaliation commitment
-   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_workplace_conduct_policy_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](https://support.icompaas.com/compliance) 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.

| Framework | Control | Title | Component |
| --- | --- | --- | --- |
| ISO/IEC 27001:2022 | [A.6.2](https://support.icompaas.com/compliance/iso-27001-2022/a-6-2-terms-and-conditions-of-employment) | [Terms and conditions of employment](https://support.icompaas.com/compliance/iso-27001-2022/a-6-2-terms-and-conditions-of-employment) | People controls |

1 control across 1 framework reference this policy.

## About this page

This article is part of the iCompaas [Policy Documents](https://support.icompaas.com/compliance/policy-docs) 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.

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): SOC 2 auditors test that policies like this one exist, are approved, and are reviewed on schedule; the guide lists the full set.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 clause 5.2 and Annex A.5.1 require a documented, approved policy set; the guide shows how it fits the ISMS.