Skip to content
Playbook
IntermediateHRPeopleOps

Writing a code of conduct people actually read (and use)

Most codes of conduct are lawyer-written, employee-ignored, and never referenced when it matters. Here's the structure that works — principles, examples, and…

9 min read
On this page
60-Second Summary
  • Principles + concrete examples + clear paths. If any one is missing, the document is decoration.
  • Annual acknowledgement is a SOC 2 control AND a culture moment. Don't waste it on a click-through.
  • Reporting paths must offer at least three options: manager, HR, anonymous/external. Equal-status.
  • Live the document: cite it in decisions, reference it in onboarding, refresh it annually.

A code of conduct is only useful when an employee uses it as a reference under stress. That means it has to be readable, specific, and structurally available — three reporting paths, at least one of which doesn't go through their manager.

The structure

  1. Why we have this (½ page).
  2. 5-7 principles, each one sentence.
  3. For each principle: 2-3 'looks like' examples and 1-2 'doesn't look like' examples.
  4. What to do if you see a violation (3 paths).
  5. Consequences spectrum (coaching → formal → termination).
  6. Acknowledgement + annual refresh.

Examples beat principles alone

Principle: 'We treat each other with respect'
Looks like
  • Disagreeing in the meeting and aligning after
  • Naming harm without labelling the person
  • Apologising specifically when wrong
Doesn't look like
  • Eye-rolls and side conversations in meetings
  • Public criticism of named individuals
  • 'I was just joking' as a defence

Reporting paths

  • Manager (default, fastest, but conflicted when manager is involved).
  • HRBP / People (named individual; not a generic inbox).
  • Anonymous / external (third-party ethics hotline or ombudsperson).
  • Each path describes: who sees it, response SLA, what happens next, retaliation protection.

Keeping it alive

If your last update was 3+ years ago, nobody trusts it. Annual refresh: review what enforcement actions you took, add examples from real cases (anonymised), update where the world changed (remote work, AI tools, social media). Publish the changelog.

Written by Pawan Joshi.Sources cited inline.
First published 16 Jun 2026See site changelog →