Check a new yield map is clean before it’s used for zones
A yield map with a bad calibration or overlaps looks convincing and can put next year’s fertiliser in the wrong places. The errors are only obvious if someone checks the total against the weighbridge.
The Variable-rate mapper checks the yield file for header calibration errors, overlaps, headland and turn values and missing strips and lists what needs cleaning before the map goes into the zone history.
- When · Daily
- A harvest yield file arrives for a paddock
- You get
- List of problems in the file by type and area; whether calibration looks out against the weighbridge; a clean-up list; a note to keep the map out of zones until fixed
- Approval level
- Inform. Tells you what’s happening. Does nothing. You can change it.
- Useful for
- Cropping
What it reads
- Yield files from the header
- Weighbridge or docket tonnes for the paddock
- Paddock boundary
- Header operator notes
What you get
- A list of problems in the file: overlaps, headlands, speed spikes, missing strips
- The header total against the weighbridge tonnes
- A clean-up list, and a note to keep the map out of zones until it’s sorted
When it stops and asks you
- Two headers worked the paddock with different calibrations
- Weighbridge tonnes for the paddock aren’t complete
- A strip is missing and it doesn’t know why
How often
After each paddock is harvested
Who uses it
ManagersAdvisors and consultants
What it uses
Photos, PDFs and spreadsheets
Send in scale exports, scan results, soil tests, old spreadsheets or a photo of the shed whiteboard, and they become records.
John Deere Operations Center
If we get access, machine records for sowing, spraying and harvest would be filed against the right paddock.
The last 2 make it better, but it works without them.
Nothing official leaves the farm without your yes.This job runs at Inform: tells you what’s happening. Does nothing. You can change that any time.
The conversation
How the job plays out, step by step.
Variable-rate mapper
Started 5:40am · Daily
- Start to done
- 3 min
- Agent actions
- 6
- Needed you
- 1×
[AGENT NAME]For the Variable-rate mapperDaily check · 5:40am
Yield file for Paddock 8 wheat arrived from the header

Variable-rate mapper
Checked the file against the boundary and the dockets

Paddock 8’s yield file reads 612 t but the dockets add to 548 t, so the header is reading about 12% high. There’s overlap on 6% of the paddock and two missing strips by the dam. Two headers worked it. Was the second header calibrated separately?
[AGENT NAME] · 5:40am
The contract header did the dam end. No idea about its calibration.
You · 5:42am

Variable-rate mapper
Split the file by machine and compared each with the dockets

Your header is within 2%. The contract header is reading about 30% high on the dam end. I can show you what it looks like scaled to the dockets with the overlap and headland passes taken out. Keep the map out of the zones until you’ve had a look.
[AGENT NAME] · 5:43am
Done · 5:43am3 saved
- A list of problems in the file: overlaps, headlands, speed spikes, missing stripsSaved
- The header total against the weighbridge tonnesSaved
- A clean-up list, and a note to keep the map out of zones until it’s sortedSaved
Behind the scenes
5:40am
Trigger Daily check
Yield file for Paddock 8 wheat arrived from the header
documents.read[file] [date]
5:40am+16 sec
Variable-rate mapper works on it · 4 steps
Checked the file against the boundary and the dockets
- Header total 612 t
- Dockets for Paddock 8: 548 t
- Overlap on 6% of the area, two missing strips near the dam
records.search2 headers in Paddock 8 per harvest log
5:40am+2 sec
[AGENT NAME] messages you
“Paddock 8’s yield file reads 612 t but the dockets add to 548 t, so the header is reading about 12% high. There’s overlap on 6% of the paddock and two missing strips by the dam. Two headers worked it. Was the second header calibrated separately?”
5:42am+3 min
You reply
“The contract header did the dam end. No idea about its calibration.”
5:42am+10 sec
Variable-rate mapper works on it · 2 steps
Split the file by machine and compared each with the dockets
- Own header: within 2% of its share
- Contract header: about 30% high
5:43am+2 sec
[AGENT NAME] messages you
“Your header is within 2%. The contract header is reading about 30% high on the dam end. I can show you what it looks like scaled to the dockets with the overlap and headland passes taken out. Keep the map out of the zones until you’ve had a look.”
5:43am+3 sec
Variable-rate mapper Done
Clean-up list sent to you with the scaling worked out; original untouched; keep Paddock 8 out of zone history until you’ve checked it
- Set out for you: yield file check
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
Variable-rate mapperCroppingThe Variable-rate mapper turns yield maps and soil tests into variable-rate seed and fertiliser plans, zone by zone.
What it won’t do
- Set rates without your agronomist’s sign-off
- Send a file to a machine
- Build zones from one season alone without saying so
More jobs the Variable-rate mapper does.
- Draft a variable-rate urea plan for a paddockOn demand
- Find the zones that underperform every yearScheduled
- Price a variable-rate seed plan against a flat rateOn demand
- Draft a variable-rate lime plan from the grid soil testsScheduled
- Check the variable-rate file is ready for the spreaderOn demand
- Check variable-rate zones still fit each paddock’s shapeScheduled
Put [AGENT NAME] to work on your farm.
We’re taking a small number of pilot farms in [REGION]. Start with one or two agents and add more as you go.
See it on a farm like yours.
30 minutes with Thomas, our founder, on records like your own.
Livestock, paddocks, visitors and tanks, in one place.
The farm management software comes with every plan. Keep the software you already use, or use ours.
Not ready yet? Start with a free calculator.
The sums you do every week, for stock, pasture, crops and the books. No sign-up.
Watch a job before you commit.
Pick a playbook and see it play out, step by step.

