Pull a pen’s antibiotic history for the processor’s program
Processor programs ask for treatment history in their own format, usually with a week’s notice. Pulling it out of the hospital book by hand takes a day, and one missing reason holds up the whole pen.
The Feedlot QA clerk pulls every antimicrobial treatment on the pen’s cattle from induction to dispatch, with product, date, reason and who gave it and drafts the report in the format the processor asked for.
- When · On demand
- “[Processor] wants the antibiotic treatments on pen 14 for their [program]. Can you get it together?”
- You get
- Antimicrobial treatments for the pen in the processor’s format; head never treated; gaps marked; report ready for you to send
- Approval level
- Act with approval. Prepares it fully. You tap yes. You can change it.
- Useful for
- Feedlots
What it reads
- The processor’s request and the format it asks for
- Treatment records for every animal in the pen
- Hospital pen notes
What you get
- Every antimicrobial treatment by tag, product, date and reason
- A count of head never treated
- The report drafted, with any gap marked rather than filled
When it stops and asks you
- A treatment has no reason recorded
- A product isn’t clearly an antimicrobial
- Cattle were treated before they came to the yard
How often
When a processor or program asks, a few times a year
Who uses it
ManagersThe farm office
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.
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 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.
The conversation
How the job plays out, step by step.
Feedlot QA clerk
Started 7:12am · On demand
- Start to done
- 6 min
- Agent actions
- 5
- Needed you
- 3×
[AGENT NAME]For the Feedlot QA clerk[Processor] wants the antibiotic treatments on pen 14 for their [program]. Can you get it together?
You · 7:12am

Feedlot QA clerk
Read the request and pulled the treatments

Pen 14 has 165 head. 21 were treated with an antimicrobial: 17 for respiratory, 3 for footrot, and one on tag [number] with no reason recorded. 144 never treated. Know what that one was?
[AGENT NAME] · 7:12am
Pinkeye. [Staff] did it.
You · 7:14am

I’ll add pinkeye with [staff] noted as the source. Report is drafted in [processor]’s format. Send it to you to forward?
[AGENT NAME] · 7:14am
Yep, send it over.
You · 7:17am

Feedlot QA clerk
Filled the gap and finished the report
Done · 7:17am1 waiting for you
- Every antimicrobial treatment by tag, product, date and reasonSaved
- A count of head never treatedSaved
- The report drafted, with any gap marked rather than filledWaiting for you
Behind the scenes
7:12am
You ask
“[Processor] wants the antibiotic treatments on pen 14 for their [program]. Can you get it together?”
7:12am+13 sec
Feedlot QA clerk works on it · 3 steps
Read the request and pulled the treatments
documents.read[processor] email: tag, product, date, reason, number of treatmentsrecords.searchpen 14, 165 head; 21 treated with antimicrobials: 17 respiratory, 3 footrot- 1 treatment on tag [number] with no reason
7:12am+2 sec
[AGENT NAME] messages you
“Pen 14 has 165 head. 21 were treated with an antimicrobial: 17 for respiratory, 3 for footrot, and one on tag [number] with no reason recorded. 144 never treated. Know what that one was?”
7:14am+3 min
You reply
“Pinkeye. [Staff] did it.”
7:14am+2 sec
[AGENT NAME] asks for your yes
“I’ll add pinkeye with [staff] noted as the source. Report is drafted in [processor]’s format. Send it to you to forward?”
7:17am+3 min
You approve
“Yep, send it over.”
7:17am+10 sec
Feedlot QA clerk works on it · 2 steps
Filled the gap and finished the report
records.log_treatmentreason added to tag [number], source [staff]reports.draft[program] treatment report, pen 14
7:17am+3 sec
Feedlot QA clerk Done
Pen 14 antimicrobial report ready for you to send to [processor]; the one gap filled with its source noted
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
Feedlot QA clerkCompliance & riskThe Feedlot QA clerk keeps the NFAS records, the EPA licence conditions and HGP declarations in order.
What it won’t do
- Make an HGP-free declaration the records don’t support
- Deal with the EPA or AUS-MEAT for you
- Change a treatment record after the cattle have shipped
More jobs the Feedlot QA clerk does.
- Check HGP status before cattle go on an HGP-free programDaily
- Pull the month’s EPA licence records togetherScheduled
- Flag the heat load records that weren’t done on a hot dayDaily
- Close out the treatment records before a pen shipsScheduled
- Chase a feed delivery’s CVD before it goes in the rationDaily
- Keep the cattle scales and feed truck calibration currentScheduled
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.


