Water gets treated, on most farms, as infrastructure rather than as an input. A spray gets logged because it came out of a jug with a label. A fertilizer gets logged because it came in a bag with a rate on the tag. Irrigation just runs — a pivot goes around, a drip line turns on, a hand line gets moved — and none of that naturally produces a written record the way opening a container does.
But water applied to a field is an input in every sense that matters for a record: it goes onto a specific piece of ground, on a specific date, from a specific source, at some volume or duration, and it can carry its own risks depending on where it came from. The only difference between an irrigation event and a spray application, from a recordkeeping standpoint, is that nothing forces the irrigation event to be written down.
Source is the fact that gets skipped most often
Ask most farms about irrigation and you’ll get a volume, a rough schedule, or a description of the system. Ask about the source — well, municipal, surface canal allocation, recycled or reclaimed water — and the answer is often less precise, even though the source is usually the single most important fact for anyone reviewing the record later.
A food safety audit asking about irrigation is almost never asking how much water a field received. It is asking where that water came from, what quality testing it has behind it, and how close to harvest it was applied — because those are the variables that actually bear on risk. A record that logs gallons but not source has answered the less important half of the question.
Method and timing change what the record has to say
Overhead irrigation close to harvest raises different questions than drip irrigation applied at the root zone early in the season, because the water’s contact with the harvestable part of the crop is different. A record that notes only “irrigated” without the method loses exactly the detail that would let a later reader judge whether a given application posed the kind of risk an auditor or a buyer cares about.
This mirrors the discipline behind spray and input records: it is never enough to know that something was applied. What, how, and when relative to harvest are the facts that turn a bare application log into something that can actually be evaluated later, by someone who was not standing at the field when it happened.
An irrigation event is not really a standalone record — it is another entry against the same field that already carries a planting record, a scouting history, and a spray log. Recording it separately, in a different notebook or a different system tied to the pump rather than the field, produces exactly the kind of disconnected record that makes a later question — what did this block actually receive, in total, this season — impossible to answer without reconciling several sources by hand.
Volume matters, but consistency matters more
Farms that do track irrigation volume often do it unevenly — careful during a drought year when water is scarce and worth rationing, casual in a normal year when it doesn’t feel like it matters. The record that results is accurate exactly when it was already obvious that water use mattered, and thin in every other year, which is backwards from what a usable record needs.
The volume does not need to come from a precise meter to be useful — a system runtime multiplied by a known flow rate is enough for most purposes. What matters is applying the same method every time, in every season, so that a field’s water history can be read the same way across years instead of switching between an estimate and a measurement depending on how much anyone cared that year.
Irrigation is increasingly an audited fact, not an assumed one
Water has moved, in a lot of buyer and certifier programs, from a background assumption to a line item that gets asked about directly — where it comes from, whether it is tested, and how its use is documented. That shift means a farm’s irrigation record is no longer purely an internal management tool; it is increasingly something a buyer’s audit or a certification review wants to see, in the same way it already wants to see a spray log.
Treating irrigation with the same recordkeeping seriousness as a spray application — field, date, source, method, and volume, written at or close to the time it happened — is no longer optional diligence. It is catching up with what is already being asked for. It is also the ordinary discipline of running a crop year on the record, applied to the one input that arrives through a pipe instead of a jug.
This is also relevant to organic certification, where water source and application method can bear on a certifier’s review in ways that vary by program. As with any certification question, the specific rule is your certifier’s to state; the record you can control is making sure the source and method are written down consistently enough to answer whatever they ask.
A dry season makes the record's absence obvious
The year an irrigation record is missed most sharply is a dry one — when an allocation is tight, a well runs low, or a buyer starts asking pointed questions about how much water a specific field received during a shortage. Farms that treated irrigation as background noise in wet years suddenly need exactly the record they never built, at the moment they can least afford to reconstruct it from memory. Building the habit in an ordinary year is what makes the record available in the year it actually matters.
Attach it to the same field record everything else uses
An irrigation event, like a spray or a scouting note, is only useful in context if it is tied to the same field or block identifier used everywhere else in that field’s history. An irrigation log kept in a separate notebook, referring to fields by a different naming convention, cannot be read alongside the planting and spray records it needs to sit next to when someone asks a question about the whole season.
Farm40 lets an irrigation event be logged against the same field record used for plantings and input applications, with the source, method, and volume as first-class fields, so a field’s water history sits next to everything else that happened to it. The limit is the same one that applies to every export the product produces: it is a view of what you entered. Farm40 does not meter your system or verify the volume you reported — it does not tell you what you failed to record, only what you did.