Skip to content
Agentic Ag

Spot a block that got more water than planned

A valve that sticks open or a shift left running overnight puts water below the roots, leaches nutrients and burns allocation. Without comparing applied to planned, nobody knows until the water account is short.

The Irrigation scheduler compares planned against applied water by block, uses the probes to check where the extra went and flags the likely cause, such as a valve left open or a long shift.

When · Daily
Logged watering, or the probe readings you send, show a block got well over its planned mm
You get
Planned against applied by block; the extra ML; likely cause; next watering for that block pushed back
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
Orchards and vinesIrrigated cropsDairy

What it reads

  • The watering plan by block
  • Logged run hours or flow meter readings
  • Probe readings you send, at each depth before and after
  • Valve and controller faults on the job list

What you get

  • A flag with the block, the planned and applied mm, and the extra ML
  • Whether the probes show water going past the root zone
  • A pushed-back next watering and a check job for the valve

When it stops and asks you

  • The flow meter and logged hours disagree
  • The block was watered on purpose for frost or salt flushing
  • Two blocks share a valve

How often

A few times a season

Who uses it

ManagersFarm staff

What it uses

Partner

Water monitors and weather stations

Trough, tank and rain gauge readings would start jobs for the team.

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.

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.

See the guardrails

The conversation

How the job plays out, step by step.

Irrigation scheduler

Started 5:40am · Daily

Start to done
6 min
Agent actions
5
Needed you
2×
[AGENT NAME]For the Irrigation scheduler

Daily check · 5:40am

The probe export you sent this morning shows Block 8 up overnight at 80 cm; Block 8 wasn’t on last night’s plan

Irrigation scheduler

Checked last night’s plan and the run log

Block 8 got water last night though it wasn’t on the plan. Its probes rose from 11 pm at all three depths, so it’s down to 80 cm. Block 7 shares a manifold. Looks like Block 8’s valve opened with 7. Roughly 18 ML extra.

[AGENT NAME] · 5:40am

That solenoid’s been playing up. Get Dave on it.

You · 5:42am

I’ll raise a job for Dave on the Block 8 solenoid, and push Block 8’s next watering from Tuesday to Friday. OK?

[AGENT NAME] · 5:42am

Approved

Yep.

You · 5:45am

Irrigation scheduler

Raised the job and moved the watering

Done · 5:45am3 saved

  • A flag with the block, the planned and applied mm, and the extra MLSaved
  • Whether the probes show water going past the root zoneSaved
  • A pushed-back next watering and a check job for the valveSaved

Behind the scenes

  1. 5:40am

    Trigger Daily check

    The probe export you sent this morning shows Block 8 up overnight at 80 cm; Block 8 wasn’t on last night’s plan

    • probes.readBlock 8, 30, 60 and 80 cm rising from 11 pm
  2. 5:40am+13 sec

    Irrigation scheduler works on it · 3 steps

    Checked last night’s plan and the run log

    • Plan: Blocks 7 and 9, 8 hours
    • Run log: Block 7 valve on, Block 8 valve not on the log
    • records.search
  3. 5:40am+2 sec

    [AGENT NAME] messages you

    “Block 8 got water last night though it wasn’t on the plan. Its probes rose from 11 pm at all three depths, so it’s down to 80 cm. Block 7 shares a manifold. Looks like Block 8’s valve opened with 7. Roughly 18 ML extra.”

  4. 5:42am+3 min

    You reply

    “That solenoid’s been playing up. Get Dave on it.”

  5. 5:42am+2 sec

    [AGENT NAME] asks for your yes

    “I’ll raise a job for Dave on the Block 8 solenoid, and push Block 8’s next watering from Tuesday to Friday. OK?”

  6. 5:45am+3 min

    You approve

    “Yep.”

  7. 5:45am+10 sec

    Irrigation scheduler works on it · 2 steps

    Raised the job and moved the watering

    • jobs.createBlock 8 solenoid
    • records.create18 ML unplanned, Block 8
  8. 5:45am+3 sec

    Irrigation scheduler Done

    Solenoid job raised for Dave; Block 8 next watering moved to Friday; unplanned 18 ML logged against the block

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

The agent behind it

Irrigation schedulerIrrigation & water

The Irrigation scheduler turns soil moisture and evapotranspiration into when and how much to water, block by block.

What it won’t do

  • Start or stop pumps
  • Water over a block’s allocation without telling you
  • Make up a probe reading

More jobs the Irrigation scheduler 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.

  • Water monitors and weather stations
  • SMS and voice notes
  • 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