Monday
Dating and signing a field note
No. 09 Keeping the Record 5 min read
A dated and signed field note lets a future reader tell who recorded what and when. This article covers the minimum a useful note needs.
What is the minimum a field note needs?
A field note needs three things at the top: the date, the recorder's name, and where the note was made. Those three items let a future reader tell who wrote it and when, which is the whole point of dating and signing a note. Without them, a page of observations becomes hard to trust or reuse.
The date should be written in full, for example 14 March 2025, so day and month cannot be swapped. The name should be the person who actually made the observation, not the farm owner if someone else walked the block. The location ties the note to a specific place on a map or unit.
A note that carries these three identifiers at the top is easy to review months later. It also makes it possible to build up a set of notes across a season that can be compared honestly.
Why does a record need a fixed date format?
A fixed date format stops a note from becoming ambiguous. In New Zealand, 03/04/2025 could be read as 3 April or 4 March by someone trained in a different convention. Writing the month as a word removes that risk.
A consistent format also makes paper notes and spreadsheet rows line up. If every note uses the same order, day month year, a later reader can sort them without guessing. The 2025 farm planning resource from Beef+Lamb New Zealand describes keeping a plan as a living document that is reviewed and revised over time, and a stable date format supports that practice without changing the content of the note.
When dates shift, records lose their place. A note that says "early autumn" cannot be checked against a weather event or a stock movement as precisely as one that names a date.
Who should sign a note when more than one person works the block?
The person who made the observation should sign it. If two people walked the same block, both can sign, but the note should say what each person saw or decided. A shared signature with no division of responsibility can hide who is accountable for a later action.
For a farm team, a short line near the top works: recorded by [name], checked by [name] where a second person has read and agreed with the content. The checked by line is useful for decisions that carry cost or risk, such as a change to a fence line or a grazing rotation.
Keeping the recorder's name visible also helps when a note is passed on. A future reader can ask a direct question of the right person instead of guessing whose handwriting or shorthand was used.
How do you tie a note to a place on the map?
Tie the note to a place using the same unit and map name used elsewhere in the record set. If the farm is divided into land management units, name the unit in the note. If a resource chart is used, refer to the row label from that chart. Naming units so others can follow is the discipline that makes this work, and it is covered in Naming units so others can follow.
A note that names both the unit and a nearby feature, such as a gateway or a water trough, is easier to place than one that only names a paddock. When a map is the reference point, the note and the map should use the same label spelling. Checking a map against the ground is a good habit before a note is filed, and the process is described in Checking a map against the ground.
If a photo is taken, record the photo point name in the same note so the image and the written observation can be found together. Photo points that stay comparable are described in Photo points that stay comparable.
What should a note say about changes since the last visit?
A note should record what is different from the last time the place was seen. That difference is often more useful than a full description of the current state. A short line such as "water level lower than March, gate still sound" tells a future reader what changed without repeating the whole picture.
Stating the previous note date helps the reader judge the gap. If the last visit was two weeks ago and the note says the same thing, that is a useful signal. If the gap was six months, the reader knows the comparison is weaker.
A simple checklist keeps the note short and consistent. The table below is a working format, not a required standard, and can be adjusted to suit the farm.
| Item | What to write | Why it matters |
|---|---|---|
| Date | Day month year, written in full | Removes ambiguity and allows sorting |
| Recorder | Full name of the person who observed | Shows who is accountable for the content |
| Place | Unit name plus one nearby feature | Ties the note to a point on the map |
| Previous date | Date of the last note for this place | Sets the comparison gap |
| Change | One or two lines on what is different | Makes the note useful to a later reader |
| Action | Any decision taken, and by whom | Keeps the next step visible |
How long should a field note be kept, and in what form?
Keep the note for as long as it can be useful for comparison and review. A season of notes is often worth archiving together, because a single note only gains meaning when it can be read alongside others. The 2025 farm planning guide treats plans as documents that are reviewed and revised over time, which suggests that notes should be kept in a form that can be revisited.
Paper and spreadsheet both work. One paper sheet and one spreadsheet is a simple discipline that avoids duplication and keeps the record traceable, and the approach is set out in One paper sheet, one spreadsheet. When records are moved to a new format, the date and the recorder's name should travel with them so the note does not lose its identity.
Before archiving, check that the dates are in the same order and that names are spelled the same way. Small inconsistencies become large problems when a set of notes is read as a whole.
What mistakes make a field note hard to trust?
A note becomes hard to trust when it is undated, unsigned, or attached to a place that cannot be found. Another common problem is a note that mixes observation with opinion without saying which is which. A short phrase such as "observed" or "decided" can separate the two.
A note that is rewritten later without saying so is also hard to trust. If a correction is needed, the cleaner practice is to add a dated correction line rather than overwrite the original. That way a reader can see both the first entry and the change.
Finally, a note that uses a private shorthand only one person understands will not serve a wider team. Writing the unit name in full, and using the same terms as the map and the resource chart, keeps the record readable for anyone who comes after.