The last thing that touches a piece of produce before it leaves the field is rarely a person’s hand. It is a bin, a knife, a conveyor belt, a tote stacked on a pallet. Those surfaces are as much a food safety hazard as a contaminated water source or an untrained worker, and they get a fraction of the record-keeping attention, mostly because they look like equipment rather than like food safety.
An inspection record for this equipment is not a maintenance log. A maintenance log asks whether the machine runs. A food-contact inspection asks a narrower and more specific question: is the surface that touches the crop clean, intact, and free of anything that arrived on it since the last wash.
The two questions can have opposite answers on the same piece of equipment, which is exactly why they need separate records. A knife can be perfectly functional and still fail a food-contact check because its edge has pitted enough to trap residue. A bin can be structurally sound and still fail because of a hairline crack invisible from three feet away. A record that only tracks whether equipment works will miss both.
Which equipment and how often is your plan’s call. The specific equipment covered, the inspection frequency, and what condition disqualifies a piece of equipment from use are set by your food safety plan and the standard you are certified against, and they vary by commodity and by equipment type. Your certifier is the authority on the requirement. This page describes the record that shows it was met.
The line between food-contact and everything else
Not every piece of equipment on a farm needs the same kind of scrutiny. A tractor that pulls a loaded wagon down a farm road is a maintenance concern; the surface of the bin riding on that wagon, which the produce actually rests against, is a food safety concern. The distinction that matters for this record is contact — does the surface touch the harvested product after the point it was last washed or sanitized. Bins, totes, knives and cutting tools, gloves, conveyor surfaces, and packing-line equipment are almost always on the list. A truck cab is almost never on it, even though the truck itself is essential to the harvest.
Damage is a food safety finding, not just a repair ticket
A cracked plastic bin is a maintenance item in most contexts. In a food-contact context it is something else: a crack can trap organic material and residue in a way that resists normal cleaning, turning a single damaged bin into a source that recontaminates every load it touches afterward. The same logic applies to a pitted or rusted knife blade, a conveyor belt with a torn section, or a tote with a broken corner that collects debris.
This is why the inspection record needs to note not just whether equipment was checked, but what condition it was found in and what happened as a result — held back for repair, pulled from service entirely, or cleared for continued use. A record that only says “inspected, OK” answers less than half the question, the same way a checkmark on a sanitation log answers less than a description of what was actually cleaned.
Between-use cleaning is where the record and the practice most often diverge
A bin sanitized once at the start of the day and reused across a dozen loads is a different food safety situation than one sanitized between each load, and a farm’s plan usually specifies which practice applies to which equipment and crop. The inspection record is where the gap between the plan and the practice shows up first, because it is the record most likely to be filled in generically — “bins cleaned” — rather than specifically enough to show the actual frequency.
The stronger entry names the specific bins or equipment, the point in the day’s harvest they were cleaned, and by whom, mirroring the same discipline covered in water testing records: a vague claim of compliance is worth less than a specific, dated entry, even when both describe the same underlying practice.
Who inspects matters as much as what gets inspected
Many operations split this into two layers: the crew using a piece of equipment checks it before each use, and a supervisor performs a more thorough, periodic inspection independent of daily operation. The crew-level check catches the obvious problem before it touches product that day. The supervisor-level check catches the slower-developing problem — a crack widening over weeks, a wear pattern nobody using the equipment day to day would notice because they see it every day.
The reason both layers matter is that familiarity is exactly what erodes a daily check. The same crew handling the same bins every harvest stops seeing them, in the way anyone stops seeing a worn spot on a tool they use constantly. A periodic check from someone who does not touch that equipment daily brings back the fresh eye a daily user gradually loses.
A record that only captures one layer is missing half the picture an auditor expects. Two layers of inspection, each recorded separately with its own date and name, is a stronger showing than a single daily check-off, however diligently that single check is performed.
The equipment record has to reach the lot it touched
A harvest lot has a field it came from, a crew that picked it, and now also the specific equipment it passed through on the way to the buyer. When a contamination question arises, an investigator or auditor traces backward through all three, and equipment that cannot be tied to a specific date or lot is a link that cannot be checked. This is part of the same traceability chain described in traceability more broadly, and it is one of the connections a mock audit is worth testing before the real one arrives. Ask, for a specific lot: which bins touched it, when were those bins last inspected, and what did that inspection find. If any part of that chain resolves to a shrug rather than a date, the equipment record has a gap the rest of the audit will eventually surface anyway.
Farm40 keeps a dated, assignable work order for tasks like this inside its operations records — an inspection can be logged against the farm with a status, a date, and whoever completed it, the same as any other field activity. There is no separate equipment screen; a check like this lives alongside the rest of the day’s work rather than in a purpose-built inspection module, because no such module exists. The limit is the obvious one: the record is only as accurate as what someone walks up to the bin or the blade and writes down. No software looks at a crack for you.