Skip to content
Agentic Ag

Check the backfat on a pig kill sheet

The Processor data analyst reads the P2 backfat and carcase weights and compares the batch with the grid and past batches.

When · Daily
A pig kill sheet arrives
You get
How the batch fitted the grid; any drift in fat or weight; a reason to check, not a verdict
Approval level
Inform. Tells you what’s happening. Does nothing. You can change it.
Useful for
Pigs

What it uses

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.

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.

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.

See the guardrails

The conversation

How the job plays out, step by step.

2 agents on it

Started 5:40am · Daily

Start to done
26 sec
Agent actions
4
Needed you
No
[AGENT NAME]For the Processor data analyst

Daily check · 5:40am

Kill sheet from [processor] for Batch 41

Processor data analyst

Reads the sheet and matches it to the batch

Batch 41: 82% in the top grid band, down from 90% over the last 5 batches. Most of the drop is fat over the P2 limit in the heavier pigs. Worth checking the diet change on [date].

[AGENT NAME] · 5:40am

Processor data analyst → Batch tracker

Sends the pattern to the batch tracker for the next batch

Done · 5:40am1 waiting for you

  • How the batch fitted the gridSaved
  • Any drift in fat or weightSaved
  • A reason to check, not a verdictWaiting for you

Behind the scenes

  1. 5:40am

    Trigger Daily check

    Kill sheet from [processor] for Batch 41

  2. 5:40am+13 sec

    Processor data analyst works on it · 3 steps

    Reads the sheet and matches it to the batch

    • pdf.extract
    • killsheets.analyseP2, HSCW
    • records.searchBatch 41
  3. 5:40am+2 sec

    [AGENT NAME] messages you

    “Batch 41: 82% in the top grid band, down from 90% over the last 5 batches. Most of the drop is fat over the P2 limit in the heavier pigs. Worth checking the diet change on [date].”

  4. 5:40am+8 sec

    → Batch tracker picks it up

    Sends the pattern to the batch tracker for the next batch

    • agents.handoff
  5. 5:40am+3 sec

    Processor data analyst Done

    Batch result reported with the fat trend and a suggested check; the batch tracker has the pattern

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

The agent behind it

Processor data analystMarkets & sales

The Processor data analyst reads the kill sheets and carcase feedback the Inbox clerk passes on.

What it won’t do

  • Argue with the processor on your behalf
  • Claim it knows why a lot missed; it shows the pattern and suggests a reason to check

More jobs the Processor data analyst 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.

  • Inbound email
  • Photos, PDFs and spreadsheets
  • 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