Building a resource chart that stays useful

A resource chart is a single working sheet that describes each land management unit on your farm: where it is, what it is like, what it does well, where it struggles, and the conditions under which you would farm it. It is not a report and not a plan chapter. Its job is to hold the description of each unit in one place, in a fixed format, so you and anyone else can look a paddock up and get the same answer.

What should a resource chart actually contain?

One row per unit, and a small fixed set of columns. The New Zealand farm planning material that many people work from suggests recording, for each land management unit, its strengths, weaknesses and any opportunities, management practices or conditions of use that apply. That is the whole content of the chart. Everything else on the sheet is scaffolding: a unit name, a short location note, and maybe a reference to the map or photo point where the unit is visible.

The temptation is to add columns. Resist it for the first version. A chart with nine columns that nobody fills in is worse than a chart with five that gets updated every season.

How do I keep each unit entry short enough to read?

Set a length limit before you start writing, and stick to it. A practical limit is one line per cell: roughly 15 words for a strength or weakness. The strength of a unit is rarely more than a phrase. If you find yourself needing three sentences, you are describing two different things, and one of them probably belongs in a different column.

A useful discipline is to write the conditions of use as instructions rather than explanations. "Graze only when soil is firm" is a condition. A paragraph about how the soil behaves in a wet winter is background reading, and it belongs elsewhere.

Where do the strengths and weaknesses come from?

They come from what you already know, checked against the map and against the ground. The published guidance is blunt about this: you probably are not starting from scratch, and you may already hold maps or information from a regional council, a fertiliser company or an earlier workshop. The chart is a way of pulling those fragments into one consistent shape.

The trap is writing strengths that are really just labels. "Good country" is not a strength. "North-facing, early to dry in spring" is. The same applies to weaknesses: "difficult" tells a reader nothing, while "shaded until mid-morning in winter, stays wet longer" tells them how to work around it.

What is the difference between a condition of use and a management practice?

A management practice is something you do. A condition of use is something that has to be true before you do it. The distinction matters because conditions are the part that other people most often need to know, and the part most often left implicit.

If you keep the map open while you write, this column writes itself faster. Deciding what belongs on the base map in the first place is covered in what a base map actually shows, and the shading conventions that make slope and aspect readable are set out in reading slope and aspect shading.

When is a unit too small to appear on the chart?

If a landform has different rules for how it is used, it earns a row. If it does not, it does not. The test is behavioural, not spatial: a small steep face with its own access constraint and its own wet-weather rule is a unit. A larger paddock that behaves uniformly throughout is one unit even if it is split by a fence.

This is the same question as naming, and the two decisions should be made together. A unit whose name means nothing to the person reading the chart in three years will not be used. The reasoning behind consistent naming is worked through in naming units so others can follow.

How do I decide what gets a column and what gets a note?

Use a simple split. If you would filter or sort by it, it is a column. If you would only ever read it in place, it is a note.

Kind of information	Column or note?	Why
Unit name	Column	Every row needs an identity and it is the sort key
Main landform	Column	You will group units by landform constantly
Strength	Column	Short, comparable across units
Weakness	Column	Short, comparable across units
Condition of use	Column	The reason the chart exists
Access notes	Note	Read in context, rarely sorted
History of the paddock	Note	Background, changes slowly
Photo point reference	Column	Links the chart to the record

This alone will keep most charts from turning into a novel. The chart holds the comparable facts. Everything else goes in a note field or an entirely separate document.

The spreadsheet equivalent of the same discipline is worth setting up early, because the chart will eventually live in one. Keeping to a single sheet rather than a workbook of fragments is the approach described in one paper sheet, one spreadsheet, and it is what makes the totals recheckable later.

How often should the chart change?

Change it when the ground changes or when your understanding of the ground changes, not on a fixed calendar. A new fence, a new track, a wetter-than-usual winter that reveals a drainage problem: all good reasons. A tidy-up for its own sake is not.

Build in one habit that makes the chart trustworthy. Any change to a row gets a date and an initial, so a later reader can see when the description was last tested against reality. Without that, a chart ages into a set of assumptions that nobody can date.

What does a good resource chart look like once it is finished?

It looks unremarkable. A dozen or so rows, five or six columns, short entries, a name for every unit and a condition of use for every unit that needs one. It fits on one screen or one sheet of paper. You can find a paddock in it in a few seconds, and so can someone who has never worked on the farm.

That is the standard worth holding to. If the chart cannot be read at a glance, the detail has outgrown its purpose, and some of it belongs in the field notes instead.