How to track harvest without a spreadsheet

Every grain farm tracks harvest somehow. Usually it's a spreadsheet — built by someone who knows the farm inside out, refined over a few seasons, and genuinely quite good. And every year, somewhere around the second week of wheat, it falls behind: tickets pile up unentered, the shed totals are two days old, and the answer to "how much barley is left to cut?" is a shrug and a squint at the heap.

The problem isn't the spreadsheet. It's when the data entry happens.

Why the spreadsheet cracks

A spreadsheet is a transcription system. Something else — a ticket book, a notebook, memory — captures the loads, and later a person types them in. That works when loads are occasional. During harvest, three things break it:

• Entry happens at the wrong time. The loads come at 20-minute intervals for 12 hours; the typing happens at 9pm, if the person doing it is still upright. Every day of lag makes the totals less useful and the backlog more daunting.
• One person owns it. The spreadsheet lives on the office PC or one laptop. The combine operator can't see it, the trailer drivers can't add to it, and if its owner is on the drier all day, nothing moves.
• It trusts memory. "Which field was that fourth load from?" is answerable at 10am and pure fiction by 9pm. Half the errors in harvest spreadsheets aren't typos — they're guesses, made confidently, days later.

The result is a record that's accurate in November and useless in August — precisely backwards, because August is when the decisions get made: which shed to open next, whether the milling wheat is staying separate, when to book the next lorry.

What a working system looks like

The fix isn't a better spreadsheet; it's moving the recording to the moment the load exists. The principles:

1. Record at the weighbridge, not the office. The load gets logged while the trailer is on the bridge — weight, crop, field, destination shed, ideally moisture. Fifteen seconds on a phone. Everything downstream is arithmetic a computer can do; see what belongs on the ticket.
2. Weigh-in and weigh-out are separate events. Real trailers weigh in, queue, tip, and weigh out later. A system that demands both numbers at once gets fed made-up tares. Open loads should stay visible until they close.
3. Everyone writes to the same record. Whoever is at the pad records the load; everyone else just sees the totals move. No merging, no "whose version is right", no single person as the bottleneck.
4. Totals are a view, not a job. Crop totals, shed fill, and per-field tonnages should exist the moment a load is saved. If producing the totals is a task someone does, it will be done late.
5. The harvest year is the unit. This season's numbers matter most next to last season's. A system that starts a fresh file every August throws away the comparison that makes the data worth collecting — see why field-level yields compound.

Nothing in that list is exotic. It's the discipline any decent weighbridge software enforces by default — and it's precisely the shape of Harvestt: loads recorded at the pad on a phone, pending loads visible until the tare closes them, and a dashboard where crop totals, shed stock, and field yields are simply there.

What you get out of it

The payoff isn't neatness, it's decisions made on numbers instead of squints:

• Shed decisions in real time. Knowing shed 2 is at 340 of 400 tonnes at lunchtime changes where the afternoon's loads go — before the mix-up, not after.
• Field yields as blocks finish — while the agronomist conversation is still live and next year's cropping is still open. More on that in the moisture guide, because tonnage without moisture is only half a number.
• A defensible record at selling time. When the merchant's figures and yours disagree, load-by-load records with timestamps win arguments that "the spreadsheet says" loses.
• No evening data entry. Which, in the second week of wheat, is not a small thing.

Frequently Asked Questions

What's the best way to track harvest tonnage?

Weigh and record every load at the point it's weighed, tagged to crop, field, and destination shed. Totals by crop, shed, and field then build themselves. The common alternative — collecting tickets and typing them into a spreadsheet later — produces totals that lag days behind exactly when they're needed live.

Can you track harvest without a weighbridge?

Yes, less precisely: trailer counts with an assumed weight per trailer, calibrated combine yield monitors, or weighed loads at the buyer's intake. Any of these still benefits from load-by-load recording against fields and sheds. A farm weighbridge just makes the weights real rather than assumed.

Why not just use a spreadsheet for harvest records?

Because a spreadsheet needs someone to type entries in after the fact, and during harvest that lag is where accuracy dies — fields get guessed, tares get invented, and totals run days old. Spreadsheets are fine for analysing harvest data; they're poor at capturing it.

What should be recorded for each harvest load?

Date and time, vehicle, gross and tare weights, net weight, crop and variety, source field, destination shed, and moisture if sampled. That's one complete weighbridge ticket — and it's enough to reconstruct crop totals, shed stock, and field yields for the whole season.