Documents · Glossary
What is a code of conduct?
A code of conduct sets out the behaviour expected of the people it covers, in specific enough terms that a breach can be identified. It usually names the standards, gives examples, says who it applies to, and describes what happens when somebody does not meet it. Ethics codes state values; conduct codes state rules.
Codes get written after an incident far more often than before one, which is why so many of them read as a list of things one particular person once did. A good code is useful before anything has gone wrong.
Indunil Asanka · Co-founder
6 min read · Published
| Code of conduct | Code of ethics | A single policy | |
|---|---|---|---|
| States | Required and prohibited behaviour | Values and principles | One rule on one subject |
| Tone | Specific and testable | Aspirational | Operational |
| Breach | Identifiable, with consequences | Rarely disciplinary on its own | Identifiable |
| Covers | Everyone in the community or workforce | Often a profession | Everyone the policy names |
| Typical length | Two to eight pages | One or two pages | One or two pages |
| Used for | Discipline, membership, contracts | Guidance and professional standing | Day to day decisions |
Specific beats aspirational
The test of a conduct code is whether two reasonable people reading it would agree on whether a given incident breached it. Treat everyone with respect fails that test, because it leaves the whole question open. Do not shout at match officials, and do not comment on an official's decisions on social media, passes it. That is why examples belong in the document rather than in a briefing: they convert a standard into something enforceable. The counterweight is that a code cannot list everything, so a short statement of the principle should sit above each set of examples, with wording making clear the list is illustrative. Codes that are all principle cannot be enforced; codes that are all examples invite the argument that anything not listed is allowed.
Who it binds, and how
A code has force because of the relationship it attaches to. For employees it usually sits under the employment contract as a lawful and reasonable direction, which is why contracts often say the policies are directions rather than terms. For members of a club or association it attaches to membership, and the constitution or rules have to give the committee the power to act on a breach. For volunteers, contractors and parents it attaches to participation, which means the code has to be given to them and accepted before they take part rather than pinned up afterwards. Codes that were never issued to the people they cover are the most common reason a disciplinary decision falls over, and it is entirely avoidable.
The complaints path is the working part
Most of the value in a code sits in what happens after an allegation. It should say who receives a complaint, what happens if the complaint is about that person, whether the complainant's identity is shared with the respondent, how long each step should take, who decides, and what the range of outcomes is. Two things are worth resisting. Promising confidentiality that cannot be delivered, since a respondent generally needs to know the substance of what is alleged in order to answer it. And committing to a fixed sequence of warnings, which removes the ability to act proportionately on serious conduct. Where children are involved, the child safe requirements in the relevant jurisdiction override the internal process and should be referenced plainly.
Keeping it alive after it is written
A code stops working the day it becomes the document everybody signed once. Reissuing it at the start of each season or year, with the sign on recorded against the version, keeps it current and creates the evidence that people were told. Reviewing it after each complaint is more useful than an annual review, because a complaint that the code did not cover is the clearest possible signal of a gap. Watch for two drifts. Scope creep, where the code absorbs uniform rules, fee policies and training schedules until nobody can find the conduct standards. And silent enforcement, where behaviour is tolerated for a season and then acted on, which makes the eventual decision look arbitrary even when it is right.
Building the code as a document
A code of conduct is a short to medium document with numbered sections, so it can be cited clause by clause in a decision letter. At eight pages it does not need a contents list, since contents are only used at long scale and the headings must match exactly when they are used. Callouts have four variants and one is enough to mark the reporting line for serious matters. Tables suit a summary of who the code applies to and in what capacity. One signature block party is one signer, so an acknowledgement countersigned by a club secretary needs two parties.
Translating the code for different audiences
A single code that covers staff, volunteers, members and parents has to speak to all of them, and the usual result is a document that speaks properly to none. The fix is one code with audience sections rather than four separate codes that drift apart. Keep the standards common, then add a short section per group listing the situations that group actually meets: sideline behaviour for parents, supervision and travel for coaches, financial delegation for committee members. A one page extract per audience, handed over at sign up and pointing back to the full document, gets read far more often than the whole code. It also makes the review easier, because a change in one group's obligations does not require reissuing everything. Where the audience includes children, write a version in language a twelve year old will follow rather than a summary of the adult text.
Questions people ask
Should a code of conduct be signed?
Recording acceptance matters more than the signature itself. An online acknowledgement naming the version and dated is sufficient in most settings and much easier to administer across a large membership. What matters is being able to show, later, which version a particular person accepted and when they accepted it.
Can a code of conduct cover behaviour outside work?
Sometimes, where the conduct has a sufficient connection to the organisation, such as representing it publicly, harming its reputation or affecting colleagues. That connection has to be real and the code should say what it means rather than claiming authority over private life generally. Overreach here is a common source of unfair dismissal findings.
Does a small club need one?
Yes, and often more than a large one, because small clubs run on personal relationships and have no other mechanism when a relationship breaks down. A two page code with a clear complaints path costs an afternoon and is the difference between a committee that can act and one that has to hope the problem resolves itself.
What is the difference between a code and a policy?
A code collects behavioural expectations across many situations into one document that everybody reads. A policy addresses one subject in depth, usually with a procedure behind it. Organisations typically have one code and many policies, and the code points to the policies rather than repeating them.
Who should handle a complaint about a committee member?
Not the committee alone, and the code should say so in advance. A named independent person, a delegate from a parent body, or a subcommittee excluding anyone with a conflict are the usual answers. Deciding this after a complaint arrives is how organisations end up with a decision nobody accepts as fair.
How long should a code be?
Two to eight pages covers most organisations. Beyond that it is absorbing material that belongs in separate policies. The practical test is whether a new volunteer would read the whole thing at sign up. If they would not, the parts that matter most to them should be pulled into a one page summary attached to the front.
Make one with documents
The button opens the generator with this use case already described. Change the wording to match your own.
Create a document with OneCraftRelated questions
- What is an employee handbook?An employee handbook collects a workplace's policies in one document. What it is for, whether it binds the employer, and how to keep it current.
- Policy against procedure, and where a guideline fitsPolicy says what and why, procedure says how, and a guideline recommends. The difference between a policy and a procedure, with a leave example.
- Privacy policy against privacy noticeA privacy policy sets out how an organisation handles personal information. A privacy notice tells a person what is happening at the moment of collection.
Step by step in the builder: Create a document with AI, then Every document component and when to use it.
Written and checked by the OneCraft team. Last checked .