Skip to content
farmsorted
ScheduledAct with approvalAudit & records

Close off unchecked high-risk visits before the LPA audit

The auditor will ask how you manage people and gear coming onto the place, and a register full of flagged visits with nothing written against them looks worse than no register at all. Nobody remembers in March what was agreed with the shearing team in October.

The Compliance officer reads the last 12 months of the visitor register, lists every high-risk visit still marked to check and puts what the records show from that day beside each so the owner can write what was agreed while they still remember.

When · Scheduled
Three weeks before the LPA audit date on the calendar
You get
High-risk visits still to check, oldest first; the records from each day beside them; the register export on the audit list for the week before
Approval level
Act with approval. Prepares it fully. You tap yes. You can change it.
Useful for
BeefSheepGoats

What it reads

  • Visitor register: high-risk visits still to check, last 12 months
  • Each visit’s answers, as the visitor saw the questions
  • Jobs and mob records on the days of those visits
  • LPA readiness check: the biosecurity section

What you get

  • A list of high-risk visits still to check, oldest first
  • Beside each, what the records show that day: which yards were worked, which mobs were in
  • The register export put on the audit list for the week before
  • The biosecurity part of the readiness check marked done once every visit has a note

When it stops and asks you

  • The records from that day don’t show whether the visitor went near stock
  • The same high-risk visitor came back within the week
  • The audit date on the calendar doesn’t match the letter from ISC

How often

Once before each LPA audit, three weeks out

Who uses it

OwnersManagersThe farm office

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.

Compliance officer

Started 6:00am · Scheduled

Start to done
6 min
Agent actions
8
Needed you
2×
[AGENT NAME]For the Compliance officer

On schedule · 6:00am

The LPA audit on [date] is three weeks away

Compliance officer

Read the register back 12 months for high-risk visits still to check

Compliance officer

Matched each visit to what the records show that day

Audit’s in 3 weeks. 4 high-risk visits are still marked to check: the shearing team twice with used gear, [fencer] with used gear, and [name], who’d been on another sheep place. The auditor will look at these. Can you open each one and write what you agreed? I’ve put what the records show beside them.

[AGENT NAME] · 6:00am

Shearers always wash down at the gate, I told them that. The fencer never went near stock. Not sure about [name].

You · 6:03am

Compliance officer

Looked again at [name]’s visit

[name] came through the yards gate for a ram inspection, so he was with stock. If you can’t recall what was agreed, write that, and what you’d do now. I’ll put the register export on the audit list for you to do the week before. OK?

[AGENT NAME] · 6:03am

Approved

Yep. I’ll do the notes tonight.

You · 6:05am

Done · 6:05am1 waiting for you

  • A list of high-risk visits still to check, oldest firstWaiting for you
  • Beside each, what the records show that day: which yards were worked, which mobs were inSaved
  • The register export put on the audit list for the week beforeSaved
  • The biosecurity part of the readiness check marked done once every visit has a noteSaved

Behind the scenes

  1. 6:00am

    Trigger On schedule

    The LPA audit on [date] is three weeks away

    • Calendar: LPA audit, [date]
    • lpa.check_readinessbiosecurity section not done
  2. 6:00am+16 sec

    Compliance officer works on it · 4 steps

    Read the register back 12 months for high-risk visits still to check

    • visitors.read41 visits, 6 high-risk, 4 still to check
    • Visitor register: [shearing contractor], used gear, two visits in [month]
    • Visitor register: [name], another livestock farm in the last 7 days, [date]
    • Visitor register: [fencer], used gear, [date]
  3. 6:00am+13 sec

    Compliance officer works on it · 3 steps

    Matched each visit to what the records show that day

    • records.searchshearing at the woolshed both days, 1,200 ewes through
    • records.search[fencer]’s day: back boundary fence job, no stock in the paddock
    • records.searchnothing on [name]’s day
  4. 6:00am+2 sec

    [AGENT NAME] messages you

    “Audit’s in 3 weeks. 4 high-risk visits are still marked to check: the shearing team twice with used gear, [fencer] with used gear, and [name], who’d been on another sheep place. The auditor will look at these. Can you open each one and write what you agreed? I’ve put what the records show beside them.”

  5. 6:03am+3 min

    You reply

    “Shearers always wash down at the gate, I told them that. The fencer never went near stock. Not sure about [name].”

  6. 6:03am+7 sec

    Compliance officer works on it · 1 step

    Looked again at [name]’s visit

    • visitors.readreason “ram inspection”, came in the yards gate, visiting [owner]
  7. 6:03am+2 sec

    [AGENT NAME] asks for your yes

    “[name] came through the yards gate for a ram inspection, so he was with stock. If you can’t recall what was agreed, write that, and what you’d do now. I’ll put the register export on the audit list for you to do the week before. OK?”

  8. 6:05am+3 min

    You approve

    “Yep. I’ll do the notes tonight.”

  9. 6:05am+3 sec

    Compliance officer Done

    4 high-risk visits listed with the records from each day; the owner adding a note to each visit; the register export on the audit list for the week before

    • lpa.check_readinessbiosecurity, visitor register, 4 visits to close, export due [date]

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

The agent behind it

Compliance officerCompliance & risk

The Compliance officer drafts the NLIS transfers and eNVDs from one text about a sale, and keeps you ready for an LPA audit.

What it won’t do

  • Lodge anything with NLIS, eNVD or LPA without your approval
  • Answer “yes” on a declaration question your records can’t back up
  • Hide a WHP problem to get a draft finished
  • Quote a scheme rule without naming the ISC, MLA or government page it came from

More jobs the Compliance officer does.

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