Fauna assessment report template and survey app
A baseline fauna survey combines several techniques over several nights — Elliott and cage trapping, pitfall lines, spotlighting, call playback, scat and track searches — and the assessment report has to show the effort for each technique before it says anything about what was or was not found. The species list is the easy part; the effort table that justifies it is where reports are queried.
Built for ecologists running teams of roughly 3–50 inspectors.
Sample Fauna assessment report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Fauna assessment report
Table 3 — Survey effort by technique
- Site
- Fictional Valley Estate, Stage 2 (64 ha)
- Survey period
- 10–14 November 2025 (4 nights)
- Ecologists
- Two-person team
| Technique | Effort achieved | Against plan |
|---|---|---|
| Elliott traps | 4 lines × 25 traps × 4 nights = 400 trap-nights | Against plan: Met |
| Spotlighting on foot | 6 person-hours over 3 nights | Against plan: Met |
| Call playback (owls) | 2 of 3 planned nights; rain on night 3 | Against plan: Short |
| Hair tubes | Not deployed | Against plan: Not used |
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 fauna assessment report where your template puts it.
Per technique
- Technique
- Location (linked transect or trap line)
- Units and nights
- Start and end times
- Weather each night
Per record
- Species
- Count
- Evidence type (capture, sighting, call, scat, track)
- Breeding or habitat use noted
- Photo
Limitations
- Deviation from survey plan
- Reason
- Effect on conclusions
Standards the report works to
- Commonwealth survey guidelinesSurvey guidelines for Australia’s threatened mammals and threatened reptiles
- The survey effort benchmarks the effort table is set against for listed species.
- NHMRC Code (8th ed., 2013)Australian code for the care and use of animals for scientific purposes
- Underpins the animal ethics approval that trapping and handling is carried out under.
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 fauna assessment report gets built
Capture it once, offline
Your firm builds the fauna survey 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 fauna assessment 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 fauna assessment 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 trap-nights be totalled from what the team enters each night?
- Yes. Each night is a repeat entry with units deployed, and a calculated field sums trap-nights per technique and per line.
- Can a single record count toward both a technique and a transect?
- Records reference the stored trap line or transect, so the same capture shows up in the technique effort table and in the location summary.
- Will the review notice when a species in the results is never discussed?
- An AI review framework can check that every species in the results table is carried into the discussion, and flag it if not.
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
- 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
- Revegetation monitoringPlanting survival report
- Seagrass monitoringSeagrass condition report
Other disciplines
Rebuild your fauna assessment 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.