Write a code of conduct because when a conduct problem arrives, custom has nothing to show: no dated page, no consequence named beforehand, and no proof the person knew the rule broken. That is not because the people on your place behave badly. What the missing code costs is not worse behavior. It is that the farm has no ground to stand on the day it has to act, and no answer when a buyer, an inspector or the worker’s own family asks what the rule actually was.
Everybody knows the rule. No phone in your hand while the auger is running. Nobody drives the loader after drinking. The chemical store gets locked and the key goes back on the hook. It holds week after week, because each person learned it from the one before them, until the afternoon somebody does not, and someone gets hurt or something goes missing. The farm reaches for the rule and finds it was never written, never dated, and never handed to the person now saying they never heard of it.
Is a code of conduct a document, or the habit already in people’s heads?
A document, and the habit is exactly what it replaces. The Food and Agriculture Organization of the United Nations (FAO) treats a code as the working form of a farm’s ethics, and its SAFA Guidelines describe what one does: a code “provides clear guidance in concrete situations, is authoritative, without limiting scopes of action too much, and fosters desirable behavior”. The same framework states the objective plainly, that the enterprise publish a declaration “(such as a code of conduct or vision statement) that is binding for management and employees or members”.
Binding is the word a habit never reaches. A rule everyone absorbed by watching binds nobody in particular, because nobody can say when it started or who ever agreed to it.
Does writing it down change how anyone behaves?
On its own, close to not at all, and that is worth knowing before you spend a morning on it. Stöber, Kotzian and Weißenberger ran a survey experiment with 1,005 managers at one European corporation and found that “not the mere existence of a code but its design matters for compliance”, and that “more specific compliance training is more effective than general training”.
A review of 100 studies of big-company codes, by Babri, Davidson and Helin, found the codes “insufficient in themselves”; a farm is not a big company, but the lesson carries over: a code written only to exist changes nothing.
FAO says it from the other side, warning that a written statement can “project an image of sustainable practice beyond the actual effort of the enterprise”.
So do not write a code expecting it to change behavior on its own. It earns its place for two things a habit cannot give you: a written rule you can point to on the day of a problem, and a consequence decided in advance, while nobody was in trouble. What matters is the proof it leaves and a rule you can apply the same way to everyone, because it is written down.
What sits beside each rule, and where does the law come in?
A consequence, written before anyone breaks the rule, and it is the one part of the page that touches the law of your country. The consequence is the farm’s to set, a light word about the phone and a heavier one about drinking before driving a machine. When the rule broken is harassment, the consequence needs a route to report it and a deadline to answer, which live on a written harassment policy and a channel rather than here. Where the consequence is dismissal, national labor law sets a floor the farm cannot write under, and the international standard shows the shape that floor tends to take.
The International Labour Organization (ILO) gives that shape in a 1982 recommendation. It is guidance for governments, meant to feed into the law each one writes, not law on your farm, but it says that for a lesser fault, the kind that becomes grounds for dismissal only when it happens again, a worker should not be dismissed “unless the employer has given the worker appropriate written warning”.
For that warning to count, the farm needs three things: a rule that already existed, a warning in writing, and a record that both happened. That is why the consequence goes beside the rule before anyone breaks it. The exact floor is your country’s, so someone qualified where you are has to check your consequences against that law; writing the rule and collecting each worker’s signature works the same way anywhere.
| Reference | What it speaks to | What it puts on the farm |
|---|---|---|
| FAO SAFA Guidelines, Theme G1 | the code as the farm’s own rule | a declaration binding for management and employees, which is still not evidence of anything until it is practiced |
| ILO Recommendation No. 166 (international) | the consequence | no dismissal for repeatable misconduct without a prior written warning, with the exact floor left to each country’s law |
| Cornell Agricultural Workforce Development (United States farm extension) | keeping it current | apply it consistently, revise it at least once a year, and have counsel check it before it takes effect |
How do you prove the person knew the rule?
A signature, collected on the day you hand the page over, not on the day the problem arrives. The written warning the labor recommendation asks for already assumes the person was on notice, and a signature taken up front is the cheapest proof that they were. FAO’s own test for whether a code is real is that people can account for it: its positive condition is that employees can “identify how it influences the work which they do”.
The signature does not make the rule enforceable. The rule was enforceable anyway. What it does is move the argument. On the day of the problem the question is no longer whether the person knew, because there is a line with their name, the date, and a sentence saying they were given the code and read it. Read to each person and signed, it is the same rule for the operator hired last month and the one who has worked here twenty years, which is more than the habit ever managed, because the habit was never the same twice.
What keeps the code real after it is signed?
An effective date, a date to revise it, and the discipline to apply it the same way every time. Cornell Agricultural Workforce Development tells farms writing a handbook to “write down employment policies and procedures to encourage better workplace communications and consistency”, to “update the handbook on a regular basis, at least annually”, and to have it “reviewed by appropriate legal counsel before putting it into effect”. Three lines on your page come out of that sentence: the date the code takes effect, the date it comes back to the table, and the check by someone qualified in your country before either.
A rule two people apply differently is two rules, and whoever breaks it will find the difference before management does. Conduct deserves the same care you give a spray record: written, dated and applied the same way every time, like any other part of farm management. The signed code is also one of the things you check in a first internal audit, the day the farm first sits down to see whether its written rules are being kept and not only filed.
This code sits beside other written pages without replacing them. A written succession plan settles who takes over the farm and who may sign for it; this code settles how the people already working there are expected to behave. When the conduct is a deal between the farm and a relative or a partner’s company, that interest goes on a written register of family and business interests, kept beside this page. Licenses and permits that expire on dates the farm does not set go on the compliance calendar, a dated list so none of those deadlines passes unseen.
A buyer or a bank may also ask what the farm can show on paper. The signed code is one of the records that go into a first ESG report from what you already measure, a short summary of the farm’s environmental, social and governance (how the farm is run) numbers.
Where to start
An afternoon for the page, ten minutes per person to hand it over and read it back, one line whenever a rule is broken from then on. Paper is enough. One step runs on somebody else’s clock, the person qualified in your country, and the code waits for them before it takes effect.
The surprise on most farms is not that a rule finally gets broken. It is how fast the argument stops being about the conduct and turns into an argument about whether there was ever a rule at all. A page with a date and a signature ends that second argument before it starts, and that second argument is the only part of the whole business the farm was ever going to control.