Platform · document 12

Reports and Snapshots

In the workspace: /reports

Availability

Included on Basic, Pro and Advanced

This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.

What it is for

A finding on a screen persuades nobody who was not there. A snapshot is that finding fixed in time: dated, attributable, and unchanged by any later audit. It exists so that a conversation with a client, a developer or an auditor can be about the evidence rather than about whose memory is correct.

How to use it

Run the audit you want to record.
Create the snapshot from the report. From that moment it is fixed: a later audit produces a new snapshot rather than editing this one.
Export or print when you need to hand it over. The printed form keeps the findings and drops the interactive controls, which is what makes it readable on paper.

Reading the result

Every snapshot carries the date of the observation and the standard each finding was assessed against. Where a finding rests on an advisory rather than a documented engine requirement, the snapshot says which, because the difference decides how hard you should argue for the fix.

What it cannot tell you

A snapshot is evidence of what was true on its date. It is not a forecast, and a clean snapshot from last quarter says nothing about today. It is also not an accreditation: this platform certifies nothing, and a snapshot that claimed to would be worth less, not more.

What it keeps

The snapshot and its findings, bounded per project so that evidence cannot accumulate unread. The bound is shown on the register itself.