When Farm Spreadsheets Stop Working: The 5 Breaking Points for Commercial Growers
By Juraj — orchardist since 2014. I kept these records in spreadsheets first.
I kept my orchard records in spreadsheets for years before I built anything else. They didn't fail all at once. They failed in five specific places, and every one of them cost me either an evening at the desk or accuracy out in the rows.
- Spreadsheets are fine to read on a phone and close to unusable to fill in on one — which is exactly where the record gets made.
- A cell holds a number. It can't hold the photo of the branch you were looking at when you wrote the number down.
- Expenses in one file and harvest in another means you never quite know what a block actually cost you.
- Once a workbook has a dozen tabs, nobody opens it to look something up — and records nobody reads stop being kept properly.
- Rename a column or split a block and you have quietly broken every year-on-year comparison you were keeping records for.
1. Fine to read on a phone. Hopeless to fill in on one.
This is the distinction nobody makes, and it is the one that matters. A spreadsheet on a phone is a perfectly decent thing to read. You can stand in a block, pull up last season's file, and check what you sprayed and when. That part works.
The trouble starts the moment you try to put something in. You pinch to zoom, you land in the wrong cell, the keyboard covers half the sheet, and you are doing all of it one-handed because the other hand is holding secateurs. Add a glove and it stops being worth attempting.
So you don't. You tell yourself you will do it properly tonight. And tonight you are sitting at the kitchen table reconstructing from memory which rows you actually got through and roughly what time you started. The gap between when the work happens and when it gets written down is where accuracy quietly goes.
It gets worse with a crew, but it is not really a crew problem — it was already broken when it was just me.
2. A cell can't hold a photo, a voice note or a video
A good half of what you notice in an orchard is not a number. It is a patch of scab on the shaded side of row 12, a split irrigation line, the particular way a graft has failed, a bird net that will not last another season.
So you photograph it, because that is the fastest way to record something you cannot easily put into words. Now the photo is in your camera roll with four hundred others and the written note, if you made one, is in a spreadsheet. Nothing joins them. Six weeks later you have a picture you cannot place and a note you cannot picture.
The same goes for talking. With dirty hands, the quickest way to record anything is to say it out loud. A spreadsheet has nowhere to put that either — and a voice memo app has nowhere to put the block it belongs to.
3. Every sheet is an island
Expenses in one file. Harvest weights in another. A spray diary in a third, probably started because the first two had nowhere sensible to put it. Each one is fine on its own. The problem is that the questions worth asking need two of them at once.
Joining them means lookup formulas keyed on block names you typed by hand. Rename a block, split one in two, or fix a spelling, and the formula returns nothing or — much worse — the wrong row. It does this silently. There is no error, just a number that is now wrong and looks exactly like a number that is right.
Here is the shape of it. Two blocks, same variety, same season:
| Block 4 — Jonagold | Block 7 — Jonagold | |
|---|---|---|
| Inputs for the season | €2,400 | €2,950 |
| Harvested | 9,000 kg | 7,200 kg |
| Cost per kilo | €0.27 | €0.41 |
Cost per kilo by block is the number that tells you where your season actually went. It is also precisely the number a workbook of separate sheets will not hand you, because producing it means an evening of joining files — and nobody does that in September.
4. You can't find anything
By the third season the workbook has a dozen tabs. There is a copy from 2019 nobody dares delete, a sheet called Sheet1 (2), and one tab that has the good formulas in it which you must not sort. You know where things are. Nobody else does, and on a bad day neither do you.
Everyone treats this as cosmetic. It is not. A record you cannot retrieve in twenty seconds is a record you stop consulting, and once you stop consulting your records you stop keeping them properly — because keeping them stopped paying you back.
The honest test: standing in block 4, can you answer what you last sprayed there and when, before you have finished walking to the end of the row? If the answer is that you would have to go back to the office, the records are not working, however complete they are.
5. By year three you can't compare like with like
Every season starts with a new tab. You tidy up the column names because last year's annoyed you. You split a block because half of it got replanted. You start recording something you were not recording before.
All of that is sensible in the moment and none of it is recorded anywhere. Three seasons in, comparing 2024 with 2026 means remembering that B4 became Block 4 North, that the 2025 yield column was in bins and this one is in kilos, and that the block itself is not the same size any more.
Which is the whole point of keeping records. Alternate bearing only shows up across years. Whether a pruning change worked only shows up across years. Whether a rootstock is paying for itself takes five seasons to answer. A record-keeping system that quietly breaks its own history every January is answering none of those questions, no matter how carefully you filled it in.
What to look for if you do move off spreadsheets
Not enterprise agriculture software. That is built for someone with ten thousand acres and an IT department, and it will cost you more time in setup than the spreadsheet ever cost you in evenings. For 15 to 100 acres the bar is lower and more specific than the sales pages suggest.
- Entry that genuinely works one-handed, in the row, on a phone — not a desktop tool with a mobile view bolted on.
- Photos and voice attached to the record itself, so the evidence and the note are the same object.
- One place where a cost and a harvest can meet, without you writing a lookup formula to introduce them.
- Blocks that are a thing rather than a string you retype, so renaming one does not break five years of history.
- Something a new crew member can use on their first morning without being trained on it.
If you are not ready to move, the next best thing is to stop spreading records across files that cannot see each other. Our free spreadsheet templates are built around one workbook and consistent block names, which fixes the third and fifth problems above and none of the others.
And if you would rather start with the practice than the tooling, how to keep orchard records covers what to write down and when, which is the part that has to be right whichever tool you end up using. When you do want to compare tools, our own is orchard record keeping software built for exactly this size of operation.
Where these records live
Every module hangs off the same blocks and rows, so the numbers in this guide line up instead of sitting in separate files.
Orchard Record Keeping
The whole picture — tasks, harvests, costs and block history kept as one connected record instead of five separate files.
Orchard Task Management
Assign pruning, thinning, mowing and spraying to a crew, and get the work logged back from a phone in the rows.
Orchard Block Management
Structure blocks, rows and tree counts by cultivar, rootstock and planting year, then hang everything else off them.
Orchard Harvest Tracking
Log bins, lugs and weights at the row end, with running yield totals by block and variety as the pick goes on.
Orchard Inventory Management
Keep stock counts, expiry dates and equipment locations honest, with low-stock alerts before a spray window opens.
Orchard Expense Tracking
Log input, labour and machinery costs with the supplier, the category and a photo of the receipt, taken in the field.
Ready to stop retyping the orchard into a spreadsheet?
Log tasks, crew, harvests by block and input costs in one place — from the row, on a phone, without a lookup formula anywhere. Entries are protected if signal drops.