An employment tribunal can add 25% to whatever it awards against you, purely because you did not follow a procedure properly. Not for the original incident. For the process around it. That is the Acas Code of Practice, and it is what makes the question of why employees ignore company policies a financial one rather than a cultural one.
TL;DR: Why employees ignore company policies comes down to a few identifiable, mostly non-malicious reasons. They cannot find the current version. Nobody can prove it was read. The rule does not fit the job, or a manager broke it first. In a Gartner survey of 1,012 employees, 87% said they had faced a situation in the past year where they did not know how to comply with a workplace rule (HR Dive, reporting Gartner, 2024). So the fix is not a better-written policy. It is an operating system: findable, provable, practical and led by example.
Key Takeaways
- Staff usually do not ignore policies out of carelessness. Read the guides that rank on this question and they agree on the causes: unclear communication, impractical rules, management double standards and buried documents. Attitude barely features.
- 87% of employees in a Gartner survey said they had faced a situation in the past 12 months where they did not know how to comply with a rule (HR Dive, 2024). Uncertainty, not defiance, is the real driver.
- Plenty of guides give you a fix, and some are good. What none of them does is connect any of it to UK law, or tell you what your evidence has to look like when an auditor, an insurer or a tribunal asks. That is the gap this guide closes.
- The fix has four parts: findable, provable, practical and led by example. Skip one and the other three do less work than they should.
- A policy nobody can find and nobody can prove was read is not a policy. It is a document that exists so somebody can point at it after something has already gone wrong.
Interactive: why are your policies being ignored?
Why employees ignore company policies
Someone on YouTube described writing a joke into a company policy, a line requiring anyone leaving to submit a drawing of a dinosaur, purely to see whether it would be spotted. It was not. In their words: “I expected the editor to read through, nope, it’s official policy now.”
That is funny until you notice it is a test result. The policy went through approval and publication without a single person reading it properly. Ask around and you will find the same admission at every level, including from the people who write the things: it is not unusual for an HR professional to hand out handbooks for twenty years and never read one cover to cover.
Every business owner who has written a policy has watched it get ignored. Not by one difficult employee. By most of the team, quietly, within weeks of the launch email. It is tempting to read that as an attitude problem. It rarely is. In Britain, if you employ five or more people you are legally required to write your health and safety policy down (HSE, “Health and safety made simple: the policy”). But writing it down was never the hard part. Getting it read, understood and followed is.
When I managed policy roll-out across 850+ staff in 20 countries, the policies that failed were rarely the badly written ones. They were the ones nobody could find, or that a manager quietly ignored. So fix those two things first. After that, the wording matters far less than most guides suggest.
What does the evidence actually say?
Uncertainty, not defiance, is the leading driver. In a Gartner survey of 1,012 employees, 87% said they had faced a situation in the past 12 months where they did not know how to comply with a workplace rule or policy (HR Dive, reporting Gartner, April 2024). Gartner’s own conclusion was blunt: a strong ethical culture is not enough to stop noncompliance on its own. People need to know what compliance actually looks like.
Search this exact question yourself and the ranking guides list much the same causes. Unclear communication, policies that feel impractical, management double standards, over-restrictive rules, documents that are buried and hard to read, and a culture that never checks. None of that describes a workforce that has decided to misbehave. It describes a workforce working around obstacles nobody removed.
Is it usually deliberate, or something else?
Mostly something else. A useful way to think about it: most policy violations are intentional yet non-malicious. Staff know a rule exists and choose to bypass it in the moment. Not because they reject it, but because following it exactly would slow the job down under pressure.
That distinction matters for how you respond. Punish expedience as though it were sabotage and staff learn to hide the workaround rather than drop it. The same pattern shows up in a newer wrapper. 52% of AI users are reluctant to admit using it for their most important tasks at all, found in Microsoft and LinkedIn’s 2024 Work Trend Index. People who cannot follow a rule openly will follow it quietly instead.
The pattern I keep seeing is not rebellion. It is a rule and a job that were never reconciled, and nobody noticed until an audit asked.
Why does this matter more than a tidy filing system?
Because the cost of an ignored policy is not hypothetical. It is procedural. The Acas Code of Practice on Disciplinary and Grievance Procedures says it plainly in its own foreword: “Tribunals will also be able to adjust any awards made in relevant cases by up to 25 per cent for unreasonable failure to comply with any provision of the Code” (Acas Code of Practice on disciplinary and grievance procedures). That is not a theoretical maximum either: tribunals do apply the full 25% (Blake Morgan, on a case where the maximum uplift was appropriate). That uplift exists precisely to punish a policy which sits on paper and never reaches the floor. The same Code adds a line worth pinning up: employers “would be well advised to keep a written record”.
There is a second obligation nobody covering this question mentions. The acceptance record you build is personal data about your staff, so it needs a lawful basis and a defined retention period like any other employment record (ICO, keeping employment records). Keeping proof forever “just in case” is its own compliance problem. Decide how long you keep it, and write that down too.
Why doesn’t the usual advice fix this?
Let me be fair to it, because the usual advice is better than critics admit. Search why employees ignore company policies and page one gives you a consistent diagnosis and, in several cases, a real fix. One well-known UK health and safety guide pairs nine reasons with nine remedies. A large American policy-software blog already tells you to keep documents searchable online, re-issue and re-sign them whenever they change, apply consequences consistently and have leaders model the behaviour. That is genuinely useful, and three of the four parts below are in there.
Here is what is missing from all of it. Not one of those guides is written for a British employer. Not one mentions the Acas Code, the tribunal uplift for ignoring it, or the fact that the acceptance record you are being told to keep is itself personal data with a lawful basis and a retention period attached. You are told to track adherence. Nobody tells you what the record has to contain to be worth anything on the day somebody asks for it.
That is the gap. Not “nobody gives you a fix”. Nobody tells you what your evidence has to look like.
What is the operating fix that actually works?
The fix is not a better-written policy. In fact most policies are written clearly enough already. The fix is an operating system with four parts, and skipping one weakens the other three.
Make the policy findable and searchable
The most upvoted comment I found while researching this was not about policies at all. It was about folders: “My biggest problem is folders, people just love having a folder, and sub-folders to Nth degree, to put stuff in to.” That is the real filing system in most SMEs, and it is where policies go to be forgotten.
This is the single most common reason why employees ignore company policies: a document buried three folders deep in a shared drive, or attached to an email from eighteen months ago, might as well not exist. Staff do not go looking for rules. They ask a question when they hit a decision. If the answer is not one search away, they guess, ask a colleague, or do what they did last time.
The fix is unglamorous: one place, one current version, searchable by plain-English question. Old versions get archived, rather than left sitting next to the live one under a similar file name. This alone does not guarantee compliance. It removes the single most common excuse for non-compliance, which is “I couldn’t find it”. That act of looking a rule up is self-service too, and it is the half that employee self-service software usually leaves out, because these tools are built around submitting a form rather than answering a question.
Prove it was read, with an acceptance audit trail
Picture the Monday this actually matters. An incident happened on Friday. Your HR lead is looking for the current version of the policy it touches, and after twenty minutes she has found three: one on the shared drive, one attached to an old all-staff email, one in a folder somebody made during the last audit. Two are undated. The employee signed something eighteen months ago, and nobody can say which of the three it was.
Yet nothing in that story is a documentation problem. Because every version exists. What does not exist is proof of which wording that person accepted, and on what date.
Someone asked this on Quora, and the question is better than most articles on the subject: if a company changes its handbook, how is it legally required to prove employees received the changes, read them, understood them and agreed to them, without signatures? And what happens if an employee is then dismissed for breaching a policy they never knew about?
The best answer anyone offered was to make it a rule that staff check periodically for updates. That is not a control. That is hope with a policy number.
What an acceptance record has to contain
Some guides do tell you to re-issue and re-sign a policy whenever it changes, which is right as far as it goes. What none of them tells you is what the record has to contain. From the UK side, an acceptance record is worth something when it names the person, names the policy, names the version they accepted, carries a date, and can produce the list of who has not accepted it yet. Miss the version number and you cannot prove which wording they agreed to. Miss the outstanding list and you cannot show you chased anyone.
Publishing a policy once, or emailing a PDF, fails the only test that matters: can you show, today, exactly who has read the current version and who has not.
When the documents stop being the problem
There is usually a point where a business stops arguing about the wording and realises the documents are not the problem. Filing, chasing and remembering are the problem, and no amount of rewriting fixes those. At that point you do not need another policy. You need somewhere policies live that does the chasing for you.
A policy manager built into your intranet runs this as a lifecycle rather than a one-off event. Publish, notify the right people, capture a dated read-and-understood acceptance from each person, then chase the stragglers automatically rather than relying on someone’s memory. The Claromentis Policy Manager does exactly this. It publishes a policy, requires acceptance, and then reports across every policy and every person at once, so you can pull the list of who has not accepted what and export it. Be precise about what that record proves, though. The acknowledgement step happened: that much is now evidence. Whether the rule was then followed out in the field is a separate question, and still a management job. You cannot have the second without the first.
Inside Claromentis: who has not accepted what
Policy Users Report
| Name | Job Title | Reference | Policy Title | Categories | Status | Accepted | Date |
|---|
A faithful model of the Claromentis Policy Users Report, verified against the live product on 25 August 2026. It plays itself; it is not a live system, and every name, reference and policy title is invented. The real, working version is in the free 30-day demo.
Proving policy acceptance is the single clearest trigger for adding a platform like this. We go deeper on the full cost and rollout picture in our guide to deciding whether you need a dedicated intranet alongside Microsoft 365.
Retire the rules that are genuinely impractical
Sometimes the answer to why employees ignore company policies is not a communication failure at all. They are a badly fitted rule that nobody has had the authority, or the process, to remove. If a policy gets routinely worked around, the useful question is not “how do we enforce this harder”, it is “why does this not fit the job”.
Review every policy against the people who actually do the work it governs, on a fixed schedule, not just when something goes wrong. A rule that survives that review stays. One that does not gets rewritten or formally retired. Nothing in a policy platform decides this for you automatically. It supports the process by making the current version, and the decision to change it, visible and dated. The judgement stays a human one.
Align leader behaviour with the policy
Ask why employees ignore company policies for long enough and this one comes up every time: a rule a manager does not follow themselves stops being a rule and becomes a suggestion. Staff notice the gap faster than any survey captures. One manager put the problem neatly on a video about exactly this: talking to people one to one helps in the moment, but “they allllllways revert back to their old ways”. They revert because the behaviour they see modelled around them has not changed. Management double standards show up in every serious treatment of this question, alongside unclear communication and impractical rules.
The fix here is not a poster. It is visibility. Managers follow the same rule they enforce, and when a leader genuinely has to make an exception, that exception gets explained rather than left for staff to notice and quietly copy. New managers should be told, explicitly, which policies they are personally responsible for modelling, not just which ones they are responsible for enforcing.
How do you retire a policy without looking like you’re going soft?
Carefully, and in the open. Retiring a rule feels risky because it looks like lowering the bar. Handled badly, it can. Handled well, it does the opposite: it tells staff that the rules that remain were actually chosen, not just inherited.
Publish the change with the reason attached, not just the new version number. “This rule slowed approvals by two days with no measurable safety benefit, so we removed it” builds more trust than silence ever does. Keep the review evidence dated, along with the names of the people who flagged the problem. That record is what shows an auditor, or a sceptical member of staff, that removal was a decision, not neglect. It is the same no-big-bang discipline that works for rolling out an intranet without staff feeling ambushed by it: change in the open, explained, never silent.
A small UK business, before and after the fix
Picture a 40-person UK firm with an expenses policy nobody follows properly. It sits in a shared drive folder called “HR Docs 2023”, two versions behind the current one. Nobody remembers signing off on it. When a new starter asks what the mileage rate is, they ask a colleague, who guesses.
After the fix, the same policy lives in one searchable place. The new starter finds the current version in one search, accepts it as part of induction, and that acceptance is dated and recorded. Six months later the mileage rate changes, the old version archives itself, and every accepter gets asked again. Nothing about the actual rule changed. Everything about whether anyone can prove it was followed did.
| What breaks it | The old way | The operating fix |
|---|---|---|
| Finding the policy | A shared drive, several folders deep, or an old email | One search box, one current version, old ones archived |
| Proving it was read | An email sent, hopefully opened | A dated acceptance record, per person, per version |
| Impractical rules | Enforced on paper, worked around in practice | Reviewed by the people who do the job, retired if they do not fit |
| Leader behaviour | Assumed, never checked | Modelled visibly, exceptions explained |
Frequently asked questions
Why employees ignore company policies in the first place
Mostly for reasons that are not about attitude. They cannot find the current version, nobody has ever proven the policy was read, the rule does not fit how the job actually works, or they have watched a manager break the same rule without consequence. The guides that rank on this question name the same causes, alongside unclear communication and a culture that never checks.
What is it called when an employee does not follow a policy?
In the UK it is usually treated as misconduct, handled under your disciplinary procedure in line with the Acas Code of Practice, rather than the American term “insubordination” that dominates search results. The distinction matters. Insubordination implies refusing an instruction. Most UK policy breaches are not refusals at all, they are people who could not find the rule, were never shown it, or found it unworkable. Reaching for a misconduct process before you have checked those three things is how employers end up on the wrong side of the 25% uplift.
Is ignoring a policy usually intentional?
It is usually intentional in the moment but not malicious. Staff often know a rule exists and choose to bypass it under time pressure. That is worth calling intentional yet non-malicious behaviour, rather than outright defiance of the rule itself.
How do you prove staff have read a policy?
Distribute it through a system that captures a dated, per-person read-and-understood acceptance, not by email. A policy manager built into an intranet notifies the right people, records who has accepted each version, and chases non-readers automatically. It reports acceptance rates on demand, which is the evidence an auditor or insurer actually asks for.
Should you punish staff for ignoring an impractical policy?
Rarely, and not as the first move. Punishing a workaround caused by a badly fitted rule teaches staff to hide the workaround, not stop it. Review the rule against the job it governs first. If it genuinely does not fit, retire or rewrite it. If it does fit, the honest conversation becomes far easier once findability and proof are already fixed.
Do small UK businesses need a formal policy management system?
Not always, and it depends on scale and duty. A very small team can run this fix with a well-organised shared drive and a simple sign-off log. It becomes worthwhile once you need to prove acceptance to an auditor, insurer or tribunal. It is also worthwhile once policies outnumber what one person can track by memory. Our guide on what to write down about AI use at work applies the same pattern to one fast-growing policy type.
The real answer to why employees ignore company policies
Mostly, the answer to why employees ignore company policies is that the document was never built to be found, proven or followed. It is not that staff decided the rules do not matter. Fix the four things that actually break: make the policy findable, prove it was read, retire what genuinely does not work, and hold leaders to the same standard as everyone else. Do all four and the wording of the policy itself stops being the thing that decides whether people follow it.
AI use is one of the policies most often being quietly ignored right now, and it is not the only one. Training records carry the same findability-and-proof problem, covered in our guide to tracking employee training records, and the same fix sits inside the broader case for one connected digital workplace rather than a folder of separate documents.
Most owners assume their policy problem is a writing problem. In the roll-outs I have run, it almost never is. It is a proof problem, and you only discover which one you have when somebody asks you to produce the record.
So find out on your own policies rather than taking my word for it. Open the free 30-day Claromentis demo playground, publish one real policy into it, send it to three colleagues, and look at the acceptance screen on Friday. If everyone has accepted, you did not have a problem. If they have not, you have just found out for free what an auditor would have charged you to discover.