Every farm that pays anyone keeps a labor record of some kind, because you cannot write a paycheck without writing down who worked and for how long. That much is universal. What is not universal is whether the record says anything else — and most don’t.
The clock-in a worker makes at seven in the morning is a single event, but two entirely different readers want something from it. The payroll reader wants a name, a start, a stop, and a rate. The management reader wants to know what that block of hours actually bought — which field, which herd, which enterprise the work went into. Most farms build a system that satisfies the first reader and throws away the second, not on purpose, but because nobody added the one field that would have kept both.
This page is about that field, why it costs almost nothing to add, and why most farms discover its absence only when they try to answer a question the record was never built to answer.
This is not legal or employment advice. Wage rules, overtime thresholds, and hour-reporting requirements vary by jurisdiction and change over time; nothing on this page tells you what your farm is required to track for payroll or compliance purposes. What follows is about a separate, additional use of the same hours — attributing them to the work they were spent on. For what your payroll obligations actually are, ask your labour authority, your payroll provider, and a lawyer.
One clock-in, two unrelated jobs
Picture an hour spent moving irrigation pipe on the south forty. To the reader who cuts the paycheck, that hour is a row: a name, a duration, a wage. Once the pay run is done, a farm that records hours only for payroll will never open that row again. It has done its job and it is finished.
To the reader who runs the operation, the same hour is a cost, and a cost has to belong somewhere. It was not spent on “the farm” in the abstract; it was spent on the south forty, and if you want to know what the south forty cost to bring in, that hour has to land against it — not against a general pool that swallows every hour worked all season. The two readers agree on almost everything about the hour. They disagree about the one field most farms leave blank: what the work was for.
What “on what” adds, and why it is free
The field itself is not complicated. It is a place, next to the name and the hours, to write the enterprise the work was performed for — a block, a herd, a planting, a barn. It does not require new software, a new process, or a new person. It requires that the question “what was this for” get answered at the moment the hours are written down, by the person who already knows the answer without having to think about it.
That last part is the whole argument. The person logging the hour knows, right then, which block they were in. A week later, nobody does — not with any confidence. The cost of the field is one line item written at the time of work. The cost of skipping it is a reconstruction project in December, performed from memory, that produces a number dressed up as data.
The enterprise field is the difference between a total and an answer
A labor total tells you how many hours the farm paid for. It cannot tell you whether the melon block or the tomato block ate more of them, because the total does not know the difference. Only a record that carries the enterprise alongside the hour can answer that — and it is exactly the question a cost-of-production figure depends on, because labor is usually the largest single input a farm buys.
It also matters for a reason that has nothing to do with money. When an hour is attributed to an enterprise and to the specific person who worked it — the subject of recording who did the work — the record answers two different questions at once, with no additional writing beyond what payroll already required.
Where the record breaks: the general labor pool
The failure mode is not dramatic. It is a farm that logs hours correctly, pays everyone correctly, and simply never routes the hours anywhere more specific than “farm labor.” Every hour worked all season lands in one bucket. At year end, someone tries to figure out what the new orchard block cost to establish and discovers that the labor line is a single number covering every enterprise on the property, undivided.
The fix at that point is not possible. You cannot go back and ask forty timesheets which block each hour served, because nobody wrote it down and nobody remembers. The general pool is not a shortcut you can unwind later; it is a decision, made silently, every time a labor entry is written without an enterprise attached.
What this costs to do right, and what it buys
Doing it right costs one additional decision per entry, made by someone who already has the answer in front of them. It buys a cost-of-production number that is built from actual attribution rather than an end-of-season guess, and it buys the ability to answer, mid-season, whether a struggling block is struggling because of the crop or because of the labor it is absorbing.
None of this requires software particularly. A spreadsheet with a column for the enterprise, filled in at the time the hours are logged, does the job. What software changes is whether the field gets filled in reliably, at the point of work, instead of skipped because the form did not ask.
Where this fits in a labor record
This is one piece of the broader case made in farm labor recordkeeping: that the same record can serve the reader who pays and the reader who decides, if it carries a few more fields than payroll alone requires. Farm40 keeps labor logs that tie each entry of hours to the enterprise that consumed them, so the cost flows through to cost of production without a second data-entry pass. The limit is the same one that applies to every part of this system: it is a record of hours against enterprises, not a payroll system or a time clock, and it does not calculate wages, overtime, or anything your payroll provider is responsible for.
The hour and the name you are already writing down. The enterprise is the second field, and it is the one that turns a payroll record into a cost record without asking anyone to do the work twice.