Reporting Workflow

The reporting workflow turns reviewed mission findings into a delivery artifact. It should not require the reviewer to rebuild screenshots or copy evidence manually. The report imports findings, evidence, mission context, and asset context from the system of record.

Findings can be imported into reports so the report keeps a link to the original observation, geometry, severity, category, title, notes, and evidence capture. This preserves traceability from report page back to mission evidence.

Reports can have draft and published states. Versioning matters because stakeholders need to know which report was delivered, what changed, and whether later mission edits have been incorporated.

Share links allow controlled stakeholder access to published report output. They should be managed deliberately, especially for client-facing reports or sensitive infrastructure evidence.

• Only include findings that have been reviewed and categorized.
• Confirm severity values match tenant taxonomy.
• Confirm each critical finding has clear evidence.
• Avoid using low-quality measurements without notes or confidence context.
• Preview the report before publishing or sharing.