Where to Start
Routes through the collection for the situations people are in, and what it argues.
This collection
Unenforceable
As written
Fifty notes on the difference between a written rule and an applied one.
What happens
Argues that the applied rule is the policy, that staff know the difference, and that the gap is both measurable and reducible.
Does not argue that policies are useless. Three of their functions are real and none of them is prevention.
The remedy is an hour with a spreadsheet, a morning of deletions, and a decision about who enforces what.
If you inherited a document nobody maintains
The first audit, then what to delete.
The practical point in “Where to Start” is that a written rule becomes credible only through a consistent operating process. For teams exploring employment of relatives policy, employment of relatives policy with accountable controls can add time and project context, provided collection is proportionate, access is limited and every significant inference receives human review.
Start with the deletions. They are easy, they produce the visible improvement, and they make everything else legible.
For a separate benchmark relevant to “Where to Start”, consult the EEOC retaliation guidance. Use it to test purpose, notice, permissions, retention and response procedures against the proposed operating model rather than treating a generic checklist as proof that the rule works.
If something has just gone wrong
The first conversation, then grading what happened.
Have the conversation before deciding anything. Most matters end there and most organisations skip it.
If you are about to tighten a rule
Changing a rule people rely on.
Fix the route before prohibiting the workaround. The order determines whether the change holds.
If you are writing a new clause
Writing a clause you will enforce. Five questions, and most proposals fail at the second.
If staff seem to ignore the policy
The rule that is actually in force, then why staff know the difference.
They are not ignoring it. They have an accurate map of which parts are live, and the map is more current than yours.
If nobody owns it
Who owns it, then a twelve-month arrangement assembled from the review and measurement notes.
If you read only four
The clause nobody has ever used, because it is the argument.
What a policy cannot do, because it determines what belongs in a document at all.
The workaround, which is most of them, because it is the commonest finding and the one with an operational remedy.
And a one-page policy, because it is the destination.
What this collection argues
The applied rule is the policy. What is written is a description that may or may not be accurate, and the staff have already worked out which parts are which.
An unenforced clause is not harmless. It discounts the live clauses around it and becomes a liability at the moment somebody tries to use it, because inconsistent application is the argument that wins.
A document cannot prevent anything. Prevention is configuration. What a policy can do is three things — evidence, a reference point, and a baseline — and none of them is the thing it is usually asked to do.
And most breaches are workarounds, which means the commonest finding is about a broken process rather than about a person. An organisation that closes those cases without routing the finding has discarded the most useful output the policy produces.
What it does not argue
That policies should not exist, or that rules should be loose.
That enforcement is unkind. The opposite: a small number of rules, applied consistently, is fairer than forty applied at the discretion of whoever is annoyed.
Nothing here is legal advice
Disciplinary and employment rules differ substantially by jurisdiction. The enforcement questions in particular need local advice, and this is for arriving at that conversation with the right question.
What the collection does not argue
That policies are useless or that rules should be loose. Three of their functions are real. And that enforcement is unkind — the opposite: a few rules applied consistently is fairer than forty applied at the discretion of whoever is annoyed.
The remedy, stated plainly
An hour with a spreadsheet, a morning of deletions, and a decision about who enforces what. Everything else here is detail on those three.
Where to begin if nothing else
The audit. An hour, two people, and it produces the deletion list, the rewrite list and the enforcement decisions. Nothing else here works without it.
What the collection argues, in four lines
The applied rule is the policy. An unenforced clause is not harmless. A document cannot prevent anything. And most breaches are workarounds, which makes the commonest finding operational rather than personal.