Drafts the paperwork. You sign it. Being finished
When it’s time to move or sell stock, the assistant drafts the movement paperwork from your own records and computes every withholding date in code. You review and sign — nothing is ever submitted on its own.
The vendor declaration is the most consequential piece of paper on a cattle operation: a legal statement about the animals, their treatments and their movements. Getting it wrong is expensive; filling it out by hand from four sources is tedious. Compliance drafting builds the draft from the records you already keep — and leaves the signing, always, to you.
It’s written to assist a legally serious task without ever taking it over. The assistant reads your mob, tags, PICs and treatment history and produces an editable document. The compliance arithmetic — withholding periods, export intervals — is done by code, not by the model. And the hard rule underneath all of it: no document is ever submitted without your explicit “approve and sign”.
Draft, review, sign, freeze.
Draft
The assistant assembles the consignment from your records — the animals, the tags, the PICs, the treatment and withholding position.
Review
You get an editable document to check and correct. The withholding and export-interval maths is already computed by code.
Sign & freeze
You approve and sign as the vendor. The signed document is frozen exactly as issued — a later record edit can’t change it.
The maths is code, not a guess
Withholding periods and export slaughter intervals are computed deterministically from the treatments and dates on your records — never estimated by the language model. The model’s job is to assemble the document from the right facts; the arithmetic that decides whether a beast is legal to consign is done by tested code. On something this consequential, “about right” isn’t good enough.
You are always the vendor
The declaration is your legal statement, so you always make it. The assistant drafts; you review, correct and sign. Nothing is auto-submitted, nothing is filed on your behalf, and there is no mode where the AI signs for you. It removes the tedium of assembling the paperwork, not the responsibility of standing behind it.
Frozen once signed
The moment you sign, the document is captured exactly as issued — a frozen snapshot. If you later correct a record (which is always a new, traceable entry, never an overwrite), the document you already signed is untouched. What you put your name to is what stays on file, which is exactly how an audit expects it.
Built to the standard, with live filing to follow
Documents are drafted in the shape of the National Vendor Declaration / eNVD workflow. Live two-way integration with the national eNVD system is a fast-follow once that access is in place; until then, the drafted, signed document stands in for the paper process you use today — so launch doesn’t wait on an external approval outside anyone’s control.
No compliance document is ever submitted without an explicit human “approve and sign”. The assistant drafts; you are always the legal vendor who approves.
The detail.
| Drafts from | Your records — mob, tags, PICs, treatment & withholding history |
|---|---|
| Compliance maths | WHP and ESI computed by code, never by the model |
| Human control | You review, edit and sign; nothing auto-submits |
| Signed document | Frozen exactly as issued; later edits can’t rewrite it |
| Shape | National Vendor Declaration / eNVD-equivalent |
| Live eNVD API | Fast-follow once national system access is secured |
| Status | Live — drafting and the Approve-and-Sign gate |
See it on your own place.
Start free on up to 200 head — no card, no lock-in. Running a bigger show? Book a demo and we’ll set it up around how you work.