Who this is for: Anyone reading findings or reports.
Finding references are built from the audit’s reference, so a code tells you where a finding came from without opening anything.
A reference such as FIRES015-L301299-261008-F01 reads as:
Part | Meaning |
FIRES015 | The template’s reference |
L301299 | The location the audit was run at |
261008 | The audit date, as YYMMDD — 8 October 2026 |
F01 | The first finding on that audit |
The first three parts are the audit reference. Findings are numbered F01, F02 and so on within each audit, and root cause analyses get their own running number — RC01, RC02. If the same template is run at the same location on the same day more than once, a two-digit sequence is added to keep each audit unique.
Finding type and severity are not part of the code — they are shown as badges on the finding.
Corrective actions use the reference number they are given in the Actions module, not an audit code. They stay linked to the finding, so you can trace them in either direction.
Why this matters practically: when someone emails you about FIRES015-L301299-261008-F01, you already know which template, which site and which day it came from before you look it up.