Skip to content
Agentic Ag

Flag block tree counts that don’t match the last audit

Crop load estimates, spray volumes, pick labour and plant royalties all start from the tree count. A count that’s 5% out makes every one of those wrong, and an auditor will spot the gap before you do.

The Block manager compares the new count with the block record and the last audit, works out where the difference is by row and updates the record with the cause.

When · Daily
A new row count or picking tally doesn’t fit the tree or vine count on the block record
You get
Difference by block and row; likely cause from replant and loss records; record updated
Approval level
Act and tell. Does it and logs it. You hear about it after. You can change it.
Useful for
Orchards and vines

What it reads

  • Block record: rows, trees per row, total
  • Last audit count
  • Replant and tree loss records since
  • New row counts from staff

What you get

  • The difference by block and row
  • The likely cause from replants and losses on record
  • An updated count

When it stops and asks you

  • The new count was only a sample of rows
  • Replants are in the ground but too small to count
  • The difference is over 5%

How often

Whenever counts come in, mostly in winter and before picking

Who uses it

ManagersFarm staff

On other farms

  • Orchards and vines: In vineyards the count is vines per row, and missing vines show as gaps in the trellis, so it uses gap counts from pruning crews.

What it uses

Live

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.

Live

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.

Partner

Satellite pasture

You’d see pasture cover for each paddock without walking it.

The last 2 make it better, but it works without them.

Nothing official leaves the farm without your yes.This job runs at Act and tell: does it and logs it. You hear about it after. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Block manager

Started 5:40am · Daily

Start to done
5 min
Agent actions
3
Needed you
1×
[AGENT NAME]For the Block manager

Daily check · 5:40am

Pruning crew count for Block 5 Granny Smith is 2,312 trees; record says 2,410

Block manager

Compared row by row with the last audit and checked loss records

Block 5 counted at 2,312, 98 under the record. The whole gap is in rows 14 to 18. 22 of those are the collar rot trees pulled last spring. That leaves about 76 unexplained in those rows. Any other losses I don’t know about?

[AGENT NAME] · 5:40am

Rows 17 and 18 got hit by the hail. A lot died back over summer and were cut out.

Staff · 5:45am

Done · 5:45am3 saved

  • The difference by block and rowSaved
  • The likely cause from replants and losses on recordSaved
  • An updated countSaved

Behind the scenes

  1. 5:40am

    Trigger Daily check

    Pruning crew count for Block 5 Granny Smith is 2,312 trees; record says 2,410

    • records.searchBlock 5
  2. 5:40am+13 sec

    Block manager works on it · 3 steps

    Compared row by row with the last audit and checked loss records

    • Audit [date]: 2,410
    • Rows 14 to 18 short by 98 trees
    • Loss record: 22 trees pulled for collar rot in rows 15 and 16
  3. 5:40am+2 sec

    [AGENT NAME] messages you

    “Block 5 counted at 2,312, 98 under the record. The whole gap is in rows 14 to 18. 22 of those are the collar rot trees pulled last spring. That leaves about 76 unexplained in those rows. Any other losses I don’t know about?”

  4. 5:45am+5 min

    Staff replies

    “Rows 17 and 18 got hit by the hail. A lot died back over summer and were cut out.”

  5. 5:45am+3 sec

    Block manager Done

    Block 5 now 2,312 trees with causes recorded; 98 replants added for the nursery order; crop load forecaster told

    • paddocks.updateBlock 5
    • records.createtree losses, hail

An example with made-up data. Names and figures in [brackets] are placeholders.

The agent behind it

Block managerHorticulture & packhouse

The Block manager keeps the record for every block: variety, rootstock, planting year, tree or vine counts and replants.

What it won’t do

  • Remove or rename a block without asking first
  • Make up a tree or vine count
  • Decide which blocks to pull out

More jobs the Block manager does.

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.

Pilot farms wanted

Want to try it out?

Join the pilot, or book a demo and we’ll walk you through this job on a farm like yours. You text the team from your phone. Some connections are still being built, and we’ll tell you which.

  • SMS and voice notes
  • Photos, PDFs and spreadsheets
  • Satellite pasture
  • Nothing to install

Free report

Getting started with AI.

A free practical guide for Australian farms and agribusinesses

Where AI actually helps on a farm, what it needs from you, the risks to watch, and a 90-day plan to start small.

  • Where it actually helps
  • What it needs from you
  • Risks and guardrails
  • Working out the return
Book a demoJoin the pilot