Agree the checking responsibilities
Identify who will collect data, review records and approve the outputs. The scope determines what needs to be checked. Record the site boundary, required fields, units, location method and deliverables before fieldwork so the team has a shared reference.
Review an early sample
Inspect a small representative set of tree records before the full survey is completed. Check that the IDs, locations, measurements, notes and photographs can be interpreted as intended. Resolve differences in conventions early and document the agreed approach for the rest of the team.
Useful review points
- Before fieldwork: brief, coverage, access and record conventions.
- After the first sample: field completeness, units and evidence references.
- During collection: duplicate IDs, missed areas and unresolved questions.
- Before issue: map, schedule, photographs and report consistency.
- At handover: exported files, versions and recipient requirements.
An example check with evidence
Illustrative check: The reviewer samples T005 and finds that its map ID and photo caption agree, but its measurement unit is missing. The issue is recorded, corrected and rechecked. The team also checks whether the same omission affects other records instead of treating the single correction as proof that the whole dataset is complete.
Keep a review record
Record the check, reviewer, date, issue, action and recheck result. Identify the version reviewed and retain unresolved questions. Sampling is useful for finding consistency issues; it does not replace review of the professional conclusions that will be issued.
Review the exported outputs
Open the actual PDF, schedule and supporting files. Check that the source corrections reached the issued version, maps are readable and references remain consistent. Preserve the issued package with its date so subsequent changes can be identified.
Use the Canopy pilot checklist, schedule checks and report review guide.
Prepared by Canopy.