Features
A code of conduct only works if it survives real pressure, not just launch day
Codes of conduct people can actually use: what belongs in one, the rules that fail under pressure, and the test that decides whether it works.
| Situation | Immediate need | What the code contributes | Warning sign |
|---|---|---|---|
| Considering a role | A picture of the workplace | A boundary around acceptable behavior | Values and rules are mixed together |
| Responding to a doubtful request | A usable next move | A trigger, first action, and named destination | The person cannot find a route before answering |
| Reviewing an incident | The rule that applied then | A dated version and evidence of enforcement | Only the document's existence can be established |
Reading the code before joining
Someone considering a role uses the document to infer the workplace, not to resolve a live request. The conduct code should state the line around acceptable behavior; a shorter, separate values statement can explain the reasons behind it without crowding operational instructions.
Keep the code's assignment limited to boundaries and referral. Using it as a values statement, legal shield, and decision method at once makes the action harder to find. Questions about competing duties belong to ethical frameworks, not to an employee inventing a method while a response is due.
Acting while a request is pending
When a request is due soon, an abstract principle cannot supply the next move.
A usable rule names the event that activates it, a first action, and a person who can take the question when the situation is uncertain. In the example here, the employee may have about ten minutes to respond.
Reconstructing the rule after an incident
Looking back after an incident requires more than finding a current copy. The reviewer needs to know which wording applied then, whether employees knew it, and whether the organization enforced it. A polished document with no visible history or evidence may show publication, but not operation.
The Department of Justice guidance asks whether a compliance program operates, rather than whether policies simply exist. A code cannot prove its own effectiveness: relevant evidence is whether employees understood the instruction and whether the organization applied it after someone crossed the line.
Put the signal before the decision
A practical check is to give a specific situation to someone who has worked with the organization for three weeks and ask what they would do on Thursday, with the request awaiting an answer. If they cannot identify a trigger, action, and destination, the wording is not usable in context.
Why a rule fails the test
- No triggercan't tell you're in it
- No first actionsilent on what to do
- No destinationends in a mailbox
- No answer when the manager asks
If the answer is unclear, the rule has failed in use, regardless of how carefully it was drafted. The mistake patterns often involve a missing cue or route at the moment action is required. Check for these gaps before adding another broad statement to the document.
- No recognizable trigger.A general category such as conflicts may not help when a relative's company appears on a bid list. The conflicts question needs a concrete cue.
- No first action.A prohibition without a next move leaves the employee stuck. Suggest a low-cost response, such as asking a question, putting the request in writing, or contacting a named person.
- No reachable destination.Directing someone to Compliance is not enough if they cannot identify a person. A mailbox with no clear human contact does not complete the route.
- No response to a manager's instruction.An employee may receive a questionable request from their own manager. If the code says nothing about that case, the silence can be read as an instruction to comply.
Replace broad ideals with actions
Specific triggers are more useful than simply raising the severity of a consequence. The examples below stay within the code's subject matter: each practical version identifies an event that activates the rule and tells the employee what to do next.
Unusable rules vs usable rules
Unusable, no trigger
- Integrity
- Act with integrity
- Conflicts
- Avoid conflicts
- Gifts
- No inappropriate gifts
- Confidentiality
- Protect information
- Reporting
- Report promptly
- Legal
- Comply with all laws
Usable, trigger clear
- Integrity
- Put commitments in writing
- Conflicts
- Declare before the decision
- Gifts
- Declare anything in live procurement
- Confidentiality
- No records on personal devices
- Reporting
- Tell manager within one day
- Legal
- Route to counsel before deciding
| Broad instruction | Action a person can recognize |
|---|---|
| Act with integrity in all dealings | Put a commitment that changes price, date, or scope in writing before accepting it |
| Avoid conflicts of interest | Before a decision, disclose in writing a financial or family interest held by you or someone in your household in a party to it |
| Do not accept inappropriate gifts | During live procurement, disclose any offer from a party and do not decide its value yourself |
| Protect confidential information | Do not transfer company records to personal accounts or devices; treat material not already public as confidential |
| Report misconduct promptly | Within one working day, tell your manager or the named alternative in writing and keep a copy |
| Comply with applicable laws | If a decision involves employment, competition, anti-corruption, personal data, product safety, financial reporting, or sanctions, send it to counsel before deciding |
A clear instruction removes judgment from the person least able to exercise it safely. Asking a junior employee to decide whether a gift is appropriate can leave them arguing with a senior about the answer. Where one person can both perform and check a task, repair the process instead of relying on individual caution.
Publication does not settle the operating questions
A well-written code can lose credibility through exceptions, uneven enforcement, an unusable reporting channel, or training that tests attendance rather than understanding. These failures arise after launch as well as during drafting: employees learn what the organization means from how the rule is applied and whether concerns receive a response.
Four places codes fail downstream
- Unrecorded verbal exceptions
- Enforcement varying by production
- Routes with no visible evidence
- Training that measures completion
The test is not whether every detail can be made public, but whether people can see that the route operates. A short account of concerns raised, substantiation, and time taken can offer visibility without publishing case details. For training, the training framework suggests walking a real situation from the last year with the people involved and noting where the route stalls.
- Unrecorded exceptions.A senior person's verbal departure from a rule can make the written boundary depend on whom an employee asks. The person granting an exception should document it and explain the reason.
- Unequal consequences.When the same conduct ends one person's employment but brings only a conversation for a larger biller, employees take their lesson from the cases they can name.
- A silent reporting channel.People may stop using a route whose operation they cannot see. Some account of concerns raised and outcomes can show that reports do not disappear.
- Completion-only training measures.A completion figure establishes that a video played, not that someone can locate and follow the instruction.
Give each rule a reason to occupy space
A rule belongs when a reasonable person could make a good-faith mistake and that mistake would matter. Applying this test can prevent document growth without a shared standard for inclusion, a problem discussed in code ownership roles.
Does this rule earn its place?
Could a reasonable person get it wrong in good faith, and would it matter?
Include it, including the awkward specifics
Cut it: restated law, unenforceable, or never attempted
That standard excludes restatements of laws that may change while the code remains fixed; routing a question is more suitable. It also excludes conduct nobody would attempt merely to make the document look complete, and instructions the organization would not enforce. A decorative rule invites employees to guess which other directions count.
Retain situations that can be mishandled in good faith: a request from above, an offer from a customer, seeing a colleague's conduct, or a clash between a rule and a deadline. These moments call for a clear trigger and first action, rather than asking an employee to invent the boundary.
Let use determine when revisions are due
A new market, a new contract category, or a second case that fits no existing instruction can prompt review. Keep the wording that applied previously, and record what changed and why. The aim is to respond to real signals while preventing the document from growing without limit.
- Record exceptions, revisions, and reasons for removing a rule; retain older versions so the applicable wording can be established later.
- Retire instructions that no longer earn their place. A code that only grows becomes harder to use, and employees may stop consulting it.
- Review the volume passing through the escalation route each quarter. No concerns may mean the trigger is hard to recognize; every case arriving may mean the rule does not distinguish situations.
- Track recurring questions. A question asked three times may signal that a sentence needs repair, which is cheaper than repeatedly answering the same uncertainty.
Judge length by whether a person facing a ten-minute deadline can locate the operative instruction. If a code runs to dozens of pages, commentary may have buried the action. Shortening should make the rule easier to find, not remove a direction that matters.
Conduct outside work belongs only when its connection to work can be stated plainly and the organization would act on it. Legal limits differ by jurisdiction, so seek advice rather than assuming. The Information Commissioner's guidance on when consent is valid illustrates how specific limits can be when personal data is involved.
When someone breaks a rule unintentionally, the response communicates something alongside the breach. Decide in advance how to distinguish a mistake from a choice and record that distinction. Consistent treatment of intent matters more than making every response severe.
A signature can establish that someone was told about the code, but it cannot establish that they know how to use it. Assign a named owner to gather questions and propose revisions, separate from the person deciding individual cases; an unnamed committee can leave nobody accountable.
For an existing document, start with instructions that end at a department rather than a person, and with rules that provide no first action. Those edits address two immediate obstacles to use under pressure. Then test the revised wording with employees to see whether they understand how to act.
In this guide
- Codes of conduct checklist: every item, with the reason behind itCodes of conduct, audited: twelve tests from finding the gift rule in a minute to whether anyone senior has ever been disciplined, with scoring.
- Checklist for spotting codes of conduct mistakes before they cost youNine ways codes of conduct go wrong, from legal drafting it alone to rules that are never retired, each with how it happens and the repair that works.
- How to build a codes of conduct framework stage by stageCodes of conduct written as a project: scope from real questions, five-field rule cards, scenario testing, a manager launch and two working logs.
- What staff actually ask about codes of conduct, and what it meansThe eight questions staff ask about a code and what each reveals is missing, plus the harder questions the person writing one should answer first.
