Revegetation and planting survival monitoring software
Revegetation projects are funded on survival: so many tubestock planted, so many alive at three, six and twelve months. Monitoring counts survivors in fixed plots or rows, records losses by cause — drought, browsing, weeds, flooding — and decides where infill planting is needed. Landcare groups and grant bodies read the survival rate first and the explanation second.
Built for landcare groups running teams of roughly 3–50 inspectors.
Sample Planting survival report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Planting survival report
Survival monitoring — 12 months after planting
- Project
- Fictional Creek riparian planting (2.4 ha)
- Planted
- June 2025, 3,200 tubestock
- Monitoring
- 8 plots of 50 plants, June 2026
| Plot | Surviving / planted | Main loss cause |
|---|---|---|
| P1 — lower bank | 44 / 50 (88%) | Main loss cause: Pass |
| P3 — upper bank | 29 / 50 (58%) | Main loss cause: Drought |
| P5 — near road | 35 / 50 (70%) | Main loss cause: Browsing |
| P8 — floodplain | 41 / 50 (82%) | Main loss cause: Weeds |
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 planting survival report where your template puts it.
Per plot
- Plot ID (linked)
- Planting date
- Number planted
- Number surviving
- Photo point
Per species
- Species
- Planted
- Surviving
- Mean height
Losses and works
- Loss cause
- Weed cover
- Guards intact
- Infill planting recommended
How the planting survival report gets built
Capture it once, offline
Your firm builds the revegetation monitoring 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 sites, transects and plots
Enter sites, transects and plots once, as a register. Every one of your species observations and survey events then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The planting survival 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 planting survival 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 concludes no threatened species were recorded; the survey event on Transect 3 carries an observation that says otherwise.
Checks a ecology framework usually carries
- Survey effort described meets the guideline for the species being assessed
- Every species in the results table is carried through to the discussion
- Weather, season and access limitations are recorded, not left implied
- Each approval or offset condition is addressed explicitly
Questions
- Can survival rates calculate per plot and per species?
- Yes. Calculated fields divide surviving by planted for each row, and the report can average them across plots or species.
- Can we report against the grant’s milestones?
- Milestones can be set up as fields on the project job, and the template places each survival result next to the milestone it answers.
- Can photo points be repeated from the same position each visit?
- Photo points are stored with the plot, so each visit adds a new photo to the same point and the report can show them side by side.
- Can losses be broken down by cause for the funding body?
- Loss cause is a field on each plot record, so the report can total dead plants under drought, browsing, weeds or flooding and explain where infill is going.
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 ecology work we cover
- Fish surveysFish assemblage report
- Flora surveysVegetation assessment report
- Frog surveysFrog census report
- Habitat tree assessmentsHabitat tree register
- Koala habitat assessmentsKoala habitat report
- Marine mammal observationsMMO shift report
- Nest box monitoringNest box occupancy report
- Pre-clearance ecology surveysClearance survey report
Other disciplines
Rebuild your planting survival 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.