Field histories that outlast staff and memory

Every farm has field histories. On most of them, the history lives in one person's head — the person who knows that Long Meadow always drowns at the gateway end, that the 14-acre grows a decent first wheat and a shameful second one, and that the pigeons found the rape by the wood in February 2019 and have never forgotten. That knowledge is real and valuable, and it retires, changes jobs, or simply forgets, right alongside its owner.

Writing it down takes minutes per field per season. Keeping it somewhere it survives is the part most farms haven't organised.

What's worth recording, per field, per season

Not everything — the sprayer records already live in the compliance file (see farm record keeping for what has to be kept and for how long). A field history is the shorter, decision-driving layer on top:

Record	Why it earns its place
Crop and variety	The backbone of every rotation decision
Drilling date and conditions	Explains half of what follows
Weighed yield, at standard moisture, over cropped area	The scoreboard — and the only entry that needs discipline
What went wrong	Pigeons, waterlogging, the sprayer miss, the lodged corner
Anything done to the field itself	Drainage work, lime, a new margin, mole ploughing

The "what went wrong" line matters more than it looks. Three years from now, a yield of 6.9 t/ha with no note reads as a poor field; the same figure with "flooded twice, redrilled headland in March" reads correctly as a poor year. Without the note, the field wears the blame forever.

The yield line is the only one with a catch: it has to be weighed tonnage against the field, not a September estimate — which means recording loads against fields during harvest, when nobody has time. How to track harvest deals with that problem directly.

Where field knowledge currently lives, and how it dies

Three places, mostly:

One person's head. The best field histories in the country are stored this way, and every one of them is a single retirement, illness or job move from gone. A new foreman on day one knows nothing that isn't written down — and spends three seasons relearning, expensively, what the farm already knew.

A drawer of diaries. The information exists, technically. Finding what the 30-acre did in 2021 means an evening with a stack of pocket diaries and someone's handwriting. Records that can't be queried don't get queried, and knowledge you can't retrieve is barely knowledge at all.

A spreadsheet nobody else can find. A genuine step up — until its author is on holiday, or the file is on the old laptop, or there are four versions and nobody's sure which is current. A field history with one gatekeeper has the same failure mode as the head, with better handwriting.

The common thread: the record survives only while one specific person maintains it. The fix is structural, not motivational — the history has to live somewhere shared, where the person on the drier can add "shed 3's wheat came in at 19%, off the wet end of Church Field" from a phone, and where next year's questions can be answered without an archaeology project. This is part of what Harvestt does — field yields build from weighed loads as harvest runs, season stacked against season — but a shared drive and an agreed format beats a drawer of diaries by a distance too.

The payoff timeline

Year one is trivia. A single season's records prove almost nothing — any field can be excused by the weather. Write it down anyway; year one is the price of admission.

Year two, patterns start. The field that disappointed twice, in two different seasons, has earned a question. The gateway-end wet patch that appears in both years' notes is now a fact, not an impression.

Year three, it's a management tool. Persistent underperformers separate from unlucky ones — the distinction why one field yields more than another is built on. Rotation calls get grounded: the second-wheat penalty on your heavy block, in your figures. Drainage priorities rank themselves by recorded cost — the field losing 1 t/ha across 15 ha at £180/t is documenting a £2,700-a-year case for the pipe. Variety decisions lean on your fields rather than a trial 200 miles away, and a variety worth an honest extra 0.4 t/ha on your land is worth about £70/ha — visible in three years of records, invisible in none.

From there it compounds. Five years in, the history answers questions you hadn't thought to ask when you started — and it does so for whoever is running the farm, not just whoever wrote it. Benchmarking your yields covers what to do with the numbers once they exist.

The whole thing costs perhaps ten minutes per field per year, plus the harvest discipline of weighing and recording loads against fields. Set against what the farm already spends to learn the same lessons by trial and error, it's the cheapest agronomy going.

Frequently Asked Questions

What records should I keep for each field?

Per season: crop and variety, drilling date and conditions, weighed yield at a standard moisture over the cropped area, anything that went wrong (pests, waterlogging, application misses), and any work done to the field itself such as drainage or lime. That's enough to drive rotation, drainage and variety decisions within three seasons.

How long before field records become useful?

One season is a data point; two starts to show patterns; three is a working management tool, because it usually spans different weather years and lets persistent problems separate from bad luck. The records only pay if they're kept consistently, so the habit matters more than the format.

What's the best way to store field history records?

Anywhere shared, searchable, and easy to add to from the field — the failure mode isn't the wrong software, it's a record only one person can find or update. A well-organised shared spreadsheet works; purpose-built farm software adds the harvest-time load recording that makes the yield line accurate.

Are field histories the same as compliance records?

No. Compliance records (spray records, financial and VAT records — the latter kept for 6 years) are what regulation demands and follow their own rules. A field history is shorter and voluntary: the handful of facts per field per season that improve next year's decisions. Keep both, but don't let the compliance file substitute for the history.