Code of Conduct and Ethical Decision-Making: A Practical Guide for Employees

It's 4.45pm on a Friday and a colleague asks you to sign off an expense claim that doesn't quite match the receipts attached. Nobody is breaking the law, exactly, and your colleague is under real pressure to close the month out. Do you sign it, query it, or say nothing and hope it sorts itself out? Most people never face a dramatic scandal at work — they face small, ambiguous moments like this one, several times a year, where the "right" answer isn't written down anywhere and the pressure to just go along with it is real.

This is what a code of conduct is actually for. It isn't a list of things you already know not to do (steal, harass, defraud) — those are covered by specific policies and, in the UK and Ireland, by employment and criminal law. A code of conduct is the foundation underneath all of that: it sets out the values and behaviours an organisation expects day to day, and gives employees a shared way of thinking through the grey areas that policies alone can't anticipate. Most employers build this into structured induction and refresher training — see Learnsignal's CPD courses for how foundation modules like this typically sit alongside more specific compliance topics — because good judgement has to be practised, not just read once and filed away.

What a Code of Conduct Actually Covers

A code of conduct (sometimes called a code of ethics or code of business conduct) is the umbrella document setting out an organisation's core values, the standard of behaviour expected of everyone regardless of role or seniority, and the principle that employees should raise concerns rather than stay silent. It typically sits above a set of more specific policies: anti-bribery and gifts, equality and dignity at work, data protection, whistleblowing, and fraud prevention among them.

Treat the code as the "how we decide" layer and the individual policies as the detailed rulebooks for particular risk areas. For a specific issue — fair treatment and inclusion, for example, or how to raise a serious concern safely — dedicated resources such as a guide to equality, diversity and inclusion in the workplace or a guide to handling whistleblowing disclosures go further. This article covers the layer underneath all of those: how to notice a dilemma and work through it before it becomes a policy breach, a grievance, or a headline.

Recognising an Ethical Dilemma (as Opposed to a Clear Rule Break)

Some situations are straightforward: falsifying safety records or lying to a client is a clear breach, full stop. Genuine ethical dilemmas are different — they usually involve a conflict between two things that both seem reasonable: loyalty to a colleague versus honesty with a client, hitting a deadline versus following the proper process, or being helpful versus being fair to everyone else. A useful early test is to ask yourself three questions:

• Would I be comfortable explaining this decision to my manager, out loud, using the actual reasons I'm using? If you'd need to leave out a detail to make it sound acceptable, that's a signal.
• Am I being asked to bend a rule "just this once," or because "everyone does it"? Both phrases are common precursors to conduct that later looks very different in hindsight.
• Does this only affect me, or could it affect a colleague, a customer, or the organisation's reputation if it went wrong? The wider the potential impact, the more it deserves a considered decision rather than a quick one.

If any of those questions gives you pause, you're not being difficult — you've correctly identified that this is a decision worth slowing down for.

A Simple Framework for Working Through a Dilemma

You don't need a philosophy degree to make sound ethical decisions at work. Most organisational codes of conduct point to some version of the same practical sequence:

The point of a framework like this isn't to produce a mechanical, computer-like answer. It's to slow down the moment just enough that habit, social pressure, or a looming deadline doesn't make the decision for you by default.

When Personal Values and Organisational Values Don't Line Up

Sometimes the conflict isn't between rules and pressure — it's between your own principles and something the organisation, a colleague, or a manager is doing. This is genuinely uncomfortable, and it's worth naming rather than suppressing. A few things help:

• Separate discomfort from wrongdoing. Disagreeing with a business decision (a restructuring, a commercial choice) is not the same as witnessing misconduct. The code of conduct exists for the latter.
• Check what the organisation has actually committed to. Most codes state that employees are expected to raise concerns and won't be penalised for doing so in good faith. That commitment only means something if people use it.
• Use the stated values as your reference point, not personal comfort. A decision can feel awkward and still be the right one — the test is whether it's consistent with the organisation's values and the law, not whether it's the easiest option.

Where the conflict touches on fairness or how someone is treated because of a protected characteristic, it's worth reading alongside a dedicated resource on building an inclusive workplace, since those situations often carry specific legal obligations on top of the general ethical principle.

Knowing When and How to Escalate

A code of conduct is only as good as the escalation routes behind it. Most UK and Irish organisations have a hierarchy of contacts, worth knowing before you need it rather than working it out under pressure:

• Your line manager is the default first point of contact for most day-to-day dilemmas and grey areas.
• HR or a designated ethics/compliance contact is the right route when the issue involves your manager directly, or concerns conflicts of interest, gifts and hospitality, or data handling.
• A formal whistleblowing channel exists for more serious concerns — suspected fraud, illegality, danger to health and safety, or a cover-up. A guide to handling whistleblowing disclosures sets out what should happen next and how managers are expected to respond.
• A formal investigation may follow a concern or complaint; what that process typically involves is covered in a guide to conducting workplace investigations.

Acas, the UK's workplace relations body, is consistent on one point across its guidance: employees should be told clearly how to raise a concern, and organisations should respond promptly. If your escalation routes aren't clear, that's itself worth raising — a code nobody can navigate in practice isn't doing its job.

The Manager's Role: Modelling, Not Just Monitoring

Codes of conduct fail in practice for one recurring reason: employees watch what leadership does far more closely than what the policy document says. A manager who cuts corners under deadline pressure, waves through a borderline expense claim, or jokes about "how things really work here" undermines months of training in a single moment. A manager who visibly pauses on a grey area, or says "let's check the policy," normalises exactly the behaviour the code is trying to encourage. Practically, this means managers should:

• Treat the code of conduct as a living reference, not a one-off signature exercise from someone's first day.
• Respond to questions without visible irritation — a manager who sighs at a query teaches the team not to ask next time.
• Apply the same standard to a senior performer as to anyone else; inconsistent enforcement erodes trust in a code faster than almost anything else.
• Escalate their own uncertainty too. "I'm not sure either, let me check with compliance" models good judgement rather than false confidence.

Why This Foundation Matters More Than It Used To

Baseline conduct expectations aren't just good practice — the regulatory backdrop has been tightening. Under the Bribery Act 2010, an organisation can be held liable for bribery carried out on its behalf unless it can show it had "adequate procedures" in place to prevent it; the Ministry of Justice's official guidance sets out six principles behind that defence, including top-level commitment, risk assessment, and — relevantly here — communication and training so expected standards are actually understood, not just written down. More recently, the "failure to prevent fraud" offence under the Economic Crime and Corporate Transparency Act 2023 came into force on 1 September 2025, making large organisations criminally liable if an employee or agent commits fraud intended to benefit the organisation and reasonable prevention procedures weren't in place. Neither law is really "about" a code of conduct on its own — but both rest on the idea this article has been building towards: employees who can recognise an ethical grey area, and who know they can escalate one safely, are an organisation's first line of defence.

Frequently Asked Questions

What's the difference between a code of conduct and a code of ethics?

In practice the terms are often used interchangeably. Where organisations distinguish them, a code of ethics tends to describe broad values and principles ("we act with integrity"), while a code of conduct translates those into more specific expected behaviours ("declare gifts over a certain value"). Either way, the foundation module covered here — recognising a dilemma and knowing how to work through it — sits underneath both.

What if I raise a concern and nothing seems to happen?

Follow up, and put your original concern in writing if you haven't already, so there's a clear record of when and how you raised it. If the first contact you used hasn't responded within a reasonable time, escalate to HR, a designated ethics contact, or, for serious matters, the formal whistleblowing channel.

Can I get in trouble for raising a concern that turns out to be nothing?

Not if you raised it honestly and in good faith. Codes of conduct and, in the UK, whistleblowing protections exist precisely so people don't stay silent out of fear of being wrong. The expectation is reasonable belief, not certainty.

Does a code of conduct apply the same way to everyone, including senior managers?

It should, and this is one of the clearest signals of whether a code is taken seriously. A code enforced against junior staff but quietly overlooked for senior performers loses credibility fast, and employees notice the gap immediately.

A code of conduct only works if people actually use it — as a first reference when something feels uncertain, not just as a document they sign once and forget. Building that habit usually comes down to practical, scenario-based training rather than a policy read-through, which is why foundation modules on ethical decision-making are typically the entry point into a wider workplace compliance programme. If you're reviewing or refreshing that training for your organisation, Learnsignal's CPD course library covers this alongside the related compliance topics — equality and inclusion, whistleblowing, and workplace investigations among them — that a strong code of conduct programme should sit alongside.