Closing a season of farm records

What does closing a season actually mean?

Closing a season means deciding, deliberately, that this set of records is finished rather than merely paused. You settle the totals, name the files, note what changed on the ground, and put everything where the next reader expects to find it. It is a small act of curation, not a big software project.

A working definition helps: the season is closed when a person who did not do the work can open the folder, understand the period covered, see which map and which sheet are authoritative, and recheck a figure without asking you. Until that is true, the records are still open.

Which records belong in the archive?

Start by separating what you will actually reuse from what you only needed in the moment. The useful core is usually smaller than the pile on the desk.

Record type	Keep in the season archive	Usually safe to discard
Base map and unit boundaries	Final version with date and author	Earlier drafts, superseded outlines
Land management unit names	The agreed list and any renames	Working nicknames used for a week
Photo point images	Comparable set from the same points	Blurred or off-angle duplicates
Field notes	Dated, signed sheets	Undated scraps with no place reference
Spreadsheet	The sheet whose totals you trust	Sort and filter scratch copies
Totals and checks	The reconciliation you settled	Intermediate trial calculations

As a decision checklist, ask three questions per item: Will someone use this next season? Does it carry a date and a place? Can I explain it to a stranger in one sentence? Two yes answers is normally enough to keep it.

How should the map be versioned before you file it?

The map is the spine of the archive, so version it first. A base map with the property outline is the sensible starting point, and adding unit boundaries on top of an aerial or topographic image makes the layout readable to someone new. The New Zealand farm planning guidance puts it plainly, that finding a way that works for your farm business matters more than the method, and that a base map with your farm outline is a great way to start.

Keep the naming boring and consistent. A pattern such as year, unit code, layer type and revision letter is easier to trace than a descriptive sentence. Note on the map itself whether boundaries are leased, licensed or owned, because that distinction is easy to lose between seasons.

One habit saves trouble later: record what the map does not show. A short margin note listing omitted features keeps the next reader from assuming the map is complete. If you want to think harder about what belongs on a published sheet, see what a base map actually shows.

How do field notes stay readable months later?

A field note is only useful if it survives the gap between writing and reading. That means a date, a place reference that matches a unit name on the map, and a signature or initials. A note saying the fence on the north face needs work is weak. A note saying a date, a unit code and the same observation is checkable.

Write observations separately from decisions. Observations record what was seen; decisions record what was chosen and why. Mixing them makes it hard to tell later whether something was a fact or an intention.

If you want a method for this, the discipline described in dating and signing a field note transfers well to archiving, because a signed note carries its own provenance.

What makes a spreadsheet total recheckable?

A total should be reproducible from the sheet without guesswork. That means keeping the base figures visible, using simple formulas that reference the same columns you can see, and avoiding overtyped numbers that replace a calculation. The farm data workbook from Beef+Lamb New Zealand walks through building totals with a formula and an autosum across stock classes, which is a reasonable model to copy.

Before closing, do one recheck pass. Hide and unhide columns to confirm nothing is concealed that changes a figure. Sort and filter the sheet to see whether any rows are missing or duplicated, then undo back to the original view so you file the settled version, not the working view.

A short reconciliation note is worth more than a perfect sheet. If two totals disagree and you resolved it, say so and say how. A future reader trusts a page that admits its own corrections more than one that hides them. The principles in totals that can be rechecked apply directly here.

How do photo points and units stay comparable across years?

Comparability comes from repetition, not from better photographs. Keep the same points, the same framing and the same rough time of year, and the sequence becomes evidence. If a point has to move, record why in the archive rather than quietly repointing it.

Unit names do the same job for the map. A unit list that changes each season breaks the thread between years, so renames should be logged with the date of the change. Naming units so others can follow is a useful companion here, because the archive depends on names that mean the same thing in two different years.

What goes on the folder label and the coversheet?

Treat the coversheet as the front door of the archive. A single page with the season, the farm or block name, the list of files, the person who closed it and the closing date answers most questions without opening a thing.

On the physical folder or the digital folder, use the same short code that appears on the coversheet. Avoid dates written in several formats, and avoid vague labels such as final or latest, which lose meaning the moment a new season starts.

How do you hand the archive to next season's reader?

Close the loop with a short note of what changed and what to check next. Three or four lines is enough: the units that were revised, the photo points that moved, the totals that were reconciled, and the questions left open. That note is the bridge between the season just finished and the one starting.

Keep the archive read-only where you can. If the format allows it, protect the closed folder from casual edits and start the new season with a copied structure rather than writing over the old one. The farm planning overview makes the same point about plans broadly, that they need to be reviewed and revised over time as the farm system demands, which is easier when you can see what changed and when.

Finally, resist the urge to archive everything. A small, well-named, well-dated set that a stranger can navigate beats a complete pile that nobody opens.