A visitor log feels like the least important record on a food safety audit checklist, right up until an auditor asks a question a farm cannot answer: who else was on this ground in the last month, and where did they go. The log is not there to be polite about who dropped by. It exists so a contamination trail can be traced back through everyone who had access to the farm, not just the people who worked it.
Vehicles get the same scrutiny for a related reason. A truck is not a neutral object — it carries whatever was on it last, and it can go places on a farm that a visitor on foot cannot: right up to a loading dock, a wash line, or a field access road.
Which visitors and vehicles must be logged is your plan’s call. The specific thresholds — routine deliveries versus one-time visitors, which areas require a health screening question, how long records must be kept — are set by your food safety plan and the scheme you are audited against. Your certifier is the authority on the requirement. This page describes why the record matters and what a useful entry contains.
The question the log has to answer is not “who visited”
The real question is narrower and more useful: who was on the ground, when, and where did they go once they were here. A name and a date answer the first part. They do not answer whether that person walked through an active field, stood next to open product, or stayed entirely in the office. The log earns its keep by capturing the purpose of the visit and, where it matters, which areas were accessed — the difference between a delivery driver who never left the truck cab and a contractor who walked the packing line to quote a repair.
A delivery truck is a route onto the farm, not just a schedule item
It is easy to think of a delivery log as a logistics record — did the truck show up on time, did it carry the right load. From a food safety standpoint it is something else: a vehicle that was somewhere else yesterday is a vector for whatever that somewhere else was carrying — soil, residue, pests, or worse. The log has to capture enough about the vehicle to make that question answerable later: the company or driver, the date and time, what it was there for, and which parts of the farm it reached.
This matters most at the exact points where a vehicle’s presence and a food safety hazard intersect — near a wash line, a loading dock, a field during harvest. A truck that stayed on the outer access road the whole visit is a very different entry than one that backed up to an open bin of harvested product, even if both show up in the log as the same company name on the same date.
The habit worth building is treating a vehicle’s access the same way you would treat a person’s: some areas are open to anyone making a delivery, and some areas — wherever open, unwrapped product sits — deserve a second thought before a vehicle that has been elsewhere that day is allowed near them. The log is what lets you reconstruct, weeks later, whether that second thought happened.
Routine visitors still need a record, even a lighter one
It is tempting to log only unfamiliar visitors and treat regulars — a feed supplier, a neighbor, a family member helping out — as exempt because they are known quantities. Many standards do allow a lighter logging approach for people on the property daily. But “known to us” is not the same claim as “not a risk.” A family member who walked through a field an hour before harvest, or a regular supplier whose truck happens to be carrying something new that week, can introduce exactly the same hazard as a stranger. The log needs some version of every real visit, even if the regulars get a simpler entry than a one-time contractor does.
A simpler entry for a regular is still an entry — a name, a date, and a checkbox for whether anything about that visit was out of the ordinary. What is not defensible is treating familiarity as a reason to skip the log entirely, because the log’s value is cumulative: it is only useful weeks later, when someone needs to know who was on the ground during a specific window, and a gap for “just the neighbor” is still a gap.
The health question, when required, belongs with the visit
Where a food safety plan requires screening visitors for recent illness or animal contact before granting access to sensitive areas, the answer to that screening belongs in the same entry as the visit — not on a separate sign-in sheet that has to be cross-referenced by date and name. A visitor log split across two documents is the same problem as a water test split from its response: technically both records exist, but neither answers the question on its own.
The log is one of the first things checked on audit day
Visitor and vehicle logs tend to be requested early during an audit walk-through, partly because they are quick to check and partly because a gap here is a fast signal about how seriously the rest of the paperwork should be trusted. A log with obvious holes — days with no entries at all during a season the farm was clearly operating and receiving deliveries — invites closer scrutiny of everything else in the file, the same instinct an auditor brings to an empty corrective action log. It is exactly the kind of gap the mock-audit exercise in food safety audit prep is designed to surface before a real reviewer finds it first.
Keep it where someone will actually fill it in
The single biggest failure mode for a visitor log is not what it contains — it is that it sits somewhere inconvenient and gets forgotten. A clipboard at a gate nobody uses, or a sign-in sheet kept in an office fifteen minutes from where deliveries actually arrive, produces a log with gaps that have nothing to do with visitor volume and everything to do with placement.
Farm40 keeps a farm’s documents and dated records in one place that is reachable from a phone, so a visitor or delivery entry can be logged at the gate rather than reconstructed at a desk later. The limit is the one that runs through every record in this cluster: it stores what someone enters. A visitor who was never logged does not exist in the system any more than one never written on paper does, and no export can retroactively produce a visit nobody recorded.