Under PAS 79-era practice, the connection between an observation on site and a finding in the report was often implicit. The assessor saw something, formed a view, and wrote it up. The evidence trail might be a folder of photos somewhere with filenames that nobody remembered six months later when a landlord queried a finding.
BS 9792:2025 expects more. Every significant finding should be traceable to the observation, location, and evidence that justifies it. In practice that means each high-priority issue in the report should answer three questions on demand: where was this seen, what did the assessor see, and what evidence (photo, drawing, document, third-party reference) supports the rating that has been given.
For competent reviewers this is the difference between a quick procedural check and a meaningful technical review. The reviewer with traceable evidence can verify the finding by clicking through to its source. The reviewer without traceable evidence is reading prose and trusting the assessor by default. For software, this is the design constraint: a report writer that lets you produce narrative findings without keeping the underlying observation and evidence linked is a tool that fails the standard's implicit data model.
Evidence-linked AI drafting is one practical implementation of this. When the AI generates narrative findings from tagged observations, photos, and risk scores, every drafted line carries a footnote-style link back to its source. The reviewer trusts the AI draft because they can audit it in a click, not because they cross their fingers and read the prose.