AGREEING NAMES FOR TREE RECORDS AND PROJECT FILES

Separate persistent tree identity from file names and display labels. A naming convention should help the team locate records without breaking references when the project is sorted, revised or handed over.

Project/site:
Prepared by/date:
Version:

Site code
Use a clear project or location identifier.
Notes:

Tree ID
Preserve the stable asset reference.
Notes:

Visit reference
Identify the dated survey or inspection.
Notes:

File suffix
Distinguish map, report, schedule and evidence files.
Notes:

Version
State the issue or revision consistently.
Notes:

CHECKS
[ ] Test names with two sites and repeat visits.
[ ] Check leading zeros and punctuation survive spreadsheet export.
[ ] Keep a record of genuine name changes and their earlier references.

Outstanding questions:
Source references:
Review and next action:

Scope: Naming conventions improve traceability but do not replace access control, backup or professional review.

This is a general worksheet, not an automated application feature.
https://canopyapp.app/resources/tree-record-naming-conventions