Threatened species monitoring report software
Threatened species monitoring tracks one or a few listed species at the same sites over years, often as a condition of approval or as part of a recovery program. Each round repeats a fixed protocol, and the report answers whether the population is stable, increasing or declining, and whether management is working. Government agencies expect the protocol to stay consistent, so any change between rounds needs explaining.
Built for government agencies running teams of roughly 3–50 inspectors.
Sample Species monitoring report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Species monitoring report
Table 2 — Population trend, monitoring sites 1–5
- Species
- Fictional listed orchid (single population)
- Round
- Year 6 of annual monitoring
- Protocol
- Full census of flowering plants in fixed plots
| Site | Flowering plants (Year 5 → 6) | Trend |
|---|---|---|
| S1 — fenced | 84 → 97 | Trend: Increasing |
| S2 — fenced | 51 → 49 | Trend: Stable |
| S3 — unfenced | 33 → 12; heavy grazing | Trend: Declining |
| S4 — burnt 2025 | 0 → 26 (post-fire flowering) | Trend: Recovering |
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 species monitoring report where your template puts it.
Per site visit
- Site (linked register)
- Protocol version
- Observers
- Weather and season
- Site photos
Population
- Count by life stage
- Plants or animals marked
- Breeding or flowering evidence
Threats and management
- Threats observed
- Management action since last round
- Deviation from protocol and reason
Standards the report works to
- EPBC Act 1999Environment Protection and Biodiversity Conservation Act 1999 (Cth)
- Listed species and their recovery plans and approval conditions drive what the monitoring must report.
- BC Act 2016 (NSW)Biodiversity Conservation Act 2016
- In NSW, state-listed species and their conservation programs set further reporting expectations.
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 species monitoring report gets built
Capture it once, offline
Your firm builds the threatened species 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 species monitoring 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 species monitoring 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 the report show each site’s history across all rounds?
- Each visit references the stored site, so the template can loop over every earlier round for a trend table.
- How do we record a change to the protocol between rounds?
- Store the protocol version on each visit and add a required explanation whenever it differs from the previous round.
- Can sensitive locations be left out of the client report?
- Yes. Location is captured as a field, and your template decides whether it appears, so precise locations can stay in the data and out of the document.
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
- Marine mammal observationsMMO shift report
- Nest box monitoringNest box occupancy report
- Pre-clearance ecology surveysClearance survey report
- Revegetation monitoringPlanting survival report
- Seagrass monitoringSeagrass condition report
- Shorebird countsShorebird census report
- Turtle nesting patrolsNesting season report
- Bat call monitoringBat activity report
Other disciplines
Rebuild your species monitoring 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.