Check a block count that’s way off last year
One miscounted block, or a count done on the wrong rows, can throw the whole season’s bins forecast and the picker numbers built on it. It’s usually caught only when the bins don’t turn up.
The Crop load forecaster holds the odd count out of the forecast, shows what’s different from last year and asks for a recount or a reason before it goes to the packhouse.
- When · Daily
- A new fruit count puts a block 30% or more above or below last year at the same stage
- You get
- The block, both counts and the gap; likely reasons from the records; recount request or a note of the reason
- Approval level
- Act with approval. Prepares it fully. You tap yes. You can change it.
- Useful for
- Orchards and vines
What it reads
- This week’s fruit counts by block and the rows counted
- Last season’s counts and final bins for the same block
- Block notes: thinning, frost, pruning changes, trees pulled
- Count sheet photos
What you get
- A flag with both counts and the size of the gap
- Possible reasons pulled from the block notes
- A request for a recount on set rows, or the reason saved with the count
When it stops and asks you
- The block notes don’t explain the gap
- The rows counted this year aren’t the same as last year
- The count sheet photo is hard to read
How often
Each count round, a few times a season
Who uses it
ManagersFarm staff
What it uses
SMS and voice notes
Text the team, send a voice note or a photo, or forward a message. There’s no new app to learn.
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.
The last one makes it better, but it works without it.
Nothing official leaves the farm without your yes.This job runs at Act with approval: prepares it fully. You tap yes. You can change that any time.
The conversation
How the job plays out, step by step.
Crop load forecaster
Started 5:40am · Daily
- Start to done
- 5 min
- Agent actions
- 3
- Needed you
- 2×
[AGENT NAME]For the Crop load forecasterDaily check · 5:40am
Block 11 count came in at 312 fruit per tree; last year at the same stage it was 198

Crop load forecaster
Checked the block notes and the rows on the sheet

Block 11 counted at 312 a tree, 58% up on last year. Two things: the rows counted were 2 to 4 on the edge, last year was 10, 14 and 18, and there’s no hand thinning logged yet. I’d leave it out of the forecast for now. Recount the middle rows?
[AGENT NAME] · 5:40am
Thinning crew hasn’t been through yet, that’ll take it down. But yeah, get the middle rows done.
You · 5:42am

I’ve drafted a text to Sione to count rows 10, 14 and 18 tomorrow, and I’ll tag the count as pre-thinning. Look right?
[AGENT NAME] · 5:42am
Yep, I’ll send it.
You · 5:45am
Done · 5:45am3 saved
- A flag with both counts and the size of the gapSaved
- Possible reasons pulled from the block notesSaved
- A request for a recount on set rows, or the reason saved with the countSaved
Behind the scenes
5:40am
Trigger Daily check
Block 11 count came in at 312 fruit per tree; last year at the same stage it was 198
records.searchBlock 11 countsphotos.readcount sheet
5:40am+13 sec
Crop load forecaster works on it · 3 steps
Checked the block notes and the rows on the sheet
- Count sheet: rows 2, 3, 4 (edge rows)
- Last year: rows 10, 14, 18
- No thinning recorded yet this season
5:40am+2 sec
[AGENT NAME] messages you
“Block 11 counted at 312 a tree, 58% up on last year. Two things: the rows counted were 2 to 4 on the edge, last year was 10, 14 and 18, and there’s no hand thinning logged yet. I’d leave it out of the forecast for now. Recount the middle rows?”
5:42am+3 min
You reply
“Thinning crew hasn’t been through yet, that’ll take it down. But yeah, get the middle rows done.”
5:42am+2 sec
[AGENT NAME] asks for your yes
“I’ve drafted a text to Sione to count rows 10, 14 and 18 tomorrow, and I’ll tag the count as pre-thinning. Look right?”
5:45am+3 min
You approve
“Yep, I’ll send it.”
5:45am+3 sec
Crop load forecaster Done
Block 11 count held out of the forecast; text to Sione ready for you to send, for a recount of rows 10, 14 and 18; count tagged pre-thinning and the row list saved for next time
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
Crop load forecasterHorticulture & packhouseThe Crop load forecaster turns fruit counts and sizing into bins or trays per week, so the packhouse, pickers and buyers can plan.
What it won’t do
- Promise volumes to a buyer
- Forecast a block without counts
- Share forecasts outside the farm without asking first
More jobs the Crop load forecaster does.
- Turn fruit counts into bins per weekOn demand
- A weekly peak-week forecast for the packhouse and pickersScheduled
- Redo the crop forecast after hail goes throughDaily
- Project harvest fruit size against the buyer’s count sizesScheduled
- Turn the bin forecast into picker numbers by weekOn demand
- Redo the packable fruit forecast after a scorching dayDaily
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.


