The FOD Discipline: Why Contamination Control Doesn't Stop at the Bin

Most contamination programs stop at telling people what goes in the bin. They have no answer for what happens next.

Every opportunity should be taken to reduce contamination risk. Not as a single tactic bolted onto an education program, but as the frame for everything that follows — from the first bin tag a household receives to the last visual scan before product leaves the gate.

It Starts With Source Separation — But It Can't End There

Education, re-education, encouragement: this is the right starting point, and most councils already do some version of it. Bin lid stickers, photo-illustrated tags, the occasional letterbox drop. It's necessary. It is not sufficient.

The gap is what happens after the education has been tried and the contamination keeps showing up. Most programs — including the better-known national benchmarks — are comprehensive on prevention and thin on response. They tell residents what goes where. They rarely specify, in writing, what happens when someone keeps getting it wrong.

That gap matters because, eventually, sanctions are inevitable. People are people. A council that hasn't decided in advance how it escalates from a first mistake to a persistent pattern ends up improvising under pressure — usually after a complaint, a media query, or a contaminated load a client has already rejected. That's the wrong moment to be designing the policy for the first time.

How Should Contamination Response Actually Escalate?

The principle that works is proportionality: a one-off mistake and a repeat offender are different problems, and treating them identically either over-punishes the first or under-responds to the second.

In practice, that means a graduated ladder — education-only for a first occurrence, increasingly targeted and personal contact for repeats, and only reaching a service-level consequence after a documented pattern or a genuinely hazardous single event. The specific tiers and triggers are a policy design exercise tailored to each council's by-laws and risk appetite — not something to standardise blindly across very different local government contexts.

That line does more work than it looks like it does. Sorting guidance that tries to enumerate every possible item inevitably misses edge cases; a rule that defaults to the safe, low-cost error (something compostable ending up in general waste) rather than the expensive one (something non-compostable contaminating a load) is easier to remember and easier to act on under uncertainty.

Contamination Control Doesn't Stop at the Bin

This is where most operators — not just councils, but processing sites themselves — under-invest. Contamination management is too often treated as a single stage: manual picking, somewhere in the middle of the process, performed by whoever's rostered on. Once that stage finishes, the assumption is that the job is done.

It isn't. Contamination control needs to continue through collection, arrival, picking, processing, movement, stockpiling, screening, and dispatch — every point where material is handled is a point where something out of place can be caught, or missed.

What Does an Airport Runway Have to Do With Compost Quality?

Airports run FOD walks — scheduled, mandatory sweeps of the runway and apron for any object that could damage an engine or aircraft, performed whether or not anything was seen on the previous pass, because the cost of a single missed object is severe and the timing of the next one is unpredictable.

The same logic applies directly to organics processing. Constant visual scanning for contamination should be a duty every person on site carries, in every role — not a task reserved for whoever is rostered "on picking." A piece of plastic, glass, or metal gets picked up the moment it's seen, not when it's convenient. No item is too small to bother with, because the discipline degrades the moment people start triaging what's "worth stopping for."

The mechanism that makes this work in practice is removing friction: a single, known, fixed disposal point for anything flagged — never moved without notice — so there's no excuse to leave something "for later," which in practice means never.

Why This Is a Commercial Risk, Not Just a Compliance Exercise

Here's the part that's easy to underweight until it happens: contamination discovered in delivered product can have a serious effect on a client relationship. Not a compliance footnote — a trust problem, the kind that's expensive to repair and sometimes isn't repaired at all.

That reframes contamination management from "something we do to satisfy a license condition" to "a business risk we actively manage on a client's behalf." It's the difference between a facility that can demonstrate a defined, defensible process and one that can only say it tries hard.

Detection is not the whole answer, either. A facility also needs a defined process for what happens to contamination once it's found — how it's handled, where it goes — and a way of measuring it. Measurement matters most as a feedback loop, not a static KPI: data fed back to the source, whether that's a household or an upstream commercial supplier, turns "you got it wrong" into a visible, trackable scorecard of improvement. That loop is what actually changes behaviour over time — a number on a report that nobody upstream ever sees changes nothing.

The Practical Takeaway

Two things, done together, close the gap most programs leave open: a household response that escalates proportionately instead of treating every mistake the same, and an on-site culture where contamination control is everyone's constant responsibility rather than one stage's job.

Neither is complicated in principle. Both take deliberate design to get right — and both are easy to get wrong in ways that only show up later, in a contaminated load, a frustrated client, or a doorstep visit that should have happened three tags ago.

Frequently Asked Questions