Skip to content
Agentic Ag
On demandAct with approvalAudit & records

Log the modules off a field at picking

Modules sit on pads for weeks before the gin carts them, and a lost or mislabelled one is a lot of money. When the gin’s figures don’t add up, you need the field-by-field count from the day it was picked.

The Cotton crop monitor records the module count, IDs and pad location by field, and later matches them to the gin’s receivals so every module is accounted for.

When · On demand
“Finished Field 4. 62 round modules, at the north pad”
You get
Modules logged by field and pad; module IDs from photos; gin receivals matched as they come in; any missing module flagged
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
Irrigated cropsCropping

What it reads

  • Module count and pad from the picker operator
  • Photos of module tags
  • Gin receival notices

What you get

  • Module count and IDs logged against the field and pad
  • A running tally of modules carted and still on pads
  • A flag on any module the gin hasn’t received after carting

When it stops and asks you

  • A tag photo can’t be read
  • The count from the picker and the tags don’t agree
  • A module was moved between pads

How often

Daily through picking, then as the gin carts

Who uses it

ManagersFarm staff

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.

Live

Inbound email

Forward invoices, kill sheets, NVDs, soil tests and emails from your stock agent to your own farm address. The team reads each one, sums it up and suggests who handles 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 with approval: prepares it fully. You tap yes. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Cotton crop monitor

Started 7:12am · On demand

Start to done
8 min
Agent actions
6
Needed you
3×
[AGENT NAME]For the Cotton crop monitor

Finished Field 4. 62 round modules, at the north pad. Tag photos coming.

You · 7:12am

Cotton crop monitor

Read the tag photos

62 modules from Field 4 on the north pad. 61 tags read fine. One photo is blurred, ending in 47. Can someone get a clearer shot next time they’re out there? Then I’ll log them all. OK?

[AGENT NAME] · 7:12am

Approved

Yep.

You · 7:14am

Done. It’s [tag number].

Staff · 7:19am

Cotton crop monitor

Logged the modules with the missing tag and updated the pad tally

Cotton crop monitor

Matched the gin’s receival notice against the pad tally a week later

[Gin] has received 116 of the 118 north pad modules. The 2 missing are Field 4, tags [tag] and [tag]. Are they still on the pad, or worth asking the gin?

[AGENT NAME] · 7:20am

Done · 7:20am3 saved

  • Module count and IDs logged against the field and padSaved
  • A running tally of modules carted and still on padsSaved
  • A flag on any module the gin hasn’t received after cartingSaved

Behind the scenes

  1. 7:12am

    You ask

    “Finished Field 4. 62 round modules, at the north pad. Tag photos coming.”

  2. 7:12am+7 sec

    Cotton crop monitor works on it · 1 step

    Read the tag photos

    • photos.read61 readable tags, 1 blurred
  3. 7:12am+2 sec

    [AGENT NAME] asks for your yes

    “62 modules from Field 4 on the north pad. 61 tags read fine. One photo is blurred, ending in 47. Can someone get a clearer shot next time they’re out there? Then I’ll log them all. OK?”

  4. 7:14am+3 min

    You approve

    “Yep.”

  5. 7:19am+5 min

    Staff replies

    “Done. It’s [tag number].”

  6. 7:19am+13 sec

    Cotton crop monitor works on it · 3 steps

    Logged the modules with the missing tag and updated the pad tally

    • records.createField 4, 62 modules, north pad
    • North pad: 118 modules from Fields 3 and 4
    • memory.remembernorth pad tally
  7. 7:20am+10 sec

    Cotton crop monitor works on it · 2 steps

    Matched the gin’s receival notice against the pad tally a week later

    • documents.read[gin] receival, 116 of 118 north pad modules
    • 2 Field 4 modules not on the notice
  8. 7:20am+2 sec

    [AGENT NAME] messages you

    “[Gin] has received 116 of the 118 north pad modules. The 2 missing are Field 4, tags [tag] and [tag]. Are they still on the pad, or worth asking the gin?”

  9. 7:20am+3 sec

    Cotton crop monitor Done

    Field 4 modules logged with IDs; gin receivals matched; 2 modules flagged as not yet received

    • reports.draftmodule tally by field

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

The agent behind it

Cotton crop monitorCropping

The Cotton crop monitor keeps the season’s checks together: square counts, insect checks, defoliation timing, modules and gin results.

What it won’t do

  • Recommend sprays or defoliation timing: that’s your agronomist’s call
  • Make up a count
  • Change gin results

More jobs the Cotton crop monitor 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
  • Inbound email
  • 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