Skip to content
farmsorted

Compare water use at halfway with the same day last season

The monthly figure says how much is left, not that you’re running a third ahead of last year. By March that’s the difference between finishing the crop and buying water at the top of the market.

The Water account keeper adds up use to date from the meter readings and the flow meters in Monitoring, puts it beside the same date last season and finds which outlet is behind the difference, and chases the dial reading that wasn’t taken.

When · Scheduled
1 January, the halfway date you set for the irrigation season
You get
Use to date against last season; allocation left; which outlet and block is using more; the missing reading logged
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
Irrigated cropsDairyOrchards and vines

What it reads

  • Meter readings logged on each outlet and pump this season
  • Monitoring: flow meter totals on the river pump and Outlet 4, with last season’s readings
  • Water account: allocation and carryover
  • Blocks watered off each outlet

What you get

  • Use to date against the same date last season
  • Allocation and carryover left
  • Which outlet and block makes up the difference
  • The missing dial reading chased and logged

When it stops and asks you

  • A meter reading is missing for the month
  • A flow meter and the dial disagree by more than a few per cent
  • A block has changed crop since last season

How often

Once a season, at the halfway date

Who uses it

OwnersManagersAdvisors and consultants

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.

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.

2 agents on it

Started 6:00am · Scheduled

Start to done
8 min
Agent actions
7
Needed you
2×
[AGENT NAME]For the Water account keeper

On schedule · 6:00am

Halfway through the irrigation season

Water account keeper

Added up use to date and put last season beside it

Halfway: about 410 ML used, against 315 ML at the same point last season, so 30% ahead. Most of the jump is on Outlet 4. I’ve only got its flow meter for December, because no dial reading was logged on 1 January. Can someone read the dial?

[AGENT NAME] · 6:00am

Outlet 4 dial says 2,204.

Staff · 6:05am

Log 2,204 ML on Outlet 4 for 1 January? That’s 228 ML this season, close to its flow meter, and puts you at 414 ML, 31% ahead of last season, with [y] ML left.

[AGENT NAME] · 6:05am

Approved

Yep. Block 4’s in lucerne now, that’s the difference.

You · 6:07am

Water account keeper

Logged the reading and noted the lucerne

Water account keeper → Irrigation scheduler

Passed the halfway figures and Block 4’s use to the Irrigation scheduler, to plan the rest of the season against what’s left

Done · 6:08am4 saved

  • Use to date against the same date last seasonSaved
  • Allocation and carryover leftSaved
  • Which outlet and block makes up the differenceSaved
  • The missing dial reading chased and loggedSaved

Behind the scenes

  1. 6:00am

    Trigger On schedule

    Halfway through the irrigation season

    • Calendar: 1 January, the date you set
  2. 6:00am+16 sec

    Water account keeper works on it · 4 steps

    Added up use to date and put last season beside it

    • records.searchmeter readings this season; Outlet 4 last logged 1 December
    • Monitoring: river pump flow meter 186 ML since 1 August; Outlet 4 flow meter 224 ML
    • Same date last season: 315 ML in all
    • water.read_accountallocation [x] ML, [y] ML left
  3. 6:00am+2 sec

    [AGENT NAME] messages you

    “Halfway: about 410 ML used, against 315 ML at the same point last season, so 30% ahead. Most of the jump is on Outlet 4. I’ve only got its flow meter for December, because no dial reading was logged on 1 January. Can someone read the dial?”

  4. 6:05am+5 min

    Staff replies

    “Outlet 4 dial says 2,204.”

  5. 6:05am+2 sec

    [AGENT NAME] asks for your yes

    “Log 2,204 ML on Outlet 4 for 1 January? That’s 228 ML this season, close to its flow meter, and puts you at 414 ML, 31% ahead of last season, with [y] ML left.”

  6. 6:07am+3 min

    You approve

    “Yep. Block 4’s in lucerne now, that’s the difference.”

  7. 6:08am+10 sec

    Water account keeper works on it · 2 steps

    Logged the reading and noted the lucerne

    • records.log_readingOutlet 4, 2,204 ML, 1 January, read by [staff]
    • memory.rememberBlock 4 changed to lucerne this season
  8. 6:08am+8 sec

    → Irrigation scheduler picks it up

    Passed the halfway figures and Block 4’s use to the Irrigation scheduler, to plan the rest of the season against what’s left

    • reports.draftHalfway water use, this season against last
  9. 6:08am+3 sec

    Water account keeper Done

    Outlet 4’s January reading logged; halfway report filed with use 31% ahead of last season; the Irrigation scheduler working to what’s left

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

The farm software this job works from

Put [AGENT NAME] to work on your farm.

We’re taking a small number of pilot farms in Australia. 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
  • 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