What this is
What is a code of conduct acknowledgement?
What is a code of conduct acknowledgement?
A code of conduct acknowledgement is a worker's confirmation that they were given the organisation's code of conduct, in a language and with the time they needed to read it, and that they accept it. It is completed at hire and again whenever the code is revised, and it is the document HR relies on if a conduct matter later becomes formal.
Who completes it and when?
The worker completes it, prompted by HR or a line manager, at three points: new starter induction, whenever the code is revised, and on whatever periodic cycle the compliance programme sets. Contractors and agency staff bound by the code should go through the same process, not just directly employed workers.
What makes an acknowledgement usable in a disciplinary case?
Not the signature alone. It needs the comprehension fields answered: the code provided in a language the worker understood, real time given to read it, and questions invited. A signature with those fields blank proves distribution, not understanding, and understanding is what a disciplinary process actually has to establish.
Scope
When is a code of conduct acknowledgement required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- A worker joins and needs to acknowledge the code as part of induction
- The code of conduct has been revised and every existing acknowledgement needs to be reissued against the new version
- A periodic re-acknowledgement cycle is due under the compliance programme
- The workspace is being set up, or the register needs an entry added or retired
- A disciplinary matter is being prepared and the acknowledgement needs to be produced as evidence
Do not use it for
- Whistleblowing Report Record, which records a concern raised confidentially about wrongdoing, and how it was handled.
- Conflict of Interest Declaration, which records a declared interest that could affect a business decision, and how it will be managed.
- Just Culture Determination, which records how an individual's actions were judged against the culpability framework once a breach or incident has occurred.
- Induction record, which covers the wider onboarding programme the code of conduct acknowledgement sits inside, not the code itself.
- Anything outside KnowComply, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 37301 cl.5.2 requirements does this satisfy?
ISO 37301 treats the code of conduct as one output of the compliance policy, and requires that the policy and the behaviour it sets out are communicated, understood and reinforced by leadership, not simply issued once and filed.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 37301 cl.5.2 | Compliance policy communicated in a form workers can understand and apply | Header |
| ISO 37301 cl.7.3 | Awareness of the compliance policy and the obligations that follow from it | Content covered |
| ISO 37301 cl.7.4 | Internal communication relevant to the compliance management system | Process |
| ISO 37301 cl.5.1 | Top management demonstrating leadership and commitment to the standards set | Process |
| ISO 37301 cl.7.2 | Competence, including training that supports what the code sets out | Process |
| ISO 37301 cl.7.5.3 | Documented information controlled and retained as evidence | Outcome |
What it does not cover
- Whistleblowing Report Record, which records a concern raised through the reporting channel the code refers to, and how it was handled.
- Conflict of Interest Declaration, which records a specific declared interest, not general acceptance of the standard the code sets.
- Just Culture Determination, which records how an individual's actions were judged once a breach is alleged, and which duty of care applied.
- Modern Slavery and Labour Standards Assessment, which assesses labour conditions at the site rather than a worker's acceptance of behavioural standards.
- Training records for the substance of the code, which live in KnowTrain and evidence competence, not acknowledgement.
Global
Code of Conduct Acknowledgement requirements by country
Few regimes mandate a code of conduct itself, but several attach real consequences to how well an organisation can show its standards were actually communicated and understood, not just distributed.
Federal Sentencing Guidelines §8B2.1; DOJ Evaluation of Corporate Compliance Programs
An effective compliance programme is expected to communicate and enforce its standards, with training and acknowledgement treated as evidence of that.
In an investigation, prosecutors ask whether the code was actually read and understood, not just distributed; an acknowledgement without the comprehension fields answers only half of that question.
Bribery Act 2010, adequate procedures guidance
Communication and training are one of the six principles a compliance procedure is judged against.
A code acknowledged but never explained weakens the adequate procedures defence specifically at the point prosecutors test hardest: whether staff actually understood what was expected of them.
ISO 37301
Requires the compliance policy to be communicated within the organisation and made available to relevant interested parties.
Certification audits sample acknowledgements against the fields that show understanding, not just against the count of signatures on file.
How to complete it
How to complete a code of conduct acknowledgement, step by step
Most acknowledgements are collected as a formality at induction. The parts that decide whether the record holds up later are the ones a template does not force anyone to think about.
Provided in understood language and time given to read it are Yes/No fields, but a Partly or No against either is the actual finding. Recording it and moving on defeats the point of asking; it should trigger translation, a briefing session, or both before the acknowledgement is treated as complete.
A code revision only means something if every existing acknowledgement is reissued against the new version. Organisations routinely update the document and leave the historic acknowledgements standing, so the personnel file shows agreement to a version nobody currently follows.
Applies to contractors and agency is a Yes/No field precisely because it is the one most often assumed rather than checked. A disciplinary process against an agency worker for a code breach fails immediately if that worker was never asked to acknowledge the code in the first place.
An acknowledgement drive with no answer against managers model the code and training supports the code produces high completion numbers next to a workforce that has never seen the standard applied. Both fields exist so the record cannot be read as compliance activity alone.
What auditors find
Most common code of conduct acknowledgement findings
Acknowledgement records are usually complete as paperwork. The findings are about what the paperwork actually evidences, not whether it exists.
| Finding | Clause | What fixes it |
|---|---|---|
| Acknowledgement recorded with no evidence the code was provided in an understood language. | ISO 37301 cl.5.2 | Record the language used and, where translation was needed, retain the translated version referenced against the acknowledgement. |
| Signature held, but no real time was given to read the document before signing. | ISO 37301 cl.7.3 | Separate distribution from acknowledgement by at least a stated reading period; do not collect both at the same desk visit. |
| Code revised, but historic acknowledgements not reissued against the new version. | ISO 37301 cl.7.4 | Trigger a reissue campaign from the document control revision, and track it as its own completion metric. |
| Contractors and agency workers excluded from the acknowledgement cycle. | ISO 37301 cl.7.3 | Extend the acknowledgement to anyone bound by the code, and cross-check it against the agency labour provider assessment. |
| Acknowledgement not held in the personnel file, or held separately from the disciplinary case that later relies on it. | ISO 37301 cl.7.5.3 | File the acknowledgement in the personnel record at the point it is signed, not retrospectively when a case needs it. |
| No record that questions were invited or how they were handled. | ISO 37301 cl.7.3 | Record whether questions were invited and note who fielded them, even where none were asked. |
Case in point
Case in point: the acknowledgement that could not be relied on
A distribution site dismissed a supervisor for a serious breach of the code's conflicts-of-interest section. HR produced the signed acknowledgement from two years earlier as evidence the supervisor knew the standard. The acknowledgement recorded a signature and a date; the fields for provided in understood language and questions invited were both blank.
At the tribunal, the supervisor's representative argued the code was one of a stack of documents signed on the first day, in English, with no briefing, to a worker whose first language was not English. Without an answer in those fields to rebut the claim, the acknowledgement was accepted as proof of distribution but not of understanding, and the dismissal was found procedurally unfair on that point alone.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- CMP-039
- Archetype
- Record
- Record ID
- COC-2026-000
- Scoring
- Acknowledgements current
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 37301 cl.5.2
- Links
- Links Induction, Document control
- Tags
- Ethics
- Sections
- 4
- Fields
- 40
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
15 fieldsRecord ID*
Auto sequence. Format COC-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Worker*
Person ID*
Format PER-0000.
Links to FDN-003 Person ID
Worker 2*
Code Version*
Acknowledgement Trigger*
Provided In Understood Language*
- Yes3 pts
- Partly1 pt
- No0 pts
Time Given To Read It*
- Yes3 pts
- Partly1 pt
- No0 pts
Questions Invited*
- Yes3 pts
- No0 pts
The Document Referred To When Conduct Becomes Formal
A code nobody acknowledged is hard to rely on in a disciplinary process. Acknowledgement at hire and on revision is what makes it usable.
Content covered
6 fieldsExpected Behaviour Explained*
- Yes3 pts
- Partly1 pt
- No0 pts
Reporting Concerns Explained*
- Yes3 pts
- Partly1 pt
- No0 pts
Conflicts Of Interest Explained*
- Yes3 pts
- Partly1 pt
- No0 pts
Gifts And Hospitality Explained*
- Yes3 pts
- Partly1 pt
- No0 pts
Confidentiality Explained*
- Yes3 pts
- No0 pts
Consequences Of Breach Explained*
- Yes3 pts
- Partly1 pt
- No0 pts
Process
6 fieldsAcknowledgement Recorded*
- Yes3 pts
- Partly1 pt
- No0 pts
Signature Or Digital Confirmation Held*
- Yes3 pts
- Partly1 pt
- No0 pts
Applies To Contractors And Agency*
- Yes3 pts
- Partly1 pt
- No0 pts
Reissued On Revision*
- Yes3 pts
- Partly1 pt
- No0 pts
Managers Model The Code*
- Yes3 pts
- Partly1 pt
- No0 pts
Training Supports The Code*
- Yes3 pts
- Partly1 pt
- No0 pts
Outcome
13 fieldsAcknowledgement Complete*
- Yes3 pts
- Pending1 pt
- No0 pts
Acknowledged Date
Recorded In Personnel File*
- Yes3 pts
- No0 pts
Next Version Reissue Required*
- No3 pts
- Yes1 pt
Review Date*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
HR*
Signature*
Compliance Lead*
Second Signature*
CMP-039 · record IDs look like COC-2026-000 · Links Induction, Document control
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Holds the code of conduct acknowledgement library against your registers, flags acknowledgements not reissued since the last code revision, and keeps the evidence trail together.
Connects the code to the briefing or training session that gives the acknowledgement its comprehension evidence, rather than leaving that to a desk-side signature.
Extends the acknowledgement cycle to contractors and agency workers bound by the code, so the applies to contractors field reflects a checked answer, not an assumption.
Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowComply — audit and governance. Audit programmes, legal register, management review, risk and certification.
Meet KnowComply→Glossary
Code of Conduct Acknowledgement definitions and key terms
- Code of conduct
- The organisation's statement of expected behaviour, covering areas such as conflicts of interest, gifts and hospitality, confidentiality, and reporting concerns.
- Acknowledgement
- A worker's confirmation that they received, read and understood the code, distinct from agreement or endorsement of its content.
- Reissue
- Providing an updated version of the code to everyone who previously acknowledged an earlier version, and collecting fresh acknowledgement against it.
- Adequate procedures
- The UK Bribery Act defence standard, judged partly on whether staff were properly communicated with and trained on the standards expected of them.
- Tone from the top
- The demonstrated behaviour of leadership against the code, which either reinforces or undermines what the acknowledgement asks workers to accept.
FAQ
Frequently asked questions about code of conduct acknowledgement
What is the code of conduct acknowledgement template based on?+
It is built against ISO 37301 cl.5.2, the compliance policy clause. ISO 37301 is the international standard for compliance management systems, and clause 5.2 requires the policy to be communicated in a form that people can actually apply, not merely published.
What sections does the code of conduct acknowledgement contain?+
There are 4 sections: header, content covered, process, outcome. Together they hold 40 fields, 35 of which are required.
How many code of conduct acknowledgement records should we have?+
This is a singleton. One record per workspace, set up once and maintained, rather than one per event. Other templates refer back to it.
Which programme does the code of conduct acknowledgement belong to?+
It is part of Ethics, Labour and Anti-Bribery. A reporting channel people trust, and labour risk assessed where it actually sits.
How is a code of conduct acknowledgement scored?+
Scoring is acknowledgements current. High is good. The scored fields sit mostly in content covered and process, because those are the fields that distinguish a genuine acknowledgement from a filed signature.
Does a signature alone satisfy the record?+
No. A signature evidences that a document changed hands. The fields that evidence the acknowledgement itself are language, time given to read it, and questions invited, and a record missing those answers is weaker than most people assume it is.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Ethics, Labour and Anti-Bribery
Whistleblowing Report Record
Records a concern raised confidentially about wrongdoing, and how it was handled
Conflict of Interest Declaration
Records a declared interest that could affect a business decision, and how it will be managed
Modern Slavery and Labour Standards Assessment
Assesses the site and its labour supply chain for forced labour, debt bondage, withheld documents and unlawful deductions
Anti-Bribery Risk Assessment
Assesses exposure to bribery and improper payments across procurement, permits, inspections and customer relationships
Agency Labour Provider Assessment
Assesses an agency for how it screens, trains, inducts and supervises the people it sends
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
More in Ethics and Conduct
Whistleblowing Report Record
Records a concern raised confidentially about wrongdoing, and how it was handled
Conflict of Interest Declaration
Records a declared interest that could affect a business decision, and how it will be managed
Modern Slavery and Labour Standards Assessment
Assesses the site and its labour supply chain for forced labour, debt bondage, withheld documents and unlawful deductions
Anti-Bribery Risk Assessment
Assesses exposure to bribery and improper payments across procurement, permits, inspections and customer relationships
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 37301:2021 clauses 5.1, 5.2 and 7.2 to 7.5
- Federal Sentencing Guidelines §8B2.1 (US)
- Bribery Act 2010, adequate procedures guidance (UK)
- DOJ Evaluation of Corporate Compliance Programs
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.