The Program Submission Form in AgriWebb allows producers to enter program-required data in one place. For Technical Assistants (TAs), this is the central tool for helping producers complete the required annual submissions and baselines for programs.
The form can capture any required data point from livestock transactions to cropping data and it pre-fills information where possible, reducing the burden on producers.
Step-by-Step: Assisting producers with submissions
Starting a new submission
Access the producer's AgriWebb account through your Connect portal.
From the left-hand menu, select Reports.
2. Click the Sustainability tab.
3. Under Programs, find the program the producer is enrolled in.
4. Select Start submission to begin, or open an existing submission to continue.
Understanding cohorts
Cohorts group animals that are managed the same way during the reporting period, for example, all breeder cows or 2024-drop heifers.
AgriWebb automatically creates cohorts using:
Age class (e.g., Heifers, Cows, Steers)
Enterprise (e.g., Breeder, Trading), if available
Notes:
Management groups aren’t included in pre-fill. Create or rename cohorts if you want to review data that way.
You can rename, remove, or add cohorts in the form. This won’t change records in AgriWebb itself.
If animals or records are missing, add or correct them in the AgriWebb, sync, then refresh the submission.
💡 Tip: Keep cohort names consistent across years if you are naming them (e.g., “Heifers — Breeder”) when submitting multi-year baselines.
Completing the form with Pre-Fill
AgriWebb pre-fills the submission form using existing records to save time, but producers must still review and attest to the accuracy of all data before submitting.
How Pre-Fill Works
Pre-fill pulls in existing livestock records from the producer’s AgriWebb account including
Births
Sales
Purchases
Transfers on/off
Deaths
Age In/Out
Cohort changes
Livestock are grouped into cohorts for easier review (see more info above).
It is best to open each cohort and review the data that has been pre-filled for accuracy.
If data needs to be changed we recommend recording or editing the records in AgriWebb and then refreshing the submission form. If needed you can also add records in the submission form but this data will not be available in AgriWebb for further decision-making.
You can edit, add, or remove cohorts directly in the form if needed.
Refreshing Pre-Filled Data
If the producer adds or updates records in AgriWebb, use the Refresh button to pull in the latest data.
Refreshing overwrites manual edits in the form, so re-check and re-edit fields afterwards.
Completing the Form Manually
If pre-fill isn’t available or the producer doesn’t have AgriWebb records, data can be entered manually.
Step-by-Step: Manual Entry
Add Livestock Groups:
Click Add Livestock Group and create cohorts based on enterprise or age class.Enter Data:
Fill in required data for each group (e.g., births, deaths, purchases etc)Save Progress:
You can save and return later. Manual entries are stored in the submission form only and do not sync to the AgriWebb app.
💡 Tip: For producers using AgriWebb, it’s best to record data in the app first, then refresh the submission. That way, records are stored for ongoing management and insights.
Reviewing Before Submission
Review each section with the producer.
Confirm all required fields are complete.
Submit for automatic QC and correct any flagged errors.
Once cleared, you can submit the form to the MRV partner.
Multi-Year Submissions
If the program requires multiple years of data (e.g., a three-year baseline), create one submission per year.
This ensures records are grouped and reviewed correctly.
FAQs for Technical Assistants
Can producers who don’t use AgriWebb day-to-day use the form?
Yes. They can access and complete the Program Submission Form without AgriWebb Records
Can we import data producers have already collected elsewhere?
No. That data must be entered manually to ensure accuracy.
Best Practice Tips for TAs
Use a demo farm account to get familiar with the form.
Sit with producers during their first submission to reduce confusion.
Emphasise that producers own their data and can review before submission.
Keep reference notes on program requirements handy when assisting.