Check feed delivered against the silo readings mid-batch
Feed is the biggest cost in a batch, and on a company contract it’s often charged against your result. A docket for a load that went into the wrong silo or a short delivery is easy to catch mid-batch and impossible to prove at settlement.
The Batch tracker adds up the feed dockets for the batch, takes the silo levels, works out feed used so far and compares it with what the birds should have eaten at their weight.
- When · Scheduled
- Day 21 of each batch
- You get
- Feed delivered, in silo and used to date; feed conversion so far; any docket that doesn’t match a silo rise; a note to the grower contract liaison on gaps
- Approval level
- Inform. Tells you what’s happening. Does nothing. You can change it.
What it reads
- Feed dockets for the batch
- Silo levels from readings you send or a sensor export
- Bird or pig numbers and weights
- Feed intake curve for the genetics
What you get
- Feed delivered, on hand and used to date
- Feed conversion so far against the curve
- Dockets that don’t line up with a silo rise
- A note for the grower contract liaison on anything to query
When it stops and asks you
- A silo reading is missing for a delivery day
- Two silos feed one shed
- The feed type on the docket doesn’t match the stage of the batch
How often
Every batch, mid-way
Who uses it
ManagersThe farm office
On other farms
- Pigs: Grower and finisher sheds run the check every three weeks for the length of the batch.
What it uses
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.
Water monitors and weather stations
Trough, tank and rain gauge readings would start jobs for the team.
Agbot
Tank levels from Agbot monitors would come in, so a falling tank becomes a job before stock go short.
The last 2 make it better, but it works without them.
Nothing official leaves the farm without your yes.This job runs at Inform: tells you what’s happening. Does nothing. You can change that any time.
The conversation
How the job plays out, step by step.
2 agents on it
Started 6:00am · Scheduled
- Start to done
- 3 min
- Agent actions
- 6
- Needed you
- 1×
[AGENT NAME]For the Batch trackerOn schedule · 6:00am
Batch 32, day 21: mid-batch feed check
Batch tracker
Matched 9 feed dockets to silo rises
Batch tracker
Worked out feed used and conversion so far

Day 21 check: 94.2 t delivered. Docket [number] says 12 t into silo 4, but silo 4 didn’t rise. Silo 2 did, by 12 t. Looks like it went in the wrong silo. FCR so far 1.42 against 1.38. Shed 3 is most of the gap.
[AGENT NAME] · 6:00am
Silo 2 feeds shed 2, so they got the right feed. Just note the docket.
You · 6:02am

Batch tracker → Grower contract liaison
Passed on the docket for silo 2, not silo 4, so the settlement matches the right shed
Done · 6:03am4 saved
- Feed delivered, on hand and used to dateSaved
- Feed conversion so far against the curveSaved
- Dockets that don’t line up with a silo riseSaved
- A note for the grower contract liaison on anything to querySaved
Behind the scenes
6:00am
Trigger On schedule
Batch 32, day 21: mid-batch feed check
6:00am+13 sec
Batch tracker works on it · 3 steps
Matched 9 feed dockets to silo rises
records.searchdockets 94.2 t delivered- Silo levels: 8 of 9 deliveries show a matching rise
- Docket [number], 12 t grower to silo 4, no rise on silo 4
6:00am+10 sec
Batch tracker works on it · 2 steps
Worked out feed used and conversion so far
growth.calc_gain1.42 FCR, curve 1.38- Silo 2 rose 12 t the same day
6:00am+2 sec
[AGENT NAME] messages you
“Day 21 check: 94.2 t delivered. Docket [number] says 12 t into silo 4, but silo 4 didn’t rise. Silo 2 did, by 12 t. Looks like it went in the wrong silo. FCR so far 1.42 against 1.38. Shed 3 is most of the gap.”
6:02am+3 min
You reply
“Silo 2 feeds shed 2, so they got the right feed. Just note the docket.”
6:03am+8 sec
→ Grower contract liaison picks it up
Passed on the docket for silo 2, not silo 4, so the settlement matches the right shed
- Summary: docket went to silo 2
6:03am+3 sec
Batch tracker Done
Feed delivered and used checked for batch 32 to day 21; one docket shown as silo 2, not silo 4; FCR so far shown with shed 3 as the gap
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
The Batch tracker follows each batch from placement to sale: mortality, weights, feed and feed conversion.
What it won’t do
- Decide when to sell or thin
- Make up a weight or a count
- Change the feed program
More jobs the Batch tracker does.
- Spot a batch falling behindDaily
- Sum up a batch when it’s soldScheduled
- Flag first-week mortality above target in a new batchDaily
- Check how even the batch is from a weigh dayOn demand
- Work out when a pig batch hits the processor’s weight bandScheduled
- Flag a shed where the birds drank less than the restDaily
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.

