How to Record Irrigation Plans and Actual Field Work

An irrigation plan is useful before work begins. An operational record is useful after the next handover.

The difference matters when a team needs to answer simple but consequential questions: Which block was intended to be irrigated? Was the work completed? Which source and equipment were used? Did anything interrupt the event? Who is checking the unfinished item?

This article sets out an ACA working framework for irrigation record keeping. It is designed to help teams compare planned work with actual field activity without prescribing irrigation timing, water volumes, system settings or crop-specific schedules. The format can be adapted to a paper sheet, spreadsheet, work-order system or farm software.

Start with a record that can support the next handover

A plan records intent. It may say that a particular field, block or irrigation zone is expected to be worked on a given day or shift. That is valuable, but it does not establish that the event happened as planned.

A completed record adds the operational facts needed by the next person: the actual date and time, the area or identifier involved, the source and equipment used, the status of the work, and any unresolved issue.

The NRCS Irrigation Scheduling Recordbook provides one example of structured records that bring together irrigation applications, crop-water-use information and soil-water information. It is a scheduling resource developed for its own context, not a universal operating template. Its useful lesson for any team is narrower: planning information and records of irrigation applications serve related but different purposes.

ACA’s practical recommendation is to use one repeatable event record with two parts:

• Planned event: what the team expected to do before work started.
• Completed event: what was actually done, changed, stopped or left open.

Keeping both parts together avoids a common handover problem: a later reader sees a planned task but cannot tell whether it was completed, delayed or replaced by other work.

The record should remain proportionate to the operation. A small team may need a single shared sheet. A larger operation may connect the entry to a field map, maintenance ticket, pump log and staff roster. In either case, the record should be simple enough to complete consistently.

Keep the planned event and completed event side by side

A plan should be entered before the task begins, using the same identifiers that will appear in the completed entry. This creates a direct comparison rather than two disconnected documents.

For example, the planned section might state the intended date, field or block ID, source or outlet, system reference and expected status. It does not need to forecast agronomic outcomes or state an irrigation recommendation.

After the event, the operator or supervisor records what happened. The completed section should distinguish between work that was completed, partly completed, deferred, stopped or not started. If the operation records duration, meter readings or an estimated application figure for its own purposes, those can be included as operational data. They should not be added merely to make the form look more precise.

A Vermont irrigation and surface-water-use example form illustrates fields such as date, field name, crop, pump, system type, duration and estimated application information. That form is an example from a specific jurisdiction and date. It does not establish what farms elsewhere, including farms in China, must record.

For day-to-day use, the distinction can be as straightforward as this:

The value is not in filling every possible box. The value is in being able to compare intent and outcome without relying on memory.

Use stable identifiers for the field, source and equipment

A useful irrigation entry needs identifiers that remain meaningful after staff changes, shift changes or seasonal turnover. Informal names such as “the lower field” may work within one crew but become unclear when maps, contractors or management records use different names.

At a minimum, consider recording:

• the planned and actual date;
• the field, block, patch or zone ID;
• a crop or activity reference where it helps distinguish the work area;
• the water source, outlet or supply reference;
• the system, pump, valve group or equipment reference; and
• the person, role or team completing the entry.

The identifiers should match records the team already uses, such as a field map, work order, pump register or maintenance log. Creating a separate naming system for irrigation usually creates avoidable reconciliation work.

The Irrigation Australia record booklet offers another example of record design, including outlet, meter, valve, patch and crop identifiers. It is useful as evidence that irrigation records can connect an event to specific locations and equipment. It is not evidence of Chinese legal requirements, water-use reporting rules, permit conditions or local farm instructions.

Where an identifier is uncertain, record that uncertainty rather than guessing. For example, “block ID to confirm against map” is more useful than applying the wrong identifier and allowing the error to enter later summaries.

Record what changed, not only what went to plan

A record that contains only successful events can create a misleading picture of the operation. Delays, interruptions and incomplete work are often the details that matter most at handover.

Use a short exception field to capture what changed. The entry should be factual and operational rather than speculative. A practical format is:

1. What happened: delayed start, stoppage, fault, access issue or source interruption.
2. What it affected: the relevant field, zone, equipment or portion of the planned work.
3. Current status: resumed, adjusted, partly complete, deferred or left incomplete.

For example: “Start delayed; access route unavailable; Block B not started; reschedule decision pending.” This says what is known without asserting why the access issue occurred or what irrigation response should follow.

ACA suggests using exceptions such as delayed starts, stopped work, equipment faults, source interruptions, weather-related operational changes, access constraints and incomplete areas as prompts. These are workflow examples, not a universal taxonomy and not evidence that any particular event will affect crop performance, yield, water quality or compliance.

Avoid vague notes such as “problem with irrigation” if a clearer factual description is available. At the same time, do not turn the field record into a diagnosis. If an equipment issue needs technical assessment, the irrigation record can refer to the relevant maintenance ticket or inspection record.

Add a follow-up owner before the record is closed

An exception becomes actionable only when someone knows what happens next. The person making the entry does not need to decide an agronomic change or authorize repairs. They do need to make unresolved work visible to the appropriate role.

For each open item, add:

• the follow-up action needed;
• the responsible person or role;
• a due date or review trigger, where the team uses one; and
• a closure note once the item has been checked or completed.

This separates observation from recommendation. “Zone 4 work incomplete; irrigation lead to review at next handover” is an accountable record. “Increase tomorrow’s irrigation” is a management instruction that may require information beyond the event record.

Field-level context matters because fields can differ in soil, crop, planting date, rainfall and plant growth conditions. The University of Minnesota Extension guidance on field-level irrigation scheduling records makes this point in the context of its scheduling method. ACA’s workflow inference is that unresolved tasks should remain connected to the specific field or block involved, rather than appearing as a general note with no location.

A follow-up owner can be a named role rather than an individual when shifts rotate. Examples include irrigation lead, maintenance coordinator, block supervisor or farm manager. Use the role labels already recognised by the team.

Use one simple layout that fits paper, spreadsheet or farm software

The following is an ACA working template. It is not a permit form, audit form or legal reporting format. Teams should remove columns they cannot maintain consistently and add references required by their own internal procedures or locally verified requirements.

For a paper record, leave enough space for a short factual note and a follow-up reference. For a spreadsheet, use controlled status options where possible, such as completed, partial, delayed, stopped and not started. This makes it easier to filter unresolved work without forcing staff to write the same words in multiple ways.

For farm software, avoid duplicating data that already exists in a work order or equipment register. Instead, link the irrigation event to the existing job number, equipment ID or field map reference. The purpose is continuity across records, not building a second system.

The Vermont example form and the Irrigation Australia booklet show that tabular formats can capture irrigation-event information. The NRCS recordbook similarly shows the value of structured records across planning and application activity. None of these overseas materials can determine which format meets local reporting or water-use obligations in China. Verify those requirements separately with the relevant local authority, water manager or professional adviser.

Review records for unresolved work, not for a false sense of precision

A short review at shift handover, weekly planning or another team-defined interval can help turn entries into usable operational information. The timing should fit the way your team actually allocates work; there is no universal review interval.

Use the review to ask:

• Which planned events have no completed status?
• Which entries are marked partial, delayed or stopped?
• Do open exceptions have a follow-up owner?
• Does the field or block ID match the team’s map and work log?
• Are equipment issues linked to the appropriate maintenance record?
• Has the follow-up been closed, or does it need to remain visible?

This is a review of work status, not a claim that the records alone establish irrigation performance or determine the next application. Records can inform later management decisions when they are complete enough to be understood in context. They cannot replace local agronomic assessment, equipment checks, water-source management or applicable requirements.

Frequently asked questions

What is the difference between an irrigation plan and an irrigation record?

An irrigation plan records intended work before it begins. An irrigation record shows what actually happened, including the field or block involved, the source and equipment used, the completion status and any exception. Keeping both in one entry allows the team to compare intention with outcome.

What should be recorded when an irrigation event is delayed or stopped?

Record the factual reason known at the time, the area or task affected, the current status and the follow-up owner. For example, note whether work was delayed, resumed, partly completed or deferred. Do not add unsupported conclusions about crop effects or prescribe a schedule change in the exception field.

Should each field or block have its own irrigation record?

Each event should be linked to a stable field, block, patch or zone identifier where practical. This helps a team distinguish work across operating areas. The identifier should match the existing farm map or work-record system rather than create a new parallel naming convention.

Do irrigation records need to include water volume?

Not necessarily. A team may record meter readings, duration, estimated application information or other operational details when these are available and useful within its own system. Whether volume data is needed for a particular farm depends on its established operating process and any separately verified local requirements. Do not treat a generic template as proof that a field is mandatory.

Start with one shared layout for planned and completed work, then test it during the next handover. If an entry cannot show what was intended, what occurred and who owns any open item, revise the record before adding more detail.