Soil sampling program app for agronomists
Agronomists sample paddocks to guide fertiliser, lime and gypsum decisions, taking composite cores along a pattern in each management zone at set depths. The laboratory returns chemistry; the agronomist’s report turns it into a recommendation per paddock. What gets lost between the two is the field context — which zone the cores came from, the paddock history, what was sown and what the grower said.
Built for agronomists running teams of roughly 3–50 inspectors.
Sample Soil test report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Soil test report
Paddock sampling record — Autumn
- Property
- Glenrowan Downs (fictional)
- Sampled
- 3 April 2026
- Depths
- 0–10 cm and 10–30 cm
| Paddock / zone | Cores and context | Status |
|---|---|---|
| Creek Flat — zone A | 20 cores; canola stubble; lime applied 2023 | Status: Sampled |
| Creek Flat — zone B | 20 cores; waterlogging in low corner | Status: Sampled |
| Top Hill | 18 cores; stony, refusal at 20 cm in places | Status: Partial depth |
| House Paddock | Recently spread with manure | Status: Deferred |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the soil test report where your template puts it.
Per paddock or zone
- Paddock and zone ID
- Map location
- Number of cores per depth
- Current crop or stubble
- Recent inputs
- Sampling issues
- Sample bag IDs
Farm visit
- Grower notes
- Planned crop
- Photos
Standards the report works to
- Rayment & Lyons (2011)Soil Chemical Methods — Australasia (CSIRO Publishing)
- The reference for the laboratory method codes printed on Australian soil test results.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the soil test report gets built
Capture it once, offline
Your firm builds the soil sampling program form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your sample locations
Enter sample locations once, as a register. Every one of your samples, bores and monitoring rounds then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The soil test report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a soil test report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The report says every bore was sampled to three metres; the form has BH07 refused at 1.2 m.
Checks a environmental framework usually carries
- Every exceedance in the results tables is discussed in the assessment text
- The guideline values cited match the land use actually being assessed
- No sample or bore ID appears in the prose that is absent from the data
- Data gaps, refusals and deviations from the sampling plan are stated as limitations
Questions
- Can zones within a paddock be recorded separately?
- Zones are a repeat nested under each paddock, so each carries its own cores, depths and bag IDs.
- Can sample bags be scanned?
- A barcode field can capture pre-labelled bag IDs against each zone and depth.
- Can I produce a grower-friendly report?
- The report renders into your own template, so you decide how recommendations are laid out for the grower.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other environmental work we cover
- Asbestos in soil surveysACM in soil report
- Asbestos registers and reinspectionsAsbestos register update
- Beach water quality samplingBeach watch report
- Carbon project monitoringCarbon audit evidence
- Contaminated land auditsAudit evidence pack
- Environmental license compliance roundsLicense condition checklist
- Erosion and sediment auditsESC compliance report
- Groundwater monitoring roundsMonitoring event report
Other disciplines
Rebuild your soil test report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.